Skip to main content
Connect an AI assistant to explore your databases, query records and make changes in Rootset. Sign in through your browser and choose the access it receives. You do not need an API key.

Find your connection settings

  1. Open Account Settings → MCP Guide in Rootset.
  2. Choose your client from the App menu.
  3. Copy the configuration shown for your installation.
The guide includes settings for Codex, Claude Code, Cursor, VS Code and other MCP clients. It uses your installation’s API URL, so you do not have to build the endpoint yourself.

Connect a client

The server address is your public API URL followed by /mcp:
Replace the example address below with your installation’s API address. The web application’s address is separate.
For Codex, the second command starts browser sign-in. In Claude Code, open /mcp, select Rootset and authenticate. For other clients, use the configuration from MCP Guide and follow the client’s sign-in prompt. The client must support Streamable HTTP and OAuth. See the Codex MCP documentation for its configuration options.

Approve access

In the browser, review the client name and choose the access to grant: The form starts with Read-only. Available access is limited by your current workspace role. Administrator access requires an administrator account and recent identity confirmation. Role changes and membership removal revoke existing connections. Sign in again to approve access under your new role.

Try the connection

Start with a read-only request:
With Write access and a Products table, you can try:
Review the result in Rootset. For operations that return a background job, such as exports or schema changes, the assistant should check the job’s result before reporting completion. The MCP reference lists each tool’s arguments, permissions and examples.

Manage connections

Open Account Settings → MCP Connections to see approved clients, their permissions and when they were used. Select Revoke to remove a client’s access. Connect and sign in again if you want to grant access later. Use API keys for scripts and services that call the REST API directly.