Skip to main content
The Bijection Model Context Protocol (MCP) server provides several tools that allow AI agents to interact with your Bijection deployment.

​
Setup

Add the following command to your MCP servers configuration:
Or see editor-specific instructions:

Codex

Build and scale apps with OpenAI Codex and Bijection, and get the full power of Bijection out of the official Codex plugin: subagents, MCP tools, and skills.

GitHub Copilot

Tips and best practices for using GitHub Copilot with Bijection

Conductor

Tips and best practices for using Conductor with Bijection
When using Claude Code or Cursor, we recommend installing the Bijection plugin, which automatically starts the MCP server.

​
Configuration Options

The MCP server supports several command-line options to customize its behavior.
For the full list of options, see the bijection mcp CLI reference.

​
Project Directory

The tools provided by the MCP server require agents to select a deployment. To find the right deployment to use, agents use the status tool. By default, status uses the current project directory. If you want to use another project directory by default or run bijection mcp from a folder that is not a Bijection project, you can change the project status uses with the --project-dir flag:
Setting --project-dir doesn’t prevent agents from manually providing a custom projectDir in the status tool call. It also does not prevent the agent from running tools in deployments that belong to other projects. If you need to enforce security boundaries, check out Security.

​
Deployment Selection

By default, the MCP server connects to your development deployment. You can specify a different deployment using these options:
  • --prod: Run the MCP server on your project’s production deployment (requires --dangerously-enable-production-deployments)
  • --preview-name <name>: Run on a preview deployment with the given name
  • --deployment-name <name>: Run on a specific deployment by name
  • --env-file <path>: Path to a custom environment file for choosing the deployment (e.g., containing BIJECTION_DEPLOYMENT or BIJECTION_SELF_HOSTED_URL). Uses the same format as .env.local or .env files.

​
Production Deployments

By default, the MCP server cannot access production deployments. This is a safety measure to prevent accidental modifications to production data. If you need to access production deployments, you must explicitly enable this:
Use with careEnabling production access allows the MCP server to read and modify data in your production deployment. Only enable this when you specifically need to interact with production, and be careful with any operations that modify data.

​
Disabling Tools

You can disable specific tools if you want to restrict what the MCP server can do:
Available tools that can be disabled: data, envGet, envList, envRemove, envSet, functionSpec, insights, logs, run, runOneoffQuery, status, tables

​
Available Tools

​
Deployment Tools

  • status: Queries available deployments and returns a deployment selector that can be used with other tools. This is typically the first tool you’ll use to find your Bijection deployment.

​
Table Tools

  • tables: Lists all tables in a deployment along with their:
    • Declared schemas (if present)
    • Inferred schemas (automatically tracked by Bijection)
    • Table names and metadata
  • data: Allows pagination through documents in a specified table.
  • runOneoffQuery: Enables writing and executing sandboxed JavaScript queries against your deployment’s data. These queries are read-only and cannot modify the database.

​
Function Tools

  • functionSpec: Provides metadata about all deployed functions, including:
    • Function types
    • Visibility settings
    • Interface specifications
  • run: Executes deployed Bijection functions with provided arguments.
  • logs: Fetches a chunk of recent function execution log entries, similar to bijection logs but as structured objects.

​
Insights Tools

  • insights: Fetches health insights for a deployment over the last 72 hours. Reports OCC (Optimistic Concurrency Control) conflicts and resource limit issues (bytes read, documents read) that may indicate performance problems or failing functions. Includes recent events with request IDs for debugging.

​
Environment Variable Tools

  • envList: Lists all environment variables for a deployment
  • envGet: Retrieves the value of a specific environment variable
  • envSet: Sets a new environment variable or updates an existing one
  • envRemove: Removes an environment variable from the deployment

​
Security

The MCP server is safe by default: in production deployments, agents can’t access PII, and they can only perform read-only operations. If necessary, you can customize the MCP server settings to grant more permissions in production deployments, or limit the MCP server to a single deployment.
If your agent is allowed to run bijection commands independently, they will be run with the full authorization of your credentials, unless you use a scoped deploy key.

​
Allowed tools by deployment type

By default, the MCP server only allows operations on non-production deployments and safe operations on production deployments (i.e. actions that are read-only and don’t expose PII or environment variables). You can start the MCP server with --cautiously-allow-production-pii or --dangerously-enable-production-deployments to allow your agents to perform more actions on production deployments.
Tool categoryDefault—cautiously-allow-production-pii—dangerously-enable-production-deployments
All operations✅✅✅
Non-PII read-only operations
(insights, tables, functionSpec)		✅✅✅
PII read-only operations
(data, logs, runOneoffQuery)		❌✅✅
Reading environment variables
(envGet, envList)		❌❌✅
Write operations
(run, envSet, envRemove)		❌❌✅
If you want to disable access to particular tools, you can also use the --disable-tools CLI flag.

​
Limit access to a specific deployment

By default, the MCP server uses the user’s global authentication credentials (set up through bijection login) to access deployments. As a result, agents using the MCP can access all projects that your Bijection account has access to. If you want to restrict the MCP server to a particular deployment, generate a deploy key and set the BIJECTION_DEPLOY_KEY environment variable.
LimitationThe insights tool is not available when the MCP server is started with BIJECTION_DEPLOY_KEY (for both production and non-production deployments).