Skip to content
MCP server

opensignals

MCP server that runs LinkedIn signals, lead lists, outreach and inbox from your AI

Answers · sign-in required (OAuth)

The server answered 3 hours ago with a sign-in request for OAuth (HTTP 401), so we could not list its tools.

Install
Platforms
API, Web, vscode
Runs
Remotely
Access
Needs sign-in (OAuth)
Version
1.0.0
Listing updated
today

Similar MCP servers

About opensignals

opensignals is an MCP server for sales and crm. It runs as a hosted remote server, so there is nothing to install locally.

The README describes opensignals as a way to bring LinkedIn prospecting into the AI chat you already use. Instead of switching between several sales tools, you connect the server to an assistant such as Claude, ChatGPT, Cursor, VS Code, Claude Code or Codex and issue requests in plain language to manage signals, workbooks, workflows, your inbox and LinkedIn actions.

The server uses OAuth sign-in for most clients, and Codex users create a token inside the opensignals settings. The vendor says research and writing run on the user's own AI model, and that actions which spend money or contact people require confirmation each time. Changes are logged and can be undone.

The server suits sales and business development people who run outbound on LinkedIn and want lead enrichment, personalised first lines, meeting prep and reply drafting in one place.

Install

Run in a terminal

claude mcp add --transport http opensignals https://api.opensignals.so/mcp

Add to Settings → Connectors → Add custom connector

https://api.opensignals.so/mcp
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "opensignals": {
      "url": "https://api.opensignals.so/mcp"
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "opensignals": {
      "type": "http",
      "url": "https://api.opensignals.so/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "opensignals": {
      "serverUrl": "https://api.opensignals.so/mcp"
    }
  }
}

Add to Grok Bot desktop app → Connect apps → Add a custom connector

https://api.opensignals.so/mcp

Enter a Name (for example "opensignals"), choose Type: Remote HTTPS, paste this as the Server URL and choose Add plugin. When we checked, this server asked for OAuth sign-in. If its docs give you an OAuth client ID and secret, enter them in the form's OAuth Client ID and Client Secret fields.

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "opensignals": {
      "type": "http",
      "url": "https://api.opensignals.so/mcp"
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

What it does

Lead list building
Turns a pasted list such as webinar attendees or a spreadsheet into a workbook of matched LinkedIn profiles.
Personalised first lines
Writes one sentence per lead based on the person's posts and company news, then sends it through a workflow.
Account research
Answers questions about target companies from web sources and places the results into filterable columns.
Meeting preparation
With a calendar connected, summarises attendees, prior signals and messages, and company changes before a call.
Inbox reply drafting
Drafts replies to messages that need a response in the user's writing style, sending only when instructed.
LinkedIn actions
Lets the assistant view, follow, like, connect with a note, message and accept invitations under the product's safety rules.

Good for

  • Enrich a conference attendee list and start outreach from one chat
  • Prepare a briefing on each account before a sales call
  • Draft and review replies across a LinkedIn inbox
  • Push hot accounts to a CRM and post pipeline summaries to Slack
  • Ask questions about which messages get replies from target roles

Pricing

Pricing unknown

The site mentions a flat fee in its title but does not state the amount on the content provided.

Prices change. Check opensignals.so before you buy.

opensignals FAQ

Which AI apps can connect to opensignals?

The site lists Claude, ChatGPT, Cursor, VS Code with Copilot agent mode, Claude Code and Codex, and says any MCP client that supports streamable HTTP with OAuth can connect, with a local bridge via mcp-remote for others.

How does authentication work?

Most clients sign in through OAuth in the browser. Codex instead uses a bearer token created under Settings › AI apps in opensignals and exported as an environment variable.

Who pays for the AI model usage?

The site states that research, judging and writing run on the user's own AI, so they do not consume opensignals credits.

Does it take actions without asking?

The site says anything that spends money or reaches people asks for confirmation every time, and every change is logged and can be undone.

How do I add opensignals to Claude Code?

Run this command in your terminal: claude mcp add --transport http opensignals https://api.opensignals.so/mcp

What are the best alternatives to opensignals?

The closest alternatives to opensignals are Sendable, LinkedIn MCP (by TalkToHumans), GetSales: Outreach MCP Server, Funkel AI and Omentir.

Where this comes from

  • Description: written from the project's website and its MCP Registry entry.
  • Status: checked automatically by AIPoweredBot on 19 November 2026.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers