Add AGNT venue tools to Cursor via MCP
One config entry gives Cursor's agent real-time venue search, memory, and booking tools.
Cursor ships a built-in MCP client. This walkthrough shows you how to point it at AGNT's MCP server so your Cursor agent can search venues, read user memory, and query the knowledge graph — all from the chat sidebar.
Prerequisites
- An AGNT developer API key (get one at /developers).
- Cursor IDE installed (version 0.45+ with MCP support).
What you're building
By the end of this walkthrough, Cursor's agent will have access to AGNT's MCP tools: `search_venues`, `list_venues`, `read_user_memory`, and `query_knowledge_graph`. These appear as callable tools in the agent's context, discovered automatically via the MCP handshake.
There's no extension to install. Cursor reads MCP server definitions from its settings, negotiates schemas at startup, and exposes them to the model.
Step 1 — Get an AGNT API key
Head to [/developers](/developers) and generate a developer key with read scopes for `memory.read`, `venues.read`, and `graph.read`. The key starts with `ag_` — store it in your password manager.
Step 2 — Add AGNT to Cursor's MCP config
Open Cursor Settings → Features → MCP Servers → Add New MCP Server. Use these values:
{
"name": "agnt",
"url": "https://api.agntdot.com/mcp/sse",
"headers": {
"Authorization": "Bearer YOUR_AGNT_API_KEY"
}
}Replace `YOUR_AGNT_API_KEY` with your actual key. Cursor stores this in its local config — the key never leaves your machine except when making API calls.
Step 3 — Verify the handshake
Open a new Cursor chat and ask: "what MCP tools do I have from the agnt server?" The agent should list the available tools. If it doesn't, check the MCP server URL and Authorization header in Cursor's settings.
Step 4 — Use venue tools in your workflow
Ask Cursor: "find me a coworking-friendly cafe in Canggu with good wifi". The agent will call `search_venues` and return real results from the AGNT network. You can use this to enrich your code context — for example, when building a venue page, ask the agent to pull real data from AGNT's graph.
Why this matters
The same MCP config works across Cursor, Claude Code, Windsurf, and any future MCP-compatible client. You're not locked into one IDE — the protocol is the integration layer, not the vendor.