MCP server for CoinStats API integration — stdio CLI + Cloudflare Worker
Connect Coinstats MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server for CoinStats API integration — stdio CLI + Cloudflare Worker. The coinstats mcp mcp server is what makes that connection.
Hosted Model Context Protocol server for the CoinStats API. Lets AI agents (Claude, Cursor, Codex, ChatGPT — anything that speaks MCP) read and act on the same crypto data the CoinStats apps use, over a single OAuth-protected HTTPS URL.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Endpoint — SpecCursor — Restart Cursor; on first call it opens a browser window for the OAuth flowCodex — codex mcp add only registers the URL; it does not open a browser. Run codex mcp login separately:Configuration is passed through the environment: COINSTATS_API_KEY, CLOUDFLARE_ACCOUNT_ID, YOUR_API_KEY, COINSTATS_API_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Coinstats MCP's toolset — Endpoint, Cursor, Codex — is a fair guide to whether it matches your workflow. It is maintained by CoinStatsHQ; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Endpoint | Spec |
| Cursor | Restart Cursor; on first call it opens a browser window for the OAuth flow. |
| Codex | codex mcp add only registers the URL; it does **not** open a browser. Run codex mcp login separately: |
Or via Docker:
```json
{
"mcpServers": {
"coinstats": {
"command": "docker",
"args": ["run", "-i", "--rm", "-e", "COINSTATS_API_KEY", "coinstats/coinstats-mcp"],
"env": { "COINSTATS_API_KEY": "<YOUR_API_KEY>" }
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| COINSTATS_API_KEY | Credential the server authenticates with. | Yes |
| CLOUDFLARE_ACCOUNT_ID | Configuration value read at startup. | Optional |
| YOUR_API_KEY | Credential the server authenticates with. | Yes |
| COINSTATS_API_BASE_URL | Endpoint or connection string the server talks to. | Yes |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.