Connect your AI

Connect your AI client once. After that, your agent can create objects, store records and query them by itself. You only ask in plain language.

AgentDB is a remote MCP server. Every client connects to the same address:

https://app.agentdb.link/mcp

There are three ways to connect. Pick the first one your client supports.

#claude.ai and Claude Desktop

1. In Claude, open Customize, then Connectors, then Add custom connector.
2. Enter the URL https://app.agentdb.link/mcp. Keep the authentication on OAuth.
3. Claude opens an AgentDB page. Approve the connection there.
4. Back in Claude, turn the connector on in a chat. The AgentDB tools are now available.

On the approval page you have three choices:

• I'm new: create a workspace. AgentDB creates an account and a workspace for you.
• Use my API key. You paste your key once. Claude never sees it.
• Email me a sign-in link. AgentDB emails a link to your account address.

Claude Desktop uses the connectors of your Claude account. You can also use agentdb mcp install claude-desktop, described below.

#ChatGPT

ChatGPT connects with OAuth, like claude.ai. Custom connectors need a paid ChatGPT plan. On a Business or Enterprise plan, an admin may have to allow them.

1. In ChatGPT, add a custom MCP server or connector. The menu name depends on your ChatGPT version.
2. Name it AgentDB and enter the URL https://app.agentdb.link/mcp.
3. Choose OAuth as the authentication.
4. Approve the connection on the AgentDB page that opens.
5. In a chat, enable the AgentDB connector and ask: "Using AgentDB, show my workspaces."

#Claude Code, Cursor and other local tools

The agentdb CLI sets up local AI tools for you. Your key stays in the operating system's credential store. No key is written into the tool's configuration file.

1. Install the CLI and log in. See Get started.
2. Register AgentDB in your tool:

agentdb mcp install claude

Replace claude with the name of your tool:

Then restart the tool or start a new chat. The command prints the exact next step for your tool.

If the tool already has a server named agentdb, the command stops. Add --force to replace it. Run agentdb mcp list to see which tools have AgentDB. Run agentdb mcp remove <tool> to take it out again.

Claude Code can also use the official AgentDB skill. It teaches the agent good habits with AgentDB:

agentdb skill install claude

#Any other MCP client

Any client that supports Streamable HTTP with custom headers works. Give it the URL and this header:

Authorization: Bearer <your API key>

For example, Claude Code without the CLI:

claude mcp add --transport http agentdb https://app.agentdb.link/mcp --header "Authorization: Bearer <your API key>"

Write Bearer, one space, then the full key. Do not add quotes inside the value.

#Choose the workspace

An account can have several workspaces. Every data tool takes an optional workspace argument: an id, a slug or the exact name. Without it, the tool uses your default workspace.

Tell your agent which workspace to use. For example: "In my Example CRM workspace, list the contacts." The agent resolves the name once with workspace_select.

#Use a short tool list

AgentDB has more than 200 operations. Some clients work better with fewer tools. Add ?tools=compact to the URL:

https://app.agentdb.link/mcp?tools=compact

Clients that send headers can send x-agentdb-tools: compact instead. The compact list holds 16 everyday tools, such as schema_inspect, records_create, records_query and records_search. It also holds agentdb_capabilities and agentdb_execute. Every other operation stays available through agentdb_execute.

#Discover operations

Your agent does not need to scan the whole tool list. It asks agentdb_capabilities instead. A search in plain words returns the best matching operations:

{"tool": "agentdb_capabilities", "arguments": {"search": "attach a file to a record"}}

Name one operation to get its full input schema and an example:

{"tool": "agentdb_capabilities", "arguments": {"operation": "records_query"}}

Then run any operation with agentdb_execute. It has the same permissions, checks and results as the operation's own tool:

{"tool": "agentdb_execute", "arguments": {"operation": "workspace_info", "arguments": {}}}

Without arguments, agentdb_capabilities returns a short index of all categories.

#Connected apps

Every AI client you connected by signing in appears under Connected apps. You can see what each one can reach and end its access.

1. Sign in to the app at https://app.agentdb.link/app.
2. Open Settings, then Connected apps.
3. Each row shows the client name, the workspaces it reaches, when you connected it and when it was last used.
4. Choose Disconnect… on a row and confirm.

The client loses access at once. Its access tokens and refresh tokens stop working. To use it again, connect it again.

Keys used by the CLI and by local tools are API keys, not connected apps. agentdb logout removes the saved key. It also revokes a key that agentdb login issued.

#Check the connection

Ask your agent: "Using AgentDB, show the workspace info and the schema." The agent calls workspace_info and schema_inspect.

Does your agent miss a tool that this documentation names? See My AI client does not see a new tool.