Convex MCP Server, Convex's own MCP server

• Lists your tables with their declared and inferred shapes

  Returns every table in a deployment with the schema you declared and the shape Convex has seen in the stored data. Good for getting oriented in an unfamiliar backend.

  Try: “What tables does my dev deployment have, and what fields are in each?”

  Read · tables

• Reads a page of documents from one table

  Reads documents from a table in the order you choose, one page at a time. It returns a cursor so the assistant can ask for the next page.

  Try: “Show me the 20 newest rows in the messages table.”

  Read · data

• Runs a throwaway read-only query you describe in words

  Runs a short piece of JavaScript as a query against your data. Convex describes it as read-only, so it can filter, join and count but not change anything.

  Try: “Count how many users signed up each day this week.”

  Read · runOneoffQuery

• Shows every deployed function and what it accepts

  Returns each deployed function with its type (query, mutation or action), whether it is public or internal, and its argument and return types.

  Try: “List all public mutations in my deployment and what arguments they take.”

  Read · functionSpec

• Pulls recent function logs, including errors

  Fetches one batch of recent function runs with their log lines. Set it to failures only to see error messages and stack traces. It does not keep streaming.

  Try: “Show the last failed function calls and their stack traces.”

  Read · logs

• Reports conflicts and heavy reads from the last 72 hours

  Summarizes health problems in the last three days: mutations that keep colliding on the same document, and functions that read too much data. Each comes with request IDs for debugging. Not available when you limit the server with a deploy key.

  Try: “Why is my app slow? Check for performance problems on the dev deployment.”

  Read · insights

• Runs one of your deployed functions with arguments you give

  Calls a query, mutation or action you already deployed, and returns its result and logs. A mutation or action can change or delete data, so this is the tool that can write.

  Try: “Run the seedDemoData mutation on my dev deployment.”

  Write · run

• Lists environment variable names, optionally with values

  Lists the environment variables set on a deployment. It shows names only, unless the assistant asks for values too.

  Try: “Which environment variables are set on my dev deployment?”

  Read · envList

• Reads the value of one environment variable

  Returns the current value of a single environment variable on a deployment, which can include API keys.

  Try: “What is OPENAI_API_KEY set to in dev? Just check that it is set.”

  Read · envGet

• Sets or changes an environment variable

  Creates a new environment variable or overwrites an existing one on the chosen deployment.

  Try: “Set SITE_URL to http://localhost:3000 on my dev deployment.”

  Write · envSet

• Deletes an environment variable

  Removes an environment variable from the chosen deployment.

  Try: “Remove the unused STRIPE_TEST_KEY variable from dev.”

  Delete · envRemove

• Used by the assistant behind the scenes

  Finds your Convex projects and the deployments you can use

  Looks up the development and production deployments for a project folder. The assistant uses the result to pick which deployment every other tool should act on.

  Try: “Which Convex deployments does this project have?”

  Read · status

Watch out for

• It can run functions that change or delete data

  The run tool calls any deployed function, including mutations, on every development deployment by default. Disable it with --disable-tools if you only want to look. docs.convex.dev

• Production flags allow writes to live data

  --dangerously-enable-production-deployments also allows run, envSet, envRemove and reading env values in production. Leave it off unless you need it, and prefer --cautiously-allow-production-pii for read-only access to production data. docs.convex.dev

• It can delete and overwrite environment variables

  On development deployments the assistant can set or remove variables. Add envSet and envRemove to --disable-tools if that is not wanted. docs.convex.dev

• It can read secrets stored in environment variables

  envGet and envList (with values) return API keys on non-production deployments by default. Disable both if your dev deployment holds real keys. docs.convex.dev

• By default it can reach every project on your account

  It uses your login, so the assistant can pick any project you own. The --project-dir flag does not stop that. Set CONVEX_DEPLOY_KEY to a deploy key to limit it to one deployment. docs.convex.dev

• Production is protected by default

  Without those flags, production allows only read tools that do not expose personal data (insights, tables, functionSpec). docs.convex.dev