Claude

Claude connects to Chartnaut in two places: as a custom connector in claude.ai, which Claude Desktop and the mobile apps then share, and as an MCP server in Claude Code. Both use the same address, https://api.chartnaut.com/v1/mcp, and your Chartnaut plan must be Starter or above. Connect Chartnaut to an AI app covers what Claude can do once connected.

claude.ai and Claude Desktop

Custom connectors need a paid Claude plan. Labels in Claude's settings vary by version, so look for the nearest match.

1. In claude.ai or Claude Desktop, open Settings → Connectors.

2. Click Add custom connector.

3. Name it Chartnaut and paste https://api.chartnaut.com/v1/mcp as the URL. Leave any OAuth client ID and secret fields empty: Claude registers itself with Chartnaut.

4. Save the connector, then connect it. Claude opens a Chartnaut page in your browser.

5. Sign in to Chartnaut if it asks, check the permissions, and click Allow.

The browser returns to Claude and the connector shows as connected. Switch it on for a chat, then ask in plain words: Write an indicator that shows the 20-period EMA of BTC's 1-hour closes and run it on the last 30 days. What you can ask has more.

Claude asks before it calls a tool, and its settings let you allow a tool for good. Reading tools change nothing, so allowing them saves clicks. Keep asking for save_script, run_script and run_definition_over_history, the three that change your account, and read what Claude is about to save before you let it through.

Chartnaut's three prompts, Write a Chartnaut indicator, Test a trading idea and Explain a run, show up in the chat's attachment or connector menu, as do the scripting reference resources.

On a Team or Enterprise plan, an owner adds the connector for the organisation, and each person then connects their own Chartnaut account.

Claude Code

Add the server once, then sign in from inside Claude Code:

claude mcp add --transport http chartnaut https://api.chartnaut.com/v1/mcp

1. Start Claude Code and type /mcp.

2. Pick chartnaut and choose to authenticate.

3. Click Allow on the Chartnaut page that opens in your browser.

Add --scope user to the claude mcp add line to have Chartnaut in every project, not only the folder you ran it in. /mcp lists the server's tools once it is connected, and Chartnaut's prompts appear among the slash commands, named after the server and the prompt, such as /mcp__chartnaut__write_indicator.

To use an API key instead of the browser sign-in, for example on a server with no browser, pass it as a header:

claude mcp add --transport http chartnaut https://api.chartnaut.com/v1/mcp \
  --header "Authorization: Bearer cn_live_XXXX"

The key is then stored in Claude Code's config file. Give it only the scopes Claude needs, and revoke it on the Developers page when you stop using it.

Set it up with the Chartnaut CLI

If you have the Chartnaut CLI, chartnaut mcp install claude prints both lines with your API address filled in. The API-key line reads the key from CHARTNAUT_TOKEN, so the printed text never contains it.

chartnaut mcp install claude --write goes a step further: it runs claude mcp add --scope user itself, with the key the CLI is signed in with, so Chartnaut is in every project. Command reference

MCP or the CLI in Claude Code

Claude Code can also drive the CLI directly, and the two suit different work:

You can have both. Each call either one makes counts toward the same API limits. MCP, the Agent or the CLI adds the Agent to the comparison, and Troubleshooting MCP covers a connection that will not start.