Developers
Quickstart
Five minutes from API key to your agent answering questions about your data. Pick the client you use — the rest is paste-and-go.
Step 0
Get an API key.
mantle is currently in pre-release. Once access opens, sign in at app.mantleai.dev, create a project, and copy the mk_… bearer token. The same key will work across REST and MCP.
You'll then be able to connect at least one source — Drive, Gmail, Slack, or Dropbox — so you have something to query.
Client
Claude Desktop
Claude Desktop talks MCP over stdio, so we use mcp-remoteto bridge to Mantle's HTTP MCP endpoint. Open Claude Desktop → Settings → Developer → Edit Config and paste:
{
"mcpServers": {
"mantle": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.mantleai.dev/mcp",
"--header",
"Authorization:Bearer mk_your_key_here"
]
}
}
}Save, restart Claude Desktop. The Mantle tool catalog appears in the tool picker. Ask “What did Maren and the Acme team last discuss?” — Claude will resolve the entity and pull from every connected source.
Client
Cursor
Cursor speaks HTTP MCP natively — no bridge needed. Open ~/.cursor/mcp.json and add:
{
"mcpServers": {
"mantle": {
"url": "https://mcp.mantleai.dev/mcp",
"headers": {
"Authorization": "Bearer mk_your_key_here"
}
}
}
}Reload Cursor. The Mantle tools appear in the agent panel.
Client
Claude Code
A single CLI command registers Mantle as an HTTP MCP server:
claude mcp add mantle \ --transport http \ --url https://mcp.mantleai.dev/mcp \ --header "Authorization:Bearer mk_your_key_here"
Run claude mcp listto confirm. Mantle's tools are now available in any Claude Code session.
Anything else
Custom agents.
Any MCP-compatible agent can connect to Mantle. Point it at https://mcp.mantleai.dev/mcp with your API key as a bearer token. For server-side integrations that don't need MCP, use the REST API directly — see the API reference.
Stuck? Drop into our Discord or email hello@mantleai.dev.