MCPDiscovery vs Settlegrid Discovery
A side-by-side look at the MCPDiscovery and Settlegrid Discovery MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCPDiscovery for aggregators work as a local process; choose Settlegrid Discovery for aggregators as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCPDiscovery when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose Settlegrid Discovery when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 43/100 · Fair | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 53 | 1 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View MCPDiscovery | View Settlegrid Discovery |
Tools & capabilities
MCPDiscovery tools
No tool names declared yet. Check the project README from the listing page.
Settlegrid Discovery tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCPDiscovery
{
"mcpServers": {
"particlefuture-mcpdiscovery": {
"command": "npx",
"args": [
"-y",
"@1mcpserver/1mcpserver"
]
}
}
}
Settlegrid Discovery
{
"mcpServers": {
"settlegrid-discovery": {
"command": "npx",
"args": [
"-y",
"create-settlegrid-tool"
]
}
}
}
Frequently asked questions
MCPDiscovery is categorized under Aggregators and uses a local stdio subprocess. Settlegrid Discovery belongs to Aggregators and uses a local stdio subprocess. Pick MCPDiscovery for aggregators work and Settlegrid Discovery for aggregators.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCPDiscovery is listed as free. Auth: no auth required. Settlegrid Discovery has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add particlefuture-mcpdiscovery and settlegrid-discovery as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCPDiscovery has a quality signal of 43/100 (Fair) with 2 views, 0 installs and 53 GitHub stars. Settlegrid Discovery has 39/100 (Fair) with 0 views, 0 installs and 1 GitHub stars.