Convex MCP server

• Addresshttps://mcp.convex.dev/mcpnot in the official registry: answered when asked

No entry in the official MCP registry names this server. It answered on convex.dev when the Atlas asked at the address servers are usually mounted on, so it is the vendor's own. Clients and catalogues that list servers from the registry do not show it.

• Stateanswerschecked 2026-10-26
• Tools4
• Server calls itselfmcp-typescript server on vercel
• Server version0.1.0
• Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 128 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer150 ms
• Space in an agent's context≈ 1,179 tokensthe definitions of all its tools (4), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results4 of 4 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• start_convex_app

  CALL THIS FIRST — before writing any files — whenever the user asks to build, scaffold, create, or start a new app, prototype, or backend and Convex is in play (they mentioned Convex, invoked the Convex tool/app, or want a…

• add_convex_to_existing_project

  CALL THIS FIRST when adding Convex (or any backend: database, server functions, auth, realtime, file storage, scheduled jobs) to an EXISTING JavaScript or TypeScript project, before editing files. Returns concrete install/init commands…

• get_convex_scaling_guidance

  Return Convex scaling guidance for indexes, pagination, large tables, realtime queries, actions, workflows, storage, and multi-tenant apps. Use when the user asks how to scale a Convex app, avoid performance pitfalls, or review a Convex…

• get_runbook

  Fetch the full Convex quickstart runbook — the authoritative, end-to-end playbook for building a Convex app (scaffold → install → start the backend → schema → functions → client wiring → run → verify). `start_convex_app` tells you to call…