configure_project
Set up a new project by defining its root path and name, organizing files into logical chunks (e.g., functions, classes) for efficient searching and analysis within the MCPunk server.
Instructions
Configure a new project containing files.
Each file in the project is split into 'chunks' - logical sections like functions,
classes, markdown sections, and import blocks.
After configuring, a common workflow is:
1. list_all_files_in_project to get an overview of the project (with
an initial limit on the depth of the search)
2. Find files by function/class definition:
find_files_by_chunk_content(... ["def my_funk"])
3. Find files by function/class usage:
find_files_by_chunk_content(... ["my_funk"])
4. Determine which chunks in the found files are relevant:
find_matching_chunks_in_file(...)
5. Get details about the chunks:
chunk_details(...)
Use ~ (tilde) literally if the user specifies it in paths.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project_name | Yes | Name of the project, for you to pick buddy, something short and sweet and memorable and unique | |
| root_path | Yes | Root path of the project |
Input Schema (JSON Schema)
{
"properties": {
"project_name": {
"description": "Name of the project, for you to pick buddy, something short and sweet and memorable and unique",
"title": "Project Name",
"type": "string"
},
"root_path": {
"description": "Root path of the project",
"format": "path",
"title": "Root Path",
"type": "string"
}
},
"required": [
"root_path",
"project_name"
],
"title": "configure_projectArguments",
"type": "object"
}