> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dexpaprika.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect DexPaprika MCP to any client

> Connect the keyless DexPaprika MCP server to any MCP-compatible client (Windsurf, Cline, Zed, and more). One canonical config: a remote SSE/streamable-HTTP URL, or a local stdio command.

DexPaprika ships a standard MCP server, so it works with any MCP-compatible client, not just the ones with a dedicated guide. There are two ways to connect, and most clients accept the first.

## Option 1: Remote server (recommended)

Point your client at the hosted server. No install, keyless.

```json theme={null}
{
  "mcpServers": {
    "dexpaprika": {
      "url": "https://mcp.dexpaprika.com/sse"
    }
  }
}
```

`/sse` is the recommended transport. The same server also serves streamable HTTP at `https://mcp.dexpaprika.com/streamable-http` for clients that prefer it.

## Option 2: Local server (stdio)

Run the server on your machine and have the client launch it:

```json theme={null}
{
  "mcpServers": {
    "dexpaprika": {
      "command": "npx",
      "args": ["-y", "dexpaprika-mcp@latest"]
    }
  }
}
```

## Where to put the config

The `mcpServers` shape above is what **Claude Desktop, Cursor, VS Code, Cline, and Windsurf** use. The file location differs per client (for example Windsurf keeps it in `~/.codeium/windsurf/mcp_config.json`, Cline in its MCP settings pane), so check your client's MCP docs for the exact path, then paste one of the blocks above.

A few clients use a different shape:

| Client | Config format |
| - | - |
| Claude Desktop, Cursor, VS Code, Cline, Windsurf | `mcpServers` JSON (above) |
| Codex CLI | TOML in `~/.codex/config.toml` (see the [Codex guide](https://docs.dexpaprika.com/ai-integration/codex.md)) |
| Zed | `context_servers` in `settings.json` (Zed's own key), pointing at the same URL or command |

We have step-by-step guides for [Cursor](https://docs.dexpaprika.com/ai-integration/cursor-ide-integration.md), [VS Code](https://docs.dexpaprika.com/ai-integration/vscode-ide-integration.md), [Claude Code](https://docs.dexpaprika.com/ai-integration/claude-code-plugin-guide.md), and [Codex](https://docs.dexpaprika.com/ai-integration/codex.md). For anything else, the config above is all you need.

## What you get

20 tools across networks, pools, tokens, OHLCV, transactions, and cross-chain search. Start with `getCapabilities` for the runtime manifest, or read the [MCP tools reference](https://docs.dexpaprika.com/ai-integration/mcp-tools.md).

## FAQs

> **My client isn't listed. Will it work?**
>
> If it supports MCP, yes. DexPaprika is a standard MCP server. Use the remote `url` config for a hosted connection, or the stdio `command` config to run it locally, in whatever place your client keeps MCP servers.

> **Remote or local: which should I choose?**
>
> Remote (`url`) is simplest: no install, always up to date, keyless. Choose local (stdio) if your client does not support remote MCP servers, or you want to run the server in your own environment.

> **Do I need an API key?**
>
> No. Both the hosted server and the npm package read keyless. The npm package calls the API from your machine, so a [free key](https://console.dexpaprika.com) raises your allowance there; see [rate limits](https://docs.dexpaprika.com/knowledge-base/rate-limits.md). The hosted server runs tool calls on its own shared capacity, not on a plan of yours, so a key raises no limit there. The exceptions are the tools that need a paid plan, which run on your own Dev, Pro or Enterprise key; see [the hosted server page](https://docs.dexpaprika.com/ai-integration/hosted-mcp-server.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.