Skip to main content
Point your AI assistant at the docs instead of its training data. Everything on docs.celo.org is available in machine-readable form — a hosted MCP server your editor can query live, a full-text index for pasting into a chat, and a Markdown version of every page. This matters because model training data goes stale. Celo became an Ethereum L2 in March 2025, contract addresses change, and assistants confidently repeat outdated L1 details. Connecting your tool to these endpoints means answers come from the current docs.

Connect the docs MCP server

The Model Context Protocol lets an AI tool call external tools directly. Celo Docs hosts an MCP server at:
It uses streamable HTTP, needs no authentication, and exposes three tools: It also serves a Celo Developer Playbook skill resource — condensed guidance on deploying contracts, integrating wallets, fee abstraction, running nodes, and governance — which supporting clients load automatically.
This server answers questions about the documentation. To let an assistant read live chain data — balances, blocks, governance proposals — use the Celo MCP Server instead. The two are complementary, and you can run both.
Add the server from your terminal:
That registers it for the current project. To make it available everywhere, add --scope user:
Confirm it connected with /mcp inside Claude Code.Try it:
If you write .mcp.json by hand instead, the type field is required. An entry with a url but no type is read as a stdio server and skipped:

llms.txt and llms-full.txt

Two plain-text files make the whole documentation set readable by any model, with or without MCP support.

llms.txt

An index of every page with its title and a link. Small enough to paste into any chat — the model reads it, then fetches only the pages it needs.

llms-full.txt

The entire documentation set concatenated into one file (~1.5 MB). Use it with long-context models when you want everything available at once.
Reach for llms.txt by default. It costs a fraction of the tokens, and any tool that can follow a link will retrieve the specific pages it needs. Save llms-full.txt for when you genuinely want the full corpus in context and have the window to spare. llms.txt follows the llmstxt.org convention, a proposed standard for exposing site content to language models. llms-full.txt is a common companion file rather than part of that spec. The index is also served at /.well-known/llms.txt for tools that look there. Both files are generated from the live site, so they never go stale.

Copy any page as Markdown

Every page has a contextual menu beside its title:
  • Copy page — copies the page as Markdown, ready to paste as context.
  • View as Markdown — opens the raw Markdown source.
  • Open in ChatGPT / Claude / Cursor / VS Code — starts a session with the page as context, or installs the docs MCP server.
  • Copy MCP server URL — copies https://docs.celo.org/mcp to your clipboard.
You can also skip the menu: append .md to any docs URL to get the Markdown directly. For example, docs.celo.org/build-on-celo/quickstart.md. This works well in scripts and agent tooling that fetches URLs.

Celo MCP Server

Query live chain data — balances, blocks, tokens, NFTs, and governance proposals — from your editor.

Celopedia

A skill that gives your coding assistant curated Celo knowledge: contract addresses, protocols, MiniPay, and grants.

What is MCP?

How the Model Context Protocol works and why AI tools use it.

Vibe Coding Tools

AI-assisted development tools that work well for building on Celo.
Spotted something wrong on a page? Ask your assistant to use the submit_feedback tool — it reports the problem straight to the docs team. You can also open an issue.