MCP / MODEL CONTEXT PROTOCOL

Your agents.
Your data. Connected.

Connect AI agents to your Singlebase project through MCP. Discover collections, work with documents, and get answers with sources—all within the access you assign.

Agent → Singlebase / MCP
AGENT REQUEST

What is our refund policy?

Use project knowledge to answer with sources.

Toolask_documents
KnowledgeAssigned support docset
AccessScoped agent key
ANSWER

Unused items can be returned within 30 days.

Source: Returns policy

01

Tools ready for agents

Six named tools with descriptions and examples help your agent discover data and take action.

02

Your scope, enforced

Available tools and collection choices follow the agent key. Gateway checks enforce access on every call.

03

One shared gateway

Keep the same ownership rules, automations, rate limits, and usage tracking as your application’s API calls.

Six tools.
A connected workflow.

Give agents the operations they need, from finding context to keeping records up to date.

list_collections

Discover your data

Let agents inspect collection descriptions, fields, indexes, and the permissions assigned to their key.

Permission: Any collection permission
search_documents

Find the right records

Query documents with filters or full-text search, with field selection, sorting, and pagination.

Permission: read · search for full-text queries
insert_documents

Add new knowledge

Insert one document or a batch. Collection create automations run through the normal gateway.

Permission: write
update_documents

Keep records current

Update a document by ID or change matching records with a filter, using the same application automations.

Permission: write
delete_documents

Archive what is finished

Archive documents by ID, a list of IDs, or a filter, with the normal archive retention.

Permission: delete
ask_documents

Get answers with sources

Ask questions grounded in readable collections or enabled, agent-accessible docsets and receive a written answer with sources.

Permission: ai.chat + an available knowledge source

Set the scope.
Connect your client.

  1. Create an agent key

    Choose the collections and feature permissions your agent needs. MCP authenticates each request with an agk_… key.

  2. Enable MCP for your project

    Turn on MCP in the console’s project settings. It is disabled by default and requires platform availability.

  3. Add your project endpoint

    Connect your client with the endpoint and agent key. It discovers the tools available to that key and calls them over stateless HTTP.

CONNECT YOUR TOOLS

Bring your agent runtime.

Connect Claude Code or Cursor to the remote HTTP endpoint. Claude Desktop and other stdio clients can connect through the mcp-remote bridge.

Use an agent key for authentication. MCP has no user login or OAuth flow. Keep the configuration containing your key private.

Claude Code / HTTP connectionSETUP
claude mcp add --transport http singlebase \
  'https://v1.api.singlebase.io/mcp/<ENDPOINT_KEY>' \
  --header 'Authorization: Bearer agk_<AGENT_KEY>'
Replace the endpoint and agent-key placeholders with your own.