> ## Documentation index
> Fetch the complete documentation index at: [llms.txt](../llms.txt)
> Use this file to discover all available pages before exploring further.

# Set up Sleuth in other AI tools

Cursor, Gemini, VS Code, and agents your team builds connect the same way.

[See the MCP reference](mcp-overview.md)

Any AI tool that supports remote MCP servers can connect to Sleuth.

## The general steps

1. **Add a remote MCP server**, sometimes called a custom connector, in your tool's settings.
2. **Paste the server URL.** The connection uses streamable HTTP.
3. **Sign in** with your Sleuth account when your tool asks. Sign-in uses OAuth, so you don't need an API key.

```
https://mcp.sleuthapi.com/mcp
```

## Cursor

[Add Sleuth to Cursor](cursor://anysphere.cursor-deeplink/mcp/install?name=sleuth&config=eyJ1cmwiOiJodHRwczovL21jcC5zbGV1dGhhcGkuY29tL21jcCJ9), or add an MCP server with the server URL in Cursor's MCP settings. Cursor asks you to sign in.

## Tools with a config file

Add Sleuth to the tool's MCP settings file, then sign in when prompted:

```
{
  "mcpServers": {
    "sleuth": {
      "url": "https://mcp.sleuthapi.com/mcp"
    }
  }
}
```

## Agents your team builds

Agents that a person signs in to connect over MCP the same way as Claude does, on any plan. Jobs that run without a person, like a nightly refresh, need an API key, which comes with Enterprise. The [MCP reference](mcp-overview.md) lists every tool and how a research run works, and [API](api.md) covers keys.

## Related

- [Sleuth MCP server](mcp-overview.md): Connect any MCP client or agent to Sleuth: run research, look up the knowledge base, build Explore datasets, and search the research library, with 52 tools.
- [API](api.md): Sleuth’s REST API lets your own software run Sleuth research without the Studio screen. It comes with Enterprise and powers the MCP server.
- [Fix connection problems](ai-troubleshooting.md): The most common problems connecting Sleuth to an AI tool, and how to fix each one.

*Updated November 9, 2026.*
