# MCP for Claude

> Add CurrencyCore to Claude web or Desktop as a custom connector, or to Claude Code with one command. Exact steps, config, and fixes.

Canonical: https://currency-core.com/docs/mcp-claude/

---
Claude connects to CurrencyCore as a **remote MCP connector**. You add a name and
a URL in Settings, then complete an OAuth sign-in. There is no local server
process and no API key in a file.

Checked 2026-11-10 against Anthropic's connector and Claude Code documentation.

Server URL:

```
https://mcp.currency-core.com/mcp
```

## Claude web and Claude Desktop

Use this path for Claude on the web and for the Claude Desktop app. The connector
UI is the supported way to add a remote server.

1. Open **Settings**.
2. Go to **Connectors**.
3. Choose **Add custom connector**.
4. Enter a name, for example `CurrencyCore`, and the server URL above.
5. Save, then start the connection. A browser normally opens.
6. Sign in to CurrencyCore, choose the organization, and approve the connection.
7. Return to Claude and send a test prompt.

Depending on your workspace, an owner or admin may need to allow custom
connectors before the option is available. On Team and Enterprise plans, check
the workspace connector settings if you do not see **Add custom connector**.

### Verify

Ask Claude:

> Use the CurrencyCore convert tool to convert 100 USD to EUR and tell me the
> rate date.

A working connection returns a conversion with a date. If Claude answers from
memory without a tool call, name the tool again and confirm the connector is
enabled for that conversation.

## Claude Code

Claude Code can add the server from the terminal. This avoids hand-editing JSON.

```bash
claude mcp add --transport http currency-core https://mcp.currency-core.com/mcp
```

Then, inside a session:

```text
/mcp
```

Choose `currency-core` and authenticate. The browser sign-in and organization
selection are the same as the connector flow.

### Project config

To commit the server to a repository, add `.mcp.json` at the project root:

```json
{
  "mcpServers": {
    "currency-core": {
      "type": "http",
      "url": "https://mcp.currency-core.com/mcp"
    }
  }
}
```

`type` must be `"http"` for Streamable HTTP. Do not use `"sse"` for this server.

To verify from the command line:

```bash
claude mcp list
```

The server should appear with its connection status. Use `/mcp` inside a session
to authenticate or inspect it.

## Legacy JSON for Claude Desktop

Older documentation and local-server setups use
`claude_desktop_config.json`. That file is intended for **local** MCP servers
that Claude Desktop launches as a process. It is not the supported way to add
this remote connector, and on current builds a remote server added there may not
appear at all.

If your build explicitly documents remote servers in this file, the entry looks
like this:

```json
{
  "mcpServers": {
    "currency-core": {
      "url": "https://mcp.currency-core.com/mcp"
    }
  }
}
```

Common paths:

| OS | Path |
|---|---|
| macOS | `~/Library/Application Support/Claude/claude_desktop_config.json` |
| Windows | `%APPDATA%\Claude\claude_desktop_config.json` |
| Linux | `~/.config/Claude/claude_desktop_config.json` (builds vary) |

After editing, quit Claude Desktop completely and reopen it. If the connector
still does not appear, remove the entry and use **Settings, Connectors, Add
custom connector** instead.

## Gotchas

| Problem | Why it happens | Fix |
|---|---|---|
| No connector option | The workspace has not enabled custom connectors | Ask an owner or admin to allow them. |
| The browser sign-in never opens | The client has not reached an authorized tool yet, or the OAuth challenge was not triggered | Start a keyed tool call, or use the connector's connect action. If only two tools appear, see the [troubleshooting note for older deployments](/docs/mcp-troubleshooting/#only-two-tools-and-no-sign-in-prompt). |
| The wrong organization is billed | The connector is bound to the organization chosen at consent | Remove the connector, add it again, and choose the correct organization. |
| `analyze_` tools return `403` | Analytics require Growth or higher | Upgrade, or use the core tools. |
| History is limited to 30 days | The Free plan limits historical dates | Request a recent window, or upgrade to Starter or higher. |
| Claude does not call the tool | The model chose to answer directly | Ask it to use the CurrencyCore tool by name, and confirm the connector is enabled. |

## What Claude can call

Claude sees 14 tools. Core currency tools work on every plan. Seven analytics
tools require Growth or higher:

`convert`, `get_rates`, `get_rates_by_base`, `get_history`, `get_ppp_factor`,
`list_countries`, `list_currencies`, and the `analyze_*` family.

The full reference is in [MCP tools](/docs/mcp-tools/). Each successful keyed
call counts as one API request against the organization's quota, and MCP uses no
AI credits.

## Related

- [MCP OAuth and access](/docs/mcp-oauth/)
- [MCP troubleshooting](/docs/mcp-troubleshooting/)
- [MCP for Cursor](/mcp-for-cursor/)
- [MCP for ChatGPT](/docs/mcp-chatgpt/)
- [MCP for VS Code](/docs/mcp-vscode/)