Where to find it: Smithery and the official MCP registry: live.
Set it up
- Windsurf Settings, then Cascade, then MCP servers, then Add server. Paste this configuration.
{ "mcpServers": { "signalraven": { "serverUrl": "https://api.signalraven.ai/mcp" } } } - Save. Windsurf opens SignalRaven's sign-in; sign in and press Allow.
- Ask Cascade.
Using SignalRaven, which accounts showed activity this week?
Your first prompt
Using SignalRaven, which accounts showed activity this week?
The accounts with signals this week, each with the source that produced the signal and the strongest person at the account.
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.
Troubleshooting
I see sample data instead of my workspace.
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.
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
Windsurfreads 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.
Also works in
- Cursor → Add the SignalRaven MCP server to Cursor and ask about signals, accounts, and openers while you work.
- Claude → Connect SignalRaven as a Claude connector, or install the Claude Code plugin with two skills for prospect research and opener drafting.
- ChatGPT → Ask ChatGPT who is showing intent this week, why each signal matters, and what to say, straight from your SignalRaven workspace.