SalesTouch

What the SalesTouch MCP server does

The SalesTouch MCP server gives AI agents access to LinkedIn workflows through a hosted MCP endpoint. It can inspect connected accounts, look up profiles and companies, read conversations, retrieve recent posts, search Sales Navigator audiences, inspect post reactions and comments, and work with stored paginated results.

It also supports actions that change LinkedIn or SalesTouch state. Agents can send messages, invitations, likes, comments, and publications when the relevant mutation is authorized. Write actions can be scheduled for later execution, while queued actions can be reviewed or cancelled. The hosted service reconnects a sleeping credential-based account when a scheduled action becomes due.

How it works

Clients connect to https://www.salestouch.io/api/mcp using Streamable HTTP. SalesTouch starts an OAuth flow in the browser and grants scoped access after authorization. LinkedIn passwords, cookies, and authentication secrets are not placed in the MCP configuration or shared with the AI client.

A read-only account request is recommended as the first connection check. Research workflows can look up a profile, retrieve posts with cursors, and generate a draft without changing external state. For outreach, the agent can find a conversation, read bounded history, prepare an exact reply, and wait for confirmation before using a message mutation.

Sales Navigator extraction uses a parameter-resolution step before company or people searches. Stored results can be viewed in pages or exported as signed CSV or JSONL files. Post reaction and comment extraction also returns a bounded preview and result identifier; additional source extraction can continue with paging arguments when available.

Setup and configuration

Install the plugin for Claude Desktop, Cowork, or Claude Code using the repository’s Claude installation guide. Claude Code supports the SalesTouch plugin marketplace commands. Cursor can use the local plugin or a remote entry in .cursor/mcp.json:

{
  "mcpServers": {
    "salestouch": {
      "url": "https://www.salestouch.io/api/mcp"
    }
  }
}

Other Streamable HTTP clients can use the same endpoint and name the server salestouch. No static API key or LinkedIn credential is required in the MCP configuration. The plugin is MIT-licensed, but the hosted SalesTouch service requires a separate subscription.

Tools and capabilities

The SalesTouch MCP server supports capabilities including:

• LinkedIn account checks, profile research, company research, and conversation lookup.
• Message drafting and sending, invitations, likes, comments, and publishing.
• Sales Navigator filter resolution with linkedin_sales_navigator_search_parameters.
• Company and people extraction with scrape_sales_navigator_companies and scrape_sales_navigator_people.
• Post reaction and comment extraction, including optional reply authors.
• Result pagination through scrape_result_page and signed CSV or JSONL export.
• Durable scheduling and queues for supported write actions.

Limitations and notes

Read operations are described as non-destructive and idempotent. Messages, invitations, likes, comments, and publications modify LinkedIn and are not idempotent. Cancelling a queued action changes SalesTouch state and should not be treated as automatically safe to repeat.

Availability depends on the SalesTouch plan, a connected LinkedIn account, platform availability, permissions, and usage limits. SalesTouch does not bypass LinkedIn safeguards. Users remain responsible for checking recipients and content and following applicable platform rules and laws. If OAuth fails, reconnect from the MCP client, verify the endpoint and account, and repeat the read-only account check. Do not send credentials, cookies, tokens, private messages, or prospect data in support requests.