SIGNALRAVEN
Integrations
Codex·AI assistant

Prospect research from Codex

Codex shares ChatGPT's plugin directory and MCP support, so the SignalRaven server works there without a separate setup. Research a prospect before a call without leaving your editor.

Where to find it: OpenAI Plugin Directory: in review. The MCP path below works today.

Set it up

  1. Open Codex settings and find MCP servers.
  2. Add a server named SignalRaven with the Streamable HTTP URL.
    https://api.signalraven.ai/mcp
  3. Authenticate. SignalRaven's sign-in opens in your browser; sign in and press Allow.
  4. Ask Codex.
    Using SignalRaven, research [person] before my call.

Your first prompt

Using SignalRaven, research [person] before my call.

Who they are, what they engaged with and when, the ICP read, why now, and three talking points, drawn from the signals and reports already in your workspace. Codex asks before starting a report run, since runs spend credits.

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 OAuth 2.0 Client is not allowed to request scope 'offline'."

An older registration. Remove the server and add it again under a new name.

Tool calls fail with a permission message.

The connection was approved without permissions. Remove the server, add it again under a new name, and authenticate; the consent screen lists the permissions.

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

Codexreads 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.
  • Claude → Connect SignalRaven as a Claude connector, or install the Claude Code plugin with two skills for prospect research and opener drafting.
  • Cursor → Add the SignalRaven MCP server to Cursor and ask about signals, accounts, and openers while you work.
All integrations