How to Connect AgentEarth to Cursor (MCP Setup, Step by Step)
A hands-on guide to connecting AgentEarth to Cursor over MCP. Add the server, paste one config, verify the connection, and call {{TOOL_COUNT}} tools from natural language inside Cursor.

Tool names in this guide are for reference only and may have changed or been renamed. Please use the latest tools in the tool marketplace when implementing.
Key takeaways
- Add AgentEarth as a remote MCP server in Cursor with a single config block
- Authenticate once with your AgentEarth API key, then call any tool in plain English
- Verify the connection, then run real tasks like market data, search, or image generation
Tools used
Why connecting tools to Cursor is harder than it looks
Cursor is great at writing and editing code, but on its own it can't pull live stock quotes, search the web, scrape a page, or generate an image. The moment you need a real-world capability, you're back to wiring up APIs, juggling vendor keys, and writing glue code — inside an editor that's supposed to keep you in flow.
MCP (Model Context Protocol) fixes this: Cursor is an MCP client, so it can talk to any MCP server through one standard interface. AgentEarth is a remote MCP server that exposes 2,400+ professional tools behind a single connection and a single API key. Connect it once and Cursor can call any of them from natural language.
The setup in four steps
- Get your config — grab your AgentEarth API key and the MCP endpoint.
- Add the server — drop one block into Cursor's MCP settings.
- Verify — confirm the server is connected and tools are listed.
- Use it — describe a task in plain English and let Cursor pick the tool.
Step 1: Get your config
Sign up (new users get 1,000 free credits) and open your account page to copy your API key. You'll also need the AgentEarth MCP endpoint and your key — both are shown on the access guide. Keep the key private; treat it like a password.
Step 2: Add AgentEarth to Cursor
Open Cursor's settings, go to the MCP (Tools / Model Context Protocol) section, and add a new server. Cursor reads MCP servers from a JSON config, so you add one entry pointing at the AgentEarth endpoint and pass your key. A typical remote entry looks like this (use your real endpoint and key from the access guide):
{
"mcpServers": {
"agentearth": {
"url": "https://example.com/mcp",
"headers": { "Authorization": "Bearer AE_API_KEY" }
}
}
}
Save the config and let Cursor reload its MCP servers.
Step 3: Verify the connection
Back in the MCP settings, the agentearth server should show as connected, with a tool count next to it. If it's red or empty:
- Re-check the endpoint URL and that the key is pasted without extra spaces.
- Make sure the
Authorizationheader is present and spelled correctly. - Reload the MCP server (or restart Cursor) after editing the config.
Once it's green, Cursor can see the full catalog.
Step 4: Use it from natural language
You don't call tools by name — you describe what you want and Cursor selects the right one. In the chat panel, try:
- use ae to check the latest price for AAPL
- use ae to search the web for recent news about example.com
- use ae to generate a hero image for a landing page
Cursor finds the matching tool in the AgentEarth catalog, runs it, and uses the result in its answer — no per-tool integration code.
Those three requests use a market-data tool (such as ae_twelvedata_get_quote), a search tool (such as ae_serper_search) and a text-to-image tool (such as ae_openai_gpt_image_2_5) — the agent picks them on its own.
Cursor vs Claude Code: what's different
The underlying connection is the same MCP protocol; only the UI for adding a server differs.
| Claude Code | Cursor | |
|---|---|---|
| Where you add it | CLI command / config file | Settings → MCP panel |
| Config format | JSON MCP entry | JSON MCP entry |
| Auth | API key in header | API key in header |
| Calling tools | Natural language | Natural language |
| Tool catalog | Same 2,400+ | Same 2,400+ |
If you've already connected AgentEarth in Claude Code, the Cursor steps will feel familiar — same endpoint, same key, different menu.
FAQ
Is the setup the same as Claude Code? Nearly. Both use the same MCP endpoint and API key; the only difference is where you paste the config — a settings panel in Cursor versus a config file or command in Claude Code.
Does it cost anything to connect? Connecting is free, and new accounts start with 1,000 credits. You only spend credits when a tool actually runs.
How do I verify it's working? Check that the agentearth server shows as connected with a tool count in Cursor's MCP settings, then run a simple request like use ae to check the price for AAPL and confirm you get a live result.
Get started
- Sign up — new users get 1,000 free credits.
- Add AgentEarth to Cursor's MCP settings with your API key.
- Ask in plain English and let Cursor run the right tool.
