Skip to main content
Agentset provides two MCP servers:
  • Hosted MCP server — a remote server at https://api.agentset.ai/mcp that exposes the full Agentset platform. Agents can create namespaces, ingest data, search, chat, and manage your organization autonomously.
  • Local MCP server — the @agentset/mcp npm package, a lightweight stdio server that searches a single namespace.

Hosted MCP server

The hosted server uses streamable HTTP and authenticates with your API key as a bearer token:
To scope requests to a single tenant in multi-tenant setups, add an optional x-tenant-id header. See Data Segregation. With the full toolset, an agent can bootstrap a RAG stack end-to-end without touching the dashboard: create a namespace, request upload URLs, ingest documents, monitor the ingest job, then search and chat over the results.

Claude Code

Claude Desktop and claude.ai

Go to Settings → Connectors → Add custom connector and enter https://api.agentset.ai/mcp as the server URL. The server authenticates with your API key as a bearer token.

Cursor

Add the server to .cursor/mcp.json in your project (or ~/.cursor/mcp.json globally):

Tools

Tool names are snake_case and map one-to-one to the REST API operations. Coverage by area:

Local MCP server

The @agentset/mcp package runs on your machine over stdio and exposes a single search tool scoped to one namespace. Use it when an agent only needs read access to your data. Run it with your preferred package manager:

Adding to Claude

To add the local MCP server to Claude, include the following configuration in your Claude settings:

Tips

Pass the namespace id as an environment variable:
Pass a custom tool description:
Pass a tenant id:

Next steps