Find the right people
Search LinkedIn, Sales Navigator, post engagers, and profile viewers.
Search · Sales Navigator · Signals
Safe · reliable · scalable
Direct LinkedIn automation from Claude is fragile. SalesTouch gives your AI agent a controlled LinkedIn MCP with secure cloud execution, human-paced queues, tool permissions, and complete logs.
What your AI can do
Give Claude or Codex everything it needs to search, understand, contact, and publish on LinkedIn.
Search LinkedIn, Sales Navigator, post engagers, and profile viewers.
Search · Sales Navigator · Signals
Read profiles, companies, posts, and conversation history before acting.
Profiles · Companies · Threads
Prepare or send personalized invitations, messages, and follow-ups.
Invites · Messages · Follow-ups
Like, comment, and publish posts from the same secure connection.
Posts · Comments · Likes
Why the protocol matters
MCP is an open standard for connecting AI agents to tools. For you, that means SalesTouch works with the agent you already use, exposes only the LinkedIn actions you choose, and returns a clear result every time without giving the AI your browser or your credentials.
The advantage is simple: your AI becomes capable without becoming unrestricted.
MCP advantage 01
Claude, Codex, and other compatible agents can use the same SalesTouch connection. You are not locked into one AI client.
MCP advantage 02
Your agent asks for a LinkedIn action by name. It does not need to find buttons or control your screen.
MCP advantage 03
Search, read, message, and publish are separate tools, so you decide exactly what the agent is allowed to use.
MCP advantage 04
Each request comes back with a visible outcome your agent can understand and SalesTouch can log.
Every action crosses multiple safeguards before it reaches LinkedIn. The system slows down or stops when the conditions change.
LinkedIn sees a residential IP matched to the account country, without suspicious location jumps.
Activity stops before it reaches the volume configured for that account.
Actions are spaced through working hours instead of being fired in sudden bursts.
When LinkedIn pushes back, SalesTouch pauses and reschedules instead of retrying aggressively.
Nothing is injected into your browser or into the LinkedIn page you are using.
Credentials stay encrypted and never enter the conversation with your AI agent.
Choose which LinkedIn tools the agent can call and which actions need approval.
SalesTouch watches account signals before every action and pauses new work when conditions look risky.
Why cloud execution changes everything
Claude or Codex decides what should happen. Once the action is handed to SalesTouch, the secure cloud keeps the LinkedIn session, queue, timing, and state alive even if your laptop sleeps or the conversation closes.
Claude or Codex
Workflow handed off successfully
SalesTouch keeps working
Queue, timing, and account state stay online
AI chat
Closed
Laptop
Can sleep
SalesTouch
Still running
Reliable does not mean failures never happen. It means every action has a state, every failure is visible, and queued work can be inspected, cancelled, or recovered without guessing what happened.
The infrastructure behind every action
Build it yourself and you are not building one integration. You are taking responsibility for the connection, safety rules, execution engine, logs, and every account you add. SalesTouch ships that entire operating layer by default.
Before your agent can reliably send one message, you need five production systems working together.
Source residential IPs, persist sessions, encrypt authentication, detect disconnects, and reconnect safely.
Create daily limits, working hours, human pacing, cooldowns, and rules for every risk signal.
Run queues, scheduling, retries, deduplication, and persistent state that survives restarts.
Trace every request, status, error, and retry, then build ways to pause, cancel, and recover safely.
Separate credentials, connections, queues, limits, and state for every LinkedIn identity you add.
And it never becomes “done.”
Monitor it every day, patch it when LinkedIn changes, repair broken sessions, and own every failure across every account.
One MCP connection gives your agent a production-ready LinkedIn operating layer.
Residential IP, encrypted authentication, session health, and reconnection are managed per account.
Limits, pacing, working hours, and cooldowns are checked before every action.
Cloud queues, scheduling, retries, and persistent state keep every workflow running.
Explicit statuses and 90-day activity logs make every action inspectable and recoverable.
Each account stays isolated while your agents control all of them through the same MCP.
You design the workflow. SalesTouch keeps LinkedIn execution safe, reliable, and scalable.
Your agent sits on infrastructure your team must operate.
Your agent calls a tool. The infrastructure is already running.
Multi-account by design
Add founder, sales, team, or client accounts to SalesTouch once. Claude or Codex can then choose the right identity in each tool call without adding another connector.
One connector in your AI client for every account
Select the LinkedIn identity in each tool call
Separate IP, limits, queues, and history per account
Founder at Vela Labs
Head of Sales at Northstar
CEO at Kanso Studio
Connect SalesTouch to the AI agent you already use and give it reliable LinkedIn tools in minutes.
A LinkedIn MCP is a connector that exposes LinkedIn capabilities as typed tools an AI agent can call through the Model Context Protocol. SalesTouch adds OAuth permissions, account protection, queues, cloud execution, and logs around those tools so Claude, Codex, ChatGPT, and other MCP clients can use LinkedIn through one controlled endpoint.
Any third-party tool that acts on LinkedIn carries risk. SalesTouch is designed to reduce that risk with consistent login conditions, conservative action limits, human-paced scheduling, queues, and automatic pauses when LinkedIn pushes back.
No. Your AI client connects to SalesTouch through OAuth and uses specific MCP tools. It never receives your LinkedIn password or 2FA secret. Credentials used for reconnection are encrypted and kept outside the AI conversation.
You choose the operating mode. Start with read-only checks, require approval for sensitive actions, or allow routine workflows to run within the limits and instructions you define.
SalesTouch does not keep retrying aggressively. The action is paused and can be moved into the queue for a later eligible time. If the account needs attention, new actions stop until it is reconnected.
No browser extension is required. Sales Navigator is optional: it unlocks additional search workflows, but profile research, post-engager workflows, conversations, messaging, and publishing can work without it.
You can build a script that performs one action. The difficult part is maintaining authentication, encrypted credentials, account identity, action limits, queues, follow-ups, error recovery, logs, and compatibility as LinkedIn and AI clients evolve.
The orchestration and business reasoning stay in your MCP client, such as Claude or Codex. SalesTouch receives a typed tool request, checks permissions and safety rules, executes it in the cloud, persists its state, and returns the result to your agent.
SalesTouch keeps MCP activity logs for 90 days. You can inspect the tool, request details, account, duration, returned state, and error information to understand whether work ran, entered the queue, paused, or failed.
Yes. SalesTouch plans start with one LinkedIn seat, and you can add seats as your operation grows. Every connected account keeps its own identity, session, action limits, working hours, and queue while remaining available through the same SalesTouch MCP connection.