loading…
Search for a command to run...
loading…
MCP of MCPs. Automatic discovery and configure MCP servers on your local machine.
MCP of MCPs. Automatic discovery and configure MCP servers on your local machine.
MCP of MCPs — automatically discover and configure MCP servers on your machine (remote or local).
After setup, you can usually just say:
“I want to perform . Call the
deep_searchtool and follow the outlined steps.”
The goal is that you only install this MCP server, and it handles the rest (searching servers, selecting servers, configuring servers, etc.).
Choose one of the following:
Use the hosted endpoint (recommended for the simplest setup).
Docs + guided setup: https://mcp.1mcpserver.com/
Add the following entry to your client config file:
./.cursor/mcp.json./gemini/settings.json (see Gemini docs)~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json~/.codex/config.toml%USERPROFILE%\.codex\config.tomlRemote config (JSON):
{
"mcpServers": {
"1mcpserver": {
"url": "https://mcp.1mcpserver.com/mcp/",
"headers": {
"Accept": "text/event-stream",
"Cache-Control": "no-cache"
}
}
}
}
If you already have other servers configured, just merge this entry under mcpServers For example:
{
"mcpServers": {
"1mcpserver": {
"url": "https://mcp.1mcpserver.com/mcp/",
"headers": {
"Accept": "text/event-stream",
"Cache-Control": "no-cache"
}
},
"file-system": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "."]
}
}
}
Tip: If your client supports it, move the config file into your home directory to apply globally.
Use this when you want everything local, or when your MCP client only supports STDIO.
docker run -p 8080:8080 ghcr.io/particlefuture/1mcpserver:latest
Running on other host ports:
docker run -p <FREE_HOST_PORT_NUM>:8080 ghcr.io/particlefuture/1mcpserver:latest
Running with stdio instead of streamable-http (You might see some delays when trying to connect):
run --rm -i ghcr.io/particlefuture/1mcpserver:latest --local
{
"mcpServers": {
"1mcpserver": {
"url": "https://mcp.1mcpserver.com/mcp/"
}
}
}
npx -y @1mcpserver/1mcpserver
Clone this repo and run directly.
git clone https://github.com/particlefuture/MCPDiscovery.git
cd MCPDiscovery
uv sync
uv run server.py --local
{
"mcpServers": {
"1mcpserver": {
"command": "/path/to/uv",
"args": [
"--directory",
"<PATH_TO_CLONED_REPO>",
"run",
"server.py",
"--local"
]
}
}
}
If your client supports remote
urlservers, you can use the Remote setup instead.
If you want your LLM to have file-system access, add an MCP filesystem server and point it at the directory you want to allow:
{
"mcpServers": {
"file-system": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "~/"]
}
}
}
There are two search modes:
For explicit requests like: “I want an MCP server that handles payments.”
Returns a shortlist of relevant MCP servers.
For higher-level or complex goals like: “Build a website that analyzes other websites.”
The LLM breaks the goal into components/steps, finds MCP servers for each part, and if something is missing, it asks whether to:
Deep Search stages:
test_server_template_code)
internal_ prefix unless instructedData sources:
Published to:
ModuleNotFoundError even after installing: delete the venv and recreate it.Please create an issue or directly contact me [email protected] if you encounter ANY issue of frustration. I really hope the setup is as smooth as possible!!
Добавь это в claude_desktop_config.json и перезапусти Claude Desktop.
{
"mcpServers": {
"particlefuture-mcpdiscovery": {
"command": "npx",
"args": []
}
}
}