# Celo Docs MCP server
> Search and read the Celo developer documentation, and report documentation problems to the docs team.
- Listing: https://mcp.tc/i/celo-docs
- Connect: use the server's own URL `https://docs.celo.org/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: none
- Category: [Docs & Knowledge](https://mcp.tc/c/docs-knowledge)
- Vendor: Celo
- Homepage:
## About
Connects to the Celo Docs site, covering the Celo Ethereum L2, Mini Apps, stablecoin payments, agents and node operation. You can search the knowledge base for guides, code examples and API references, and read full pages through a read-only virtual filesystem of the documentation.
The server runs as a hosted streamable HTTP endpoint at https://docs.celo.org/mcp. No sign-in or API key is needed. Apart from the feedback tool, it is read-only and limited to published Celo Docs content.
## What it can do
- Search Celo docs for guides, code examples and API references
- Read full documentation pages by path
- Run grep-style keyword searches over the docs
- Submit feedback about incorrect or outdated pages
## Tools (3)
- `search_celo_docs`: Search the Celo Docs knowledge base for guides, code examples and API references with links. (read-only)
- `query_docs_filesystem_celo_docs`: Run read-only shell-like commands (head, cat, rg) on a virtual filesystem of the docs pages. (read-only)
- `submit_feedback`: Report an incorrect, outdated or incomplete documentation page to the docs team.
## Example prompts
- "How do I build a Mini App for MiniPay on Celo?"
- "Search the Celo docs for paying gas fees in stablecoins."
- "What are the Celo network chain IDs and RPC URLs?"
- "Show the docs page on running a Celo node."
## Install
### Claude Code
1. Run this in a terminal, in your project folder:
```bash
claude mcp add --transport http celo-docs https://docs.celo.org/mcp
```
2. Start Claude Code and type `/mcp`. **celo-docs** should show as connected.
Add `--scope user` to make it available in every project, not just this one.
### Claude Desktop
1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.
2. Name it **Celo Docs** and paste this URL:
```url
https://docs.celo.org/mcp
```
3. Click **Add**. Its tools appear in the chat’s tools menu.
Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.
### claude.ai
1. Open the connector form on claude.ai. This button fills in the name and URL for you:
[Add to claude.ai]() (opens connector settings)
2. Check that the URL reads `https://docs.celo.org/mcp` and click **Add**.
3. Turn it on in a chat from the tools menu.
Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.
### ChatGPT
1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.
2. Enter a name for the server.
3. Under **Connection**, paste `https://docs.celo.org/mcp` as the server URL, then for authentication choose **No authentication**.
4. Check **I understand and want to continue**, then select **Create as a plugin**.
Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).
### Cursor
[Add to Cursor]() (opens Cursor)
Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):
`mcp.json`:
```json
{
"mcpServers": {
"celo-docs": {
"url": "https://docs.celo.org/mcp"
}
}
}
```
### VS Code
[Install in VS Code]() (opens VS Code)
Or from a terminal:
```bash
code --add-mcp '{"name":"celo-docs","type":"http","url":"https://docs.celo.org/mcp"}'
```
Or commit it to the repo in `.vscode/mcp.json`:
`.vscode/mcp.json`:
```json
{
"servers": {
"celo-docs": {
"type": "http",
"url": "https://docs.celo.org/mcp"
}
}
}
```
### Devin Desktop
1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):
`mcp_config.json`:
```json
{
"mcpServers": {
"celo-docs": {
"serverUrl": "https://docs.celo.org/mcp"
}
}
}
```
2. Refresh the MCP server list in Cascade.
Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.
### Codex
```bash
codex mcp add celo-docs --url https://docs.celo.org/mcp
```
Or edit `~/.codex/config.toml` directly:
`config.toml`:
```toml
[mcp_servers.celo-docs]
url = "https://docs.celo.org/mcp"
```
### Gemini CLI
```bash
gemini mcp add --transport http celo-docs https://docs.celo.org/mcp
```
This adds it to the current project. Add `-s user` to use it everywhere.
### Any client
Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.
```json
{
"mcpServers": {
"celo-docs": {
"type": "http",
"url": "https://docs.celo.org/mcp"
}
}
}
```
Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.
Client only starts local servers? Bridge it with `npx -y mcp-remote https://docs.celo.org/mcp`.
## Recent changes
- 2026-11-13 20:52 UTC: 1 tool changed. Source: automatic check. Changed: query\_docs\_filesystem\_celo\_docs.
- 2026-10-27 20:44 UTC: Tracking started: 3 tools read. Source: automatic check.
More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/celo-docs#history (Atom feed: https://mcp.tc/i/celo-docs/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.
## Details
- Server version: 1.0.0
- MCP protocol version: 2026-07-28
- Last checked: 2026-11-15 (reachable)
- Listed: 2026-10-27
- Updated: 2026-10-27
---
Source: https://mcp.tc/i/celo-docs (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report