Cursor

Cursor supports remote MCP servers through mcp.json.

Option 1: Add both servers globally

Create ~/.cursor/mcp.json to make the AskElephant servers available in every workspace:

1
{
2
  "mcpServers": {
3
    "AskElephant": {
4
      "url": "https://app.askelephant.ai/mcp"
5
    },
6
    "AskElephant API Docs": {
7
      "url": "https://docs.askelephant.ai/_mcp/server"
8
    }
9
  }
10
}

Option 2: Add them per project

Create .cursor/mcp.json in a specific repository if you only want these tools available for that project:

1
{
2
  "mcpServers": {
3
    "AskElephant": {
4
      "url": "https://app.askelephant.ai/mcp"
5
    },
6
    "AskElephant API Docs": {
7
      "url": "https://docs.askelephant.ai/_mcp/server"
8
    }
9
  }
10
}

Authenticate if prompted

Cursor supports OAuth-capable remote MCP servers. If Cursor prompts you to sign in or authorize AskElephant, complete that flow after saving the config.

Verify the setup

Open a new Cursor chat and check that the AskElephant tools appear in the available tools list.

Example prompts:

• Find my latest customer meetings with Acme and summarize the themes.
• Show me the transcript timeline for the most recent completed call.
• Help me write a sync job against the AskElephant API using updated_at filtering.

Notes

• Cursor’s official docs describe two common config locations: ~/.cursor/mcp.json for global tools and .cursor/mcp.json for project-specific tools.
• Cursor also supports remote server headers in mcp.json, but you do not need custom headers for the AskElephant URLs above unless your environment requires them later.
• If the tools do not appear immediately, reload the Cursor window and open a fresh chat.