modular-mcp

Modular MCP acts as a Model Context Protocol proxy server designed to handle large tool collections across multiple upstream MCP servers without overwhelming LLM context windows. It groups tools logically and loads detailed tool schemas only when needed, enabling LLM discovery through group descriptions rather than requiring upfront tool calls. The system maintains a clean separation between tool discovery and execution phases, with the LLM interacting through just two registered tools: get-modular-tools for retrieving group-specific schemas and call-modular-tool for execution. This architecture is particularly valuable for operations teams and developers managing complex multi-server MCP setups who need context-efficient tool management.

[{"step":"Identify the MCP server and tool you need. Check the modular-mcp configuration to confirm the server is registered and the tool schema is available.","tip":"Use `list_servers` and `list_tools` commands in modular-mcp to verify availability before executing tasks."},{"step":"Construct your task with the correct tool name and parameters. Use the modular-mcp proxy to send the request, which will handle schema loading and tool execution.","tip":"If the tool requires complex parameters (e.g., nested JSON), validate the schema first using `get_tool_schema` to avoid errors."},{"step":"Execute the task via the modular-mcp proxy. Monitor the response for status, execution time, and any error messages.","tip":"For long-running tasks, check the `execution_time_ms` field to identify performance bottlenecks. Use this data to optimize future requests."},{"step":"Process the result or handle errors. If the tool fails, check the error message for clues (e.g., missing parameters, authentication issues).","tip":"For persistent issues, restart the modular-mcp server or check its logs for schema loading errors."},{"step":"Log the task and result for audit purposes. Use the metadata (e.g., file size, last modified) to track changes over time.","tip":"Integrate modular-mcp with your existing logging system to correlate tool usage with operational metrics."}]