Connect any MCP-compatible AI tool to your Chartcastr account in three steps. Pick your tool, run one command (or paste one block of JSON), restart, done.Documentation Index
Fetch the complete documentation index at: https://docs.chartcastr.com/llms.txt
Use this file to discover all available pages before exploring further.
Looking for the why instead of the how? See AI Tools — Concepts for the context-layer and action-agent patterns.
Step 1 — Get an API key
In the Chartcastr dashboard, open Settings → API Keys and create a new key. Copy it — you’ll paste it in Step 2.Treat this key like a password. Anyone with it can read your sources, connections, and pulse analysis.
Step 2 — Install the MCP server in your tool
Pick your tool and run the matching command.- Claude Code
- Claude Desktop
- Cursor
- ChatGPT Desktop
- Codex
One line in your terminal:That’s it — Claude Code persists this in your user config. Skip to Step 3.Prefer JSON? See the Claude Code page for the
.mcp.json form.Step 3 — Verify it works
Ask your tool one of these:- “List my Chartcastr sources.”
- “What did the latest pulse say about my HubSpot connection?”
- “Are any of my connections inactive?”
/mcp to see the active server list — chartcastr should appear.
Available tools
These are the tools your AI agent can call once connected:| Tool | What it returns |
|---|---|
list_sources | Every connected data source with status and connection count |
list_destinations | Every configured destination (Slack workspace, email, etc.) |
list_connections | Every active chart delivery — source, destination, cadence |
get_latest_pulse | Full AI narrative analysis from the most recent delivery |
verify_connection | Live confirmation a specific connection is active |
open_chartcastr | Deep link to open the dashboard at a specific page |
Local development
Running Chartcastr locally withbun up? Swap the URL to http://localhost:8109/api/mcp and use a key generated against your local server.
Troubleshooting
401 Unauthorized
401 Unauthorized
Tool doesn't see chartcastr after install
Tool doesn't see chartcastr after install
Most MCP clients only load servers at startup. Quit fully and relaunch — a window reload isn’t enough. In Claude Code, run
/mcp to force a server-list refresh.`npx mcp-remote` hangs or errors
`npx mcp-remote` hangs or errors
First run downloads the
mcp-remote package — give it ~30 seconds. If it persists, run npx -y mcp-remote@latest once manually to prime the cache.Tool returns 'not currently available'
Tool returns 'not currently available'
A specific tool may be feature-flagged off during rollout. Check status.chartcastr.com or contact support.

