Connect Chartnaut to an AI app
You can connect Claude, ChatGPT, Cursor or Codex to your Chartnaut account and work on your scripts from that app's own chat. Ask for an indicator or a test of a trading idea, and the app reads the scripting reference, writes the script, runs it on Chartnaut's servers and reads you the results.
CodexThe connection uses MCP, the Model Context Protocol: an open standard that lets an AI app call tools on another service. Chartnaut runs one MCP server, and every app connects to the same address:
https://api.chartnaut.com/v1/mcpThis is separate from the Agent inside Chartnaut, which works in the app and builds apps, studies and Forward Insights with approval cards. MCP, the Agent or the CLI compares the three.
What the AI app can do
It can | For example |
|---|---|
Read the scripting reference | Look up how outputs and settings work before writing code |
Search the library and describe a script | Find Chartnaut's built-in RSI and list its settings |
List and read your own scripts, source included | Open your VWAP indicator to change it |
Check a script without saving it | Fix every error before anything is saved |
Save a script or a new version | Save a definition it wrote, with a one-line change summary |
Run a script on an instrument, timeframe and window | Run an EMA on 30 days of 1-hour BTC, then read the values |
Read a run's status and results | Explain why a run failed, line by line |
Read a definition's events, and run it over history | Count how often a setup fired on ETH over a year |
Find instruments and check your plan | See which dates your plan reaches on BTC |
What you can ask has prompts for each of these, and the MCP tools reference lists every tool with its inputs and outputs.
What it cannot do
It never sees your password. You sign in on Chartnaut's own page and click Allow; the app gets a token, never your login.
It acts as you, within the permissions you approved, and nothing more. Permissions and connected apps
It never gets the code of other people's scripts. It can run and describe community scripts, but their source stays private, and their names and descriptions reach it marked as text written by another user.
It never receives raw candles or tape. Runs return what the script produced: output values, events or study results.
It cannot trade, open charts, read your trades or journal, or delete anything. The only changes it can make are saving your scripts, starting runs and storing a definition's events.
Security and privacy covers what the app sees and how the connection is protected.
Plans and cost
MCP is included on Starter and above, the same as the CLI and the API. On Free, the sign-in page shows API access is included on Starter and above when you click Allow, and an app connected before a move to Free gets plan_limit on every call until you upgrade.
The AI itself runs on your plan with that app, not on Chartnaut's AI credits. Each tool call makes one or more API requests, and they count toward your plan's API limits, shared with the CLI and your API keys. Runs take from the same pool of runs at once as the app. Limits and cost lists what each tool costs.
Connect an app
App | How it connects | Read |
|---|---|---|
claude.ai and Claude Desktop | Custom connector, browser sign-in | |
Claude Code |
| |
ChatGPT | Custom connector in developer mode, browser sign-in | |
Cursor |
| |
Codex |
|
Claude CodeAny other app that supports remote MCP servers over Streamable HTTP with OAuth connects the same way: give it the address above. The Chartnaut CLI prints the setup for Claude Code, Cursor and Codex with chartnaut mcp install.
Pages in this group
To | Read |
|---|---|
Choose between an AI app, the Agent and the CLI | |
Set up an app | |
Find requests that work well | |
See what an app can do, and disconnect it | |
Know what the app sees and how your account is protected | |
Know what each tool costs against your limits | |
Look up a tool's inputs, outputs and errors | |
Fix a connection or a failing tool call | |
Follow the sign-in and each call step by step | |
Write your own MCP client |
Disconnect
Open Developers in the menu under your name, find the app under Connected apps and click Disconnect. It loses access straight away. An app connected with an API key is cut off by revoking that key on the same page. Permissions and connected apps