Feat: CLI tool for quick command line testing

[marksolly]

Interact directly with the indexer's services. Each invocation of this tool behaves as a fresh start of the MCP server. Good for performing quick verification tests during development and also aids automated testing.

Running the CLI:

# Index a project
python src/code_index_mcp/cli.py index --path /path/to/your/project

# Call a specific tool with parameters
python src/code_index_mcp/cli.py call <tool_name> --params '{"param1": "value1"}' --path /path/to/your/project

Available CLI Commands:

• index: Initializes and runs the indexing process for a specified project path.
• call: Invokes a specific tool method with JSON parameters.

Example call Usage:

# Search for code
uv run python src/code_index_mcp/cli.py call search_code_advanced --params '{"pattern": "class.*", "file_pattern": "*.py"}' --path /path/to/your/project

# Get file summary
uv run python src/code_index_mcp/cli.py call get_file_summary --params '{"file_path": "src/module.py"}' --path /path/to/your/project

# Refresh index
uv run python src/code_index_mcp/cli.py call refresh_index --params '{}' --path /path/to/your/project

[jacksenechal]

Do you know about @modelcontextprotocol/inspector? I'm not sure if that fills the same use-case as this.

npx -y @modelcontextprotocol/inspector uvx code-index-mcp

[marksolly]

I do use @modelcontextprotocol/inspector but because it is graphical UI based I find it awkward for repetitive tests and it's more complex/expensive for coding assistants to use. A CLI tool is particularly helpful for development on this repo because it automates the process of launching the server, running a command and exiting it again. Great for automated tests, etc. If there's a way to automate @modelcontextprotocol/inspector from the command line then that would satisfy my needs.

[marksolly]

Closing this PR as it is no longer compatible with main in this repo

[johnhuang316]

Hi @marksolly,

Thanks so much for taking the time to put this PR together! I really appreciate the effort and the idea of having a CLI tool to interact with the indexer.

I'm currently in the middle of reorganizing and refactoring some other parts of the project, so I can't merge this in at the moment.

This is a great feature, though, and I definitely plan to implement it once I've finished the current cleanup.

Thanks again for your contribution!