CrowdCent MCP Server
Official# crowdcent-mcp has moved
The CrowdCent MCP server now ships inside the
[`crowdcent-challenge`](https://github.com/crowdcent/crowdcent-challenge)
package as an optional extra. One config line replaces this repository, no
clone or absolute paths needed:
```json
{
"mcpServers": {
"crowdcent": {
"command": "uvx",
"args": ["--from", "crowdcent-challenge[mcp]", "crowdcent-mcp"],
"env": {"CROWDCENT_API_KEY": "your_api_key_here"}
}
}
}
```
Prefer nothing installed at all? Connect the hosted server at
`https://mcp.crowdcent.com/mcp` with your API key as a bearer token.
## Migrating from this repository
If your `mcp.json` points at a local clone (`uv run --directory
/path/to/crowdcent-mcp server.py`), replace that server entry with the
`uvx` block above. That is the whole migration.
One tool changed: `switch_challenge` is gone. Challenge-scoped tools now
take an optional `challenge_slug` argument instead (defaulting to
`hyperliquid-ranking`), and new simulation tools let your assistant
backtest portfolio constructions on the meta-model.
Docs: [docs.crowdcent.com/ai-agents-mcp](https://docs.crowdcent.com/ai-agents-mcp/)
The original source remains available in this repository's git history.
TDQS
Scored across 13 tools
Each tool has a clearly distinct purpose targeting specific resources and actions. For example, download_inference_data vs get_inference_data_info provide complementary but non-overlapping functionality, and the two submission tools handle different input formats without ambiguity.
All tools follow a consistent verb_noun pattern with snake_case throughout. The naming convention is predictable: download_*, get_*, list_*, submit_*, and switch_* prefixes clearly indicate action types, making the tool set highly readable and systematic.
With 13 tools, this server is well-scoped for its apparent domain of challenge management and data handling. Each tool serves a specific purpose in the workflow, from data retrieval to submission management, without redundancy or obvious omissions in the count.
The tool set provides comprehensive coverage for core challenge workflows, including data access, information retrieval, submission handling, and challenge switching. A minor gap exists in update/delete operations for submissions or challenges, but agents can work effectively with the available CRUD-like operations.