# SalesTouch — OAuth-protected remote MCP server that gives AI agents LinkedIn search, messaging and publishing tools.

> Source: The Agents Index — https://theagentsindex.com/salestouch (structured, researched, re-verified)
> Facts last verified: 2026-09-26

SalesTouch is a hosted remote MCP server that exposes LinkedIn search, profile, conversation, outreach and publishing tools to MCP-compatible AI clients. A queueing layer applies identity, permission, pacing and working-hour checks before any action reaches LinkedIn.

| Fact | Value |
| --- | --- |
| Website | https://salestouch.io |
| Price | from $39/month billed monthly, $32.42/month billed annually |
| Free trial | Partly |

Seven-day free trial with the complete product and one connected LinkedIn account; a payment method is required and the selected monthly or annual plan starts automatically unless cancelled in Stripe before day 7. No standing $0 plan exists.

## What it does

**Done-for-you service** · No — You run the software yourself: the vendor sells a self-serve subscription and a connector, not a managed outreach team.

> SalesTouch is a LinkedIn MCP: a secure connector that lets your AI agent work on LinkedIn with your permission.
> — https://www.salestouch.io/ · Homepage FAQ, answer to "What is SalesTouch, exactly?"

## How much it does unattended

**Runs autonomously** · Partly — Scheduled work executes in the cloud without the agent running, but the docs still direct confirmation of message content and approval controls exist for sensitive actions.

> Schedule LinkedIn actions from Claude or Codex. SalesTouch queues and executes them in the cloud when they are due, even if your agent is closed and your computer is off.
> — https://www.salestouch.io/ · Homepage, "Cloud execution" section

**Multi-agent** · Partly — Several MCP clients can share one SalesTouch connection and workspace state; no orchestration of multiple agents on a single task is described.

> Claude, Codex, and other compatible agents can use the same SalesTouch connection. You are not locked into one AI client.
> — https://www.salestouch.io/linkedin-mcp · 'What MCP changes for you', MCP advantage 01

**Agent permissions** · Yes — Every call passes a documented pre-execution gate covering identity, permissions, limits, timing and queue state, and out-of-policy work is refused rather than run.

> Before an action reaches LinkedIn, SalesTouch checks identity, permissions, limits, timing, and queue state. Approved work moves fast. Anything outside your rules is slowed, queued, paused, or rejected.
> — https://www.salestouch.io/ · Homepage, "The safety layer" section

## Which models it runs on

**Claude** · Yes — Claude is a first-class client on both plans, connected either through the vendor's plugin marketplace flow or a manual remote MCP entry.

> Use SalesTouch from Claude through MCP.
> — https://www.salestouch.io/pricing · Plan comparison table, AI compatibility section, Claude row

**GPT** · Yes — Both OpenAI surfaces are listed on every plan: ChatGPT via remote MCP and Codex as a documented connection path.

> Connect SalesTouch to ChatGPT through remote MCP.
> — https://www.salestouch.io/pricing · Plan comparison table, AI compatibility section, ChatGPT row

**Open models** · No — The only inference provider named anywhere on the site is Anthropic, for SalesTouch's own AI features; no open-weight model support is claimed.

> Anthropic | AI generation for features that use it | Prompts, relevant context and generated output
> — https://www.salestouch.io/privacy · Section 7 'Service providers and recipients', provider table

**Model choice** · Yes — The model lives in your own client, which you bring and pay for separately, so the buyer picks the model rather than the vendor.

> Connect any supported AI client that can use remote MCP servers.
> — https://www.salestouch.io/pricing · Plan comparison table, AI compatibility section, "Compatible MCP clients" row

## Where you use it

**On the command line** · Yes — The documented default connection path is the Codex command-line client, with the graphical Codex app given as the alternative.

> If you use the graphical Codex app, add a Streamable HTTP MCP server named `salestouch` with the same endpoint and connect it through OAuth.
> — https://www.salestouch.io/docs/getting-started · "Connect Codex" section, sentence after the CLI instructions

**In a browser** · Yes — Besides the MCP endpoint there is a hosted web application for setup, activity, limits, organizations and billing administration.

> Use a web interface for setup, activity, limits, organizations and billing.
> — https://www.salestouch.io/terms · Section 2, "The Service", capability list

_Not established: In your editor, In your pipeline_

## Whose machine it runs on

**Self-hosted** · No — There is one vendor-hosted endpoint on the vendor's own domain, with hosting on Vercel and managed PostgreSQL; no customer-run deployment is offered.

> SalesTouch exposes one OAuth-protected remote MCP endpoint:
> — https://www.salestouch.io/docs/getting-started · Getting started, introductory sentence above the endpoint URL

**Open source** · No — The terms reserve all rights in the software and MCP tools to the vendor and grant only a revocable right to use the service.

> SalesTouch and its licensors retain all rights in the Service, software, MCP tools, documentation, design, databases, trademarks and related technology.
> — https://www.salestouch.io/terms · Section 11, "SalesTouch intellectual property"

## What it costs to run

**How it meters** · Yes — Billing is a flat subscription per connected LinkedIn account rather than metered credits, tokens or per-task charges; the first account is included.

> Every connected LinkedIn account gets the same tools, controls, queues, and visibility.
> — https://www.salestouch.io/pricing · "Start with one account. Add more when the work grows." section

**Free tier** · Partly — You can start without a sales call, but only as a seven-day trial that requires a payment method and converts automatically into the chosen plan.

> Connect one LinkedIn account, use every capability, and judge SalesTouch on real work. Cancel in Stripe before day 7 and pay nothing.
> — https://www.salestouch.io/pricing · Trial call-to-action block above the FAQ

**API access** · Partly — Programmatic access exists, but only as the OAuth-protected MCP endpoint; no separate REST or GraphQL API is documented on the site.

> SalesTouch uses OAuth 2.1 with PKCE. MCP clients discover the authorization server automatically from the protected-resource metadata published beside the remote MCP endpoint.
> — https://www.salestouch.io/docs/authentication · Authentication, opening paragraph

**MCP server** · Yes — The entire product is a remote MCP server, so any MCP-capable agent can query it once OAuth consent and LinkedIn connection are in place.

> Make LinkedIn callable from Claude, Codex, ChatGPT, or any MCP-compatible AI agent. Search, read, message, follow up, and publish through one controlled endpoint.
> — https://www.salestouch.io/ · Homepage meta description

**Bring your own key** · Partly — Inference normally comes from your own AI client subscription, and an Anthropic API key can be supplied and is stored encrypted, but the LinkedIn execution stays on vendor infrastructure.

> Instructions, relevant prospect or message context, generated suggestions and, if supplied, an encrypted Anthropic API key
> — https://www.salestouch.io/privacy · Section 4, "Data we process", AI data row

## Buying it for a team

**A company can buy it** · Yes — The service is sold only to businesses acting professionally, the buyer must be able to bind the organisation, and organisations are a first-class object in the web app.

> The Terms apply only to customers acting for professional purposes. The Service is not offered to consumers.
> — https://www.salestouch.io/terms · Section 1, "Scope and operator"

**Seat model** · Yes — One LinkedIn account is included per subscription and each additional account costs the same full price, prorated mid-cycle, with reductions only at renewal.

> Mid-cycle additions are prorated automatically.
> — https://www.salestouch.io/pricing · "Each additional account" pricing block, bullet list

**Pooled budget** · No — Queues, limits and visibility are scoped to each connected LinkedIn identity rather than drawn from one shared workspace balance.

> Every connected LinkedIn account gets the same tools, controls, queues, and visibility. Keep each identity separate while your agents work from one SalesTouch workspace.
> — https://www.salestouch.io/pricing · "Start with one account. Add more when the work grows." section

**Admin controls** · Yes — Daily action limits, working hours, approval controls for sensitive actions and automatic cooldowns are all configurable and shipped on both plans.

> Built-in controls for how LinkedIn actions are scheduled and executed.
> — https://www.salestouch.io/pricing · Plan comparison table, "Safety and control" section header

**Audit log** · Yes — Every MCP tool call is logged with payload and timing detail and kept for ninety days, on both the monthly and annual plan.

> Inspect calls, payloads, durations, account activity, and errors.
> — https://www.salestouch.io/pricing · Plan comparison table, "90-day MCP activity logs" row

**Single sign-on** · Partly — Optional Google and GitHub social sign-in is documented as the federated login path; SAML or enterprise OIDC is never mentioned anywhere on the site.

> Google and GitHub | Optional social sign-in | Account identity and authentication data
> — https://www.salestouch.io/privacy · Section 7 provider table, Google and GitHub row

## What happens to your code

**Opt out of training** · Partly — The vendor states it does not train its own model on customer content, but that is a commitment rather than a switch, and prompts still reach Anthropic under Anthropic's terms.

> SalesTouch does not use customer content to train its own general-purpose AI model.
> — https://www.salestouch.io/privacy · Section 6, "How LinkedIn and AI data are used", final paragraph

**Data residency** · Partly — The operator is in France with an EU analytics region, but some providers process outside the EEA under transfer mechanisms and no region choice is offered.

> Some providers process data outside the European Economic Area. Where required, we rely on an adequacy decision, the EU-U.S. Data Privacy Framework for certified recipients, the European Commission's Standard Contractual Clauses, or another lawful transfer mechanism
> — https://www.salestouch.io/privacy · Section 8, "International transfers"

**Getting out** · Partly — Deletion or return at the customer's choice is contractual, but export is left to the customer before termination and scrape export links expire after seven days.

> You should export data you need before termination.
> — https://www.salestouch.io/terms · Section 10, "Customer data"

**Certifications** · Partly — A full GDPR Article 28 processing agreement with audit rights is published, but no SOC 2 or ISO 27001 certification is claimed anywhere on the site.

> This section is a data processing agreement under Article 28 GDPR when SalesTouch processes personal data in Customer Data on your behalf.
> — https://www.salestouch.io/terms · Section 16, "Data processing terms"

## Provenance

Every fact above comes from the vendor. Nothing here is independently corroborated yet.

## Coverage elsewhere

None recorded. Every fact above comes from the vendor and is not independently corroborated yet.

## What changed

- 2026-09-26 — Free tier
- 2026-09-25 — Capabilities · Commercial terms · Free tier
- 2026-09-03 — Capabilities · Commercial terms · Free tier
- 2026-08-31 — Capabilities · Commercial terms · Free tier · Price
- 2026-08-23 — Alternatives
- 2026-08-15 — One-liner · Summary

## Correcting this record

Anything marked "Not established" is a question we have not answered — it is not a No. If you represent SalesTouch, or anything here is wrong or out of date, you can supply it with a source: the operations this site accepts from an agent are listed at https://theagentsindex.com/.well-known/agents.json — that catalogue needs no key to read, and each entry states its own auth.

Supplying evidence is free. Nothing that can be bought here changes what a field says, whether a gap is closed, or how this record is scored.