SignalAI
SignalsStrategiesBacktestsDocs

Connect SignalAI to Claude

SignalAI runs an MCP server, so you can use it from inside Claude, no code. Claude discovers the tools and calls them for you. Pick the path for the Claude you use:

  • Claude Code (the CLI), install the plugin. One step, and it bundles the playbook skills too.
  • Claude web (claude.ai) or Claude Desktop, add the MCP connector by hand.

Either way you sign in once with Google (the same account as the web app).

Claude Code, install the plugin

In Claude Code, run these two commands. This is the recommended path: the plugin bundles the connector and the six playbook skills that make Claude good at SignalAI.

/plugin marketplace add yashkothari42/signalai-plugins
/plugin install signalai

The first tool call opens a browser for the one-time Google sign-in. That's it, ask Claude anything below.

Don't add the connector by hand in Claude Code. The plugin already includes it, and only the plugin gives you the skills.

Claude web or Claude Desktop, add the connector

claude.ai and Claude Desktop don't use plugins, so you add the MCP connector manually:

  1. Open Settings → Connectors.

  2. Click Add custom connector.

  3. Paste the SignalAI MCP URL:

    https://35.94.249.241.sslip.io/mcp/

  4. Save. Claude sends you through a one-time Google sign-in (the same account as the web app).

After that, Claude can call SignalAI on your behalf. You get the same nine tools as Claude Code, but not the skills (those are a Claude Code plugin feature).

Staying up to date

The plugin improves over time (new skills, refined guidance). Two ways to stay current:

  • Auto-update (recommended): run /plugin, open Marketplaces, select signalai, and enable auto-update. New versions then arrive on launch.
  • Manual: run /plugin marketplace update signalai && /reload-plugins whenever you want the latest.

When you're behind, the plugin quietly reminds you at the start of a session.

What Claude can do

Once connected, Claude has nine tools, grouped by what they touch:

  • Signals, list_signals, get_signal_history, create_signal_from_prompt, send_signal_session_message (the last two drive the interactive builder).
  • Backtests, submit_backtest, get_backtest, list_backtests.
  • Strategies, list_strategies, get_strategy.

Together these let Claude build and inspect signals, diagnose a broken one, write a strategy, backtest it, and read the results, all scoped to your account.

Skills (Claude Code)

The plugin bundles six playbook skills that teach Claude to use the tools well. Claude picks the right one automatically:

  • signalai-guide, overview and which skill to use for what.
  • build-signal, create a new signal through the interactive builder.
  • debug-signal, diagnose a signal that's empty, stalled, or down.
  • build-strategy, shape an idea and write the strategy code.
  • run-backtest, submit a backtest and poll for results.
  • analyze-backtest, read results honestly and improve them without overfitting.

(claude.ai and Claude Desktop get the same nine tools via the connector; the skills are a Claude Code plugin feature.)

Example prompts

  • "List my SignalAI signals and which ones look stale."
  • "Write a momentum strategy on AAPL and backtest it from 2015 to 2024, then tell me the return and Sharpe."
  • "My BTC signal stopped updating, help me figure out why."
  • "This backtest returned 40% but the drawdown scares me, how do I make it more robust without overfitting?"
  • "Show me the last 20 datapoints for my BTC signal."

Everything is scoped to your account, Claude only sees your data.