Find the right people
Search LinkedIn, Sales Navigator, post engagers, and profile viewers.
Search · Sales Navigator · Signals
Safe · reliable · scalable
The LinkedIn MCP built for production.
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.
OAuth protectedHuman-paced queuesStart read-only
Claude
Codex
SalesTouch
LinkedIn MCP
Securely connected
Find prospects
Read profiles and posts
Send messages
Follow up
Publish content
What your AI can do
One connection. Four workflows.
Give Claude or Codex everything it needs to search, understand, contact, and publish on LinkedIn.
Understand context
Read profiles, companies, posts, and conversation history before acting.
Profiles · Companies · Threads
Start conversations
Prepare or send personalized invitations, messages, and follow-ups.
Invites · Messages · Follow-ups
Publish and engage
Like, comment, and publish posts from the same secure connection.
Posts · Comments · Likes
From prompt to action
You ask. SalesTouch executes.
Your AI keeps the reasoning. SalesTouch handles the LinkedIn connection, safeguards, and execution.
- 01
Your agent plans
Claude or Codex turns your objective and context into a typed MCP tool call.
Reasoning stays local
- 02
MCP checks access
OAuth scopes and tool permissions decide which read or write action is allowed.
Permission by tool
- 03
SalesTouch preflights
Account identity, approval rules, working hours, limits, and cooldowns are checked.
Run · queue · approve · pause
- 04
Cloud execution runs
SalesTouch executes securely, persists the state, and returns a traceable result.
Result and logs returned
Account safety
Your account comes first.
Before any action runs, SalesTouch checks identity, timing, limits, permissions, and LinkedIn signals.
Any third-party tool that acts on LinkedIn carries risk. What matters is what happens when conditions change: SalesTouch slows down or pauses instead of forcing the action.
Permission at the tool level
MCP exposes explicit read and write tools. OAuth scopes are checked before execution.
Stable account identity
A consistent residential IP and location for each LinkedIn account.
Human-paced activity
Working hours, daily limits, and naturally spaced actions.
Pressure-aware pauses
When LinkedIn pushes back, SalesTouch pauses instead of forcing retries.
Credentials stay private
Your password and 2FA data never enter the AI conversation.
Reliable by design
Local reasoning. Secure cloud execution.
Claude or Codex keeps the orchestration and business context. SalesTouch runs the LinkedIn action in a managed cloud environment, then sends the result back to your agent.
- Local orchestration
- Your agent reasons, chooses tools, and keeps your workflow context.
- Typed MCP boundary
- Each request has a defined input, permission, and returned state.
- Managed cloud workers
- Sessions, queues, scheduling, and execution stay available after the chat closes.
- 90-day activity logs
- Inspect tool calls, request details, duration, status, and errors.
Execution traceTrace complete
01received
Agent request
messages_send
02allowed
OAuth scope
linkedin:write
03passed
Safety preflight
limits · hours · cooldown
04queued
Routing decision
human-paced queue
05persisted
Cloud result
queued_action_id returned
State
Persisted
Duration
284 ms
Retention
90 days
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.
Build or connect
A LinkedIn MCP is more than a script.
Sending the message is the easy part. Production means managing the connection, guardrails, queues, recovery, and every account around it.
Connection
DIYProxy, sessions, hosting
SalesTouchManaged remote MCP
Account safety
DIYDesign every guardrail
SalesTouchLimits and timing included
Queues
DIYBuild states and retries
SalesTouchQueue and approvals included
Failures
DIYDetect, trace, and recover
SalesTouchLogs, pauses, and recovery included
Multiple accounts
DIYIsolate every setup
SalesTouchAdd accounts independently
Connect once. Keep your focus on the outcome.Ready in about 10 minutes
Ready to scale
One MCP. Every LinkedIn account.
Connect founder, sales, or client accounts without duplicating the infrastructure behind them.
One MCP connection for the whole workspace
Separate limits and queues for every account
Use all accounts together or target one
3 accounts · 1 LinkedIn MCPProtected
FD
Founder account
Personal outreach
SL
Sales account
Conversation follow-up
CL
Client account
Managed campaign
Your LinkedIn MCP is 10 minutes away.
Connect one account, start with a read-only check, then expand when you are ready.
ConnectRead-only checkStart working
LinkedIn MCP questions, answered.
What is a LinkedIn MCP?
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.
Can SalesTouch guarantee that my LinkedIn account will never be restricted?
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.
Can Claude or Codex access my LinkedIn password?
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.
Can my agent send messages without my approval?
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.
What happens when LinkedIn temporarily limits an action?
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.
Do I need a browser extension or Sales Navigator?
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.
Why not build my own LinkedIn MCP?
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.
Where do the AI reasoning and LinkedIn execution happen?
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.
How do logs make LinkedIn automation more reliable?
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.
Can I connect and manage multiple LinkedIn accounts?
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.