# get-convex/convex-backend

**Category:** 🗄️ Databases  
**Repository:** https://github.com/get-convex/convex-backend  
**GitHub Stars:** 12705  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/get-convex-convex-backend-2

## Description
Convex database integration to introspect tables and functions and run one-off queries.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What get-convex/convex-backend does

The get-convex/convex-backend MCP server gives an MCP-compatible agent access to selected Convex backend operations. Its documented purpose is to introspect tables and functions and execute one-off queries. That makes it relevant for development, debugging, and data exploration tasks where an agent needs visibility into an existing Convex application.

Convex is an open-source reactive database that also provides a place to write server functions and client libraries. The backend is built around strongly consistent data access and server-side business logic written in TypeScript. In the confirmed 🗄️ Databases category, this MCP server is best understood as an agent-facing interface to Convex rather than a general-purpose database connector.

## How it works

The server presents Convex inspection and query operations as MCP capabilities. An agent can use those capabilities to examine the available table structure, inspect backend functions, or issue a one-off query when it needs a particular result. The supplied material does not document the MCP transport, authentication flow, request schema, or response format, so those details should be checked in the repository or its implementation before deployment.

The intended workflow is exploratory: first identify the relevant Convex tables or functions, then use a query to retrieve data needed for the task. Function introspection can help an agent understand the backend surface before it works with application data. The available description does not state that the server creates tables, edits schemas, invokes mutations, or changes application code, so those behaviors should not be assumed.

## Tools and capabilities

The documented capabilities are:

- Inspect Convex tables and their available structure.
- Introspect Convex backend functions.
- Run one-off queries against Convex data.

These capabilities suit questions such as which tables exist, what backend functions are available, or what data matches a specific ad hoc query. The material does not provide formal tool names, argument definitions, query-language details, or examples, so integrations should allow for implementation-specific naming and validation.

The underlying Convex project supports cloud and self-hosted deployments, but the provided material does not establish which deployment types this MCP interface supports. It also does not document whether queries are read-only or whether any operation can trigger server-side effects. Treat the listed inspection and query functions as the complete confirmed scope until the implementation documents more.

## Limitations and notes

The source material is primarily documentation for the Convex backend project, not a complete MCP installation guide. It does not specify required environment variables, client setup, supported MCP hosts, permissions, credentials, or operational limits for the get-convex/convex-backend MCP server. Those omissions matter when evaluating it for production use.

Convex itself can be used through its cloud platform or self-hosted product. The repository describes Docker and prebuilt-binary options for self-hosting, along with support for tools and platforms such as Neon, Fly.io, Vercel, Netlify, RDS, SQLite, and Postgres. These are Convex deployment details; the supplied material does not confirm that this MCP server directly integrates with each one.

For a precise setup, review the repository implementation and any package-specific documentation for connection requirements, authorization, transport, and tool definitions. Use the server when table introspection, function discovery, and isolated Convex queries are the primary requirements.

_Full upstream README: https://allmcps.com/mcp/get-convex-convex-backend-2/readme_