MCP Directory

How to add Agentset MCP to Cursor

Retrieve from your Agentset RAG knowledge base directly inside Claude, Cursor, and other MCP clients. Paste the config into ~/.cursor/mcp.json and restart Cursor.

Last updated June 14, 2026 · 30★ · stdio · apikey

Cursor config for Agentset MCP

npx @agentset/mcp
{
  "mcpServers": {
    "agentset-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@agentset/mcp@latest"
      ],
      "env": {
        "AGENTSET_API_KEY": "agentset_xxx",
        "AGENTSET_NAMESPACE_ID": "ns_xxx"
      }
    }
  }
}

Setup steps

  1. 1Open Cursor → Settings → MCP → Add new MCP server (or edit ~/.cursor/mcp.json directly).
  2. 2Paste the Agentset MCP config below into the "mcpServers" object.
  3. 3Fill in placeholder secrets, then save.
  4. 4Cursor reloads MCP servers automatically — check Settings → MCP for a green status dot.
  5. 5Ask Cursor to use one of Agentset MCP's tools to confirm it's connected.

Before you start

  • Node.js >= 18.17.0
  • An Agentset account and API key (AGENTSET_API_KEY)
  • An Agentset namespace id (AGENTSET_NAMESPACE_ID or the --ns flag) with ingested documents

What Agentset MCP can do in Cursor

knowledge-base-retrieve

Search the Agentset knowledge base (namespace) for data matching a query. Accepts a `query` string, an optional `topK` (1-100, default 10) for the maximum number of results, and an optional `rerank` boolean (default true) to reorder results by relevance. Returns the matching document text chunks. The tool description can be customized via the -d flag.

Security

Requires an Agentset API key (AGENTSET_API_KEY), which grants access to your Agentset account data. Provide it via the env block of your MCP client config and keep it out of source control. The server queries the namespace specified by AGENTSET_NAMESPACE_ID (or --ns); scope the API key and namespace appropriately, and use the tenant id (-t) to isolate data in multi-tenant deployments.

Agentset MCP + Cursor FAQ

Where is the Cursor config file?

Cursor reads MCP servers from ~/.cursor/mcp.json. Paste the Agentset MCP config there under the "mcpServers" key and restart the client.

Is Agentset MCP safe to use with Cursor?

Requires an Agentset API key (AGENTSET_API_KEY), which grants access to your Agentset account data. Provide it via the env block of your MCP client config and keep it out of source control. The server queries the namespace specified by AGENTSET_NAMESPACE_ID (or --ns); scope the API key and namespace appropriately, and use the tenant id (-t) to isolate data in multi-tenant deployments.

How do I tell the server which knowledge base to query?

Pass the namespace id with the --ns flag (e.g. `--ns your-namespace-id`) or set the AGENTSET_NAMESPACE_ID environment variable. The API key is provided via AGENTSET_API_KEY.

Can I use it in a multi-tenant setup?

Yes. Pass a tenant id with the -t/--tenant flag (e.g. `-t your-tenant-id`) so searches are scoped to that tenant's data.

Can I customize how the tool appears to the assistant?

Yes. Use the -d/--description flag to override the default tool description, e.g. `-d "Your custom tool description"`, which helps the model understand what knowledge it is querying.

View repo Full Agentset MCP page