SIGNALRAVEN
Integrations
Claude·AI assistant

SignalRaven in Claude, Claude Desktop and Claude Code

Claude reads your SignalRaven workspace over an OAuth connection you approve. In Claude Code, the plugin adds two skills: research a prospect, and draft three openers from a signal.

Where to find it: Claude connector directory: in review. Custom connectors and the Claude Code plugin work today.

Set it up

  1. Claude.ai or Claude Desktop: Settings, then Connectors, then Add custom connector. Name it SignalRaven and paste the URL.
    https://api.signalraven.ai/mcp
  2. Press Connect. SignalRaven's sign-in opens; sign in and press Allow.
  3. Claude Code: add the marketplace and install the plugin.
    /plugin marketplace add SignalRaven-ai/signalraven-open
/plugin install signalraven@signalraven-open
  4. In Claude Code, run a skill.
    /research-prospect Marcus Feld at Brightmile

Your first prompt

Show my strongest signals this week.

A ranked list of this week's signals: the person, their title and company, the urgency score out of 10, and why it matters, with a suggested opener for each. An account without a workspace gets the same shape with clearly labeled sample data.

What to ask

  • Show my strongest signals this week and draft an opener for each.
  • Which named accounts showed activity this week, and through which source?
  • Research [person] before my call: what did they engage with, and what should I say?
  • Which of my monitored sources are producing qualified signals, and which are dead?
  • Run Account Intelligence on [company] and tell me who to email first.

Skills

Two workflows ship with the plugin and work in any assistant that supports skills. In other clients, the same prompts trigger the same tools.

  • research-prospect: Who they are, what they engaged with and when, the ICP read, why now, and three talking points.
  • draft-openers: Three openers under 300 characters, each citing what the person actually posted.

How the skills work →

Troubleshooting

The connector connects but tools return sample data.

The account you signed in with has no active SignalRaven workspace, or you approved the connection while signed in as a different user. Disconnect, sign out of signalraven.ai in your browser, and connect again as the account that owns the workspace. Trial and paid workspaces get live data.

Claude Code says the plugin has no MCP server.

The plugin declares the server in its .mcp.json. Run /plugin install again after adding the marketplace, then restart the session.

The connector asks me to sign in every time.

Sign-in is remembered for a day per client. Reconnecting under a new client name registers a new client on our side, which starts fresh. Keep one connector per assistant.

Your data

Claudereads your own SignalRaven workspace over an OAuth connection you approve and can revoke. Anything that spends credits or changes where signals are delivered sits behind its own named permission on the consent screen. Monitoring runs on SignalRaven’s infrastructure, and the connector never touches your LinkedIn login, cookies, or session. Accounts without a workspace get clearly labeled sample data.

Start free trial →

Also works in

  • ChatGPT → Ask ChatGPT who is showing intent this week, why each signal matters, and what to say, straight from your SignalRaven workspace.
  • Cursor → Add the SignalRaven MCP server to Cursor and ask about signals, accounts, and openers while you work.
  • Codex → The same SignalRaven server ChatGPT uses, inside Codex: research a prospect, list signals, and draft openers from your terminal or editor.
All integrations