docs(build-with-ai): add Celina SDK, MCP, hosted MCP, and API pages

[andrewkimjoseph]

The hole, and the fix

build-on-celo/build-with-ai/ had no page for Celina, a third-party Celo-native AI-agent stack (SDK, local stdio MCP server, hosted MCP endpoint, REST API) that shares one tool catalog across all four surfaces. This adds:

• build-on-celo/build-with-ai/celina/index.mdx — Index page (intro + CardGroup) linking to the 4 detail pages
• build-on-celo/build-with-ai/celina/sdk.mdx, mcp.mdx, hosted-mcp.mdx, api.mdx — Guide pages (Prerequisites → How it works → task sections → Troubleshooting → Resources → Related), each with real, verified content pulled from the upstream repos (package.json, README.md, source error strings) — no invented details
• A new "Celina" group in docs.json navigation, nested under "Build with AI"
• A cross-link bullet in mcp/index.mdx and a short new "Give Agents a Wallet with Celina" section in overview.mdx (per AGENTS.md §8 rule 9 — new agent-relevant pages get listed on the overview page)

Troubleshooting sections quote verbatim strings I confirmed in the source: e.g. celina-mcp's README troubleshooting table (spawn celina-mcp ENOENT, Cannot find package 'ox', etc.), celina-sdk's token/simulation/Mento/Uniswap error messages, and celina-api's JSON error shapes ({"error":"Unknown tool: ${name}"} etc.).

What this does NOT do / residual risk

• Does not modify any existing page's stated facts (chain ID, block time, etc.) — those are only linked, never restated, per AGENTS.md §7.
• Does not add Celina to the AGENTS.md "one fact, one page" canonical-facts table — Celina is third-party, not a Celo-core fact.
• Does not verify Celina's own on-chain addresses against the chain — this PR only documents install/usage flows and error strings, not contract addresses (none are listed).
• I do not maintain Celina; content reflects the state of the linked repos at the time of writing and may drift if those repos change.

Judgement calls

• No GitHub issue backs this change (net-new content addition, not a tracked bug) — branch is named without an issue number: andrewkimjoseph/add-celina-ai-stack-docs.
• Page-type classification (Index for the landing page, Guide for the 4 detail pages) is my reading of AGENTS.md §3's page-anatomy table.
• Placed the new "Celina" nav group after "MCP Servers" and before the "Use Cases" page, inside "Build with AI" — a nav-order choice, easy to move if a maintainer prefers otherwise.

Issues

Closes #
Refs #

Stacking / conflicts

Branched off main, independent of any other open PRs. Touches docs.json and build-on-celo/build-with-ai/mcp/index.mdx and overview.mdx — flagging in case another in-flight PR touches the same files.

Verification evidence

$ mint broken-links
⠋ checking for broken links...
success no broken links found

Ran on this branch's head after all edits. No existing pages' content or facts were changed — only additive content and two small cross-link insertions.

Remaining ops steps

• none

Checklist

• Title is the commit message I want on main
• mint broken-links passes on this branch head (see Verification evidence) — this repo's CI-equivalent check for a docs PR
• No secrets in the diff
• Judgement calls flagged above
• N/A: test/mutation-count/lockfile/wallet-tree/money-path checklist items — this is a docs-only content PR, no code changes
• Questions for the maintainer: none

Made with Cursor

[GigaHierz]

Hi @andrewkimjoseph ,

thank you for creating this PR.

could you please consolidate the information in one page, under the Celo MCP page? And instead of going into detail, best to provide an overview with links to the relevant documentation

thank you

[andrewkimjoseph]

Thanks for the feedback! Done — consolidated everything into a single page, build-on-celo/build-with-ai/mcp/celina.mdx, added as a third entry in the "MCP Servers" group right next to "Celo MCP Server". It's now just a short pitch + a card for each surface (SDK, MCP, hosted MCP, API) + a Resources table, all linking out to Celina's own GitHub/GitBook/website docs instead of duplicating install steps and detail here.

[GigaHierz]

Nice addition — one small non-blocking suggestion:

Sidebar label. In the "MCP Servers" nav group, the bare sidebarTitle: "Celina" doesn't give a reader much context next to "Celo MCP Server", and this page actually covers more than an MCP server (SDK + local MCP + hosted MCP + REST API). Consider a short descriptor, e.g. sidebarTitle: "Celina (agent wallet)", so its purpose reads at a glance in the sidebar.

Separately, FYI: the neighboring Celo MCP Server page was stale (missing the remote HTTP transport and several tools) — refreshed in #2288.

[andrewkimjoseph]

Good call — updated sidebarTitle to Celina (agent wallet) so it reads clearly next to Celo MCP Server in the sidebar. Page title stays "Celina"; only the nav label changed.

Thanks for the approval and the #2288 heads-up on the Celo MCP Server refresh.

[GigaHierz]

Approving. Verified everything the pages assert:

usecelina.xyz                          200
github.com/andrewkimjoseph/celina-sdk        200
github.com/andrewkimjoseph/celina-mcp        200
github.com/andrewkimjoseph/celina-mcp-remote 200
github.com/andrewkimjoseph/celina-api        200
andrewkimjoseph.gitbook.io/celina-sdk        200
andrewkimjoseph.gitbook.io/celina-api        200

npm view @andrewkimjoseph/celina-sdk version -> 0.25.16
npm view @andrewkimjoseph/celina-mcp version -> 0.18.24

mintlify broken-links green, docs.json parses. The consolidation you did is exactly right — one page, cards out to your own docs, no duplicated install steps to go stale here.

I pushed one commit rather than leave a comment, since it is a house-style call rather than a question about your project. On build-with-ai/overview, every H2 names a Celo capability — x402 and MPP, fee abstraction, attribution — so ## Give Agents a Wallet with Celina put a single third-party project at that level. #2255 just removed that exact pattern for thirdweb, and it would be odd to reintroduce it here. The heading now names the job (## Giving an agent a wallet, sentence case per AGENTS.md) and mentions the direct viem route alongside Celina, so it reads as an answer rather than a placement. Your page, the MCP Servers nav entry and the index bullet are untouched.

Revert that commit if you disagree — it is one paragraph and I would rather discuss it than have it stand by default.

Note for sequencing: #2288 edits the same list block in mcp/index.mdx, so whichever lands second will need a rebase. This one is ready now and #2288 is blocked on an upstream release, so this goes first.