Your LinkedIn agent. Inside Claude or ChatGPT.
Tell your assistant who you want to reach. Otto finds the buyers, starts LinkedIn conversations, and follows up. Connect it to the rest of your GTM workflow, with control over what it sends.
Claude, Claude Code, Cursor, ChatGPT. Connect by URL, sign in once. 7-day free trial.
Things to ask
you ›
“Find CFOs at Swiss fintechs who posted about hiring this month and set up a play”
Estimates the audience, drafts the play, previews each lane, then asks before launching.
you ›
“Which of my plays booked conversations this week, and what should I change?”
Reads every play's stats and lane runs, then says what to widen, tighten or pause.
you ›
“Take the companies that replied to my Instantly campaign and warm up their buyers on LinkedIn”
Reads Instantly through its own MCP, loads the companies into an account list lane, and warms the buyers inside.
The difference
Every other MCP hands you a remote. This one hands you a seat.
The pain was never the prompt. It was the piping: the list, the sequence, the seat, and the fact that it all stops when you do. A play removes the piping.
Without
A remote control for a tool you still operate.
- Upload a lead list, then keep it fresh yourself
- Build a message sequence, then babysit it
- Buy a seat per LinkedIn account, rotate them
- Stops the moment the chat ends
With GTM Otto
A play: an ICP, five sourcing lanes, an autonomy level.
- Describe who you want to meet. Lanes rebuild the list daily
- No sequence. One decision per lead, per day, from fresh evidence
- Your own account, one flat price, no seats
- Keeps running after the chat ends. You approve what speaks
The five lanes
- People search: your ICP, rerun daily
- Post discovery: posts matching an intent; commenters and reactors
- Job offers: companies hiring a role: a buying signal
- Account list: up to 100 companies you name; GTM Otto finds the buyers inside
- Post engagers: retired; Post discovery replaces it
The autonomy ladder
Runs alone: Visit, Like, Invite.
Opt-in, each waits for you: Comment, First message, Follow-up, Reply.
Two-day warm-up before any invite. Working hours, per-day caps, full stop on the first warning.
Install
One URL. Sign in once. Ask.
No key to paste. The first call that needs your account shows a Connect card; you sign in in a popup and the assistant retries. Sign-up, the trial and your LinkedIn connection all start from the chat. Scripts and n8n can still use an API key.
Claude
web and desktop- 1Open Settings, then Connectors.
- 2Click Add custom connector.
- 3Paste the URL below and save.
- 4Ask Claude something. On the first protected call it shows a Connect card. Sign in once in the popup and Claude retries the call.
https://agent.gtmotto.com/mcpSign-in: OAuth in a popup, from Claude's inline Connect card. No key to paste.
Claude Code
terminal- 1Run the command below in your terminal.
- 2Start a session and type /mcp, then pick gtmotto and Authenticate.
- 3Sign in in the browser tab that opens. Come back and ask.
claude mcp add --transport http gtmotto https://agent.gtmotto.com/mcpSign-in: OAuth through /mcp, with a loopback redirect. Scripts can pass an API key with --header instead.
Cursor
one click- 1Click Add to Cursor, or paste the deeplink below into your browser.
- 2Confirm the install in Cursor.
- 3Ask in Agent mode. Cursor runs the sign-in on the first protected call.
cursor://anysphere.cursor-deeplink/mcp/install?name=gtmotto&config=eyJ1cmwiOiJodHRwczovL2FnZW50Lmd0bW90dG8uY29tL21jcCJ9Sign-in: Cursor's OAuth flow for remote servers.
ChatGPT
developer mode- 1Open Settings, then Connectors.
- 2Turn on developer mode, then click Create.
- 3Paste the URL below as the server URL and save.
- 4Ask ChatGPT something. Sign in when it asks.
https://agent.gtmotto.com/mcpSign-in: OAuth on the first protected call.
Step-by-step guides per client: /docs/mcp.
What the agent can do
Twenty-one tools. No send verb.
Reads run without asking. Writes create, configure, run and launch. What speaks to a person is drafted by GTM Otto's planner and approved by you. Full reference.
Read
9 toolsRead-only. Your client can run these without a confirmation.
gtm_whoami· Your org, plan, lead meter, and the next step to take.gtm_list_plays· Every play, its status, and whether a LinkedIn seat is connected.gtm_show_play· One play in full: ICP, lanes, caps, hours, autonomy ladder.gtm_play_stats· What a play did and what came back, over four windows.gtm_linkedin_status· Which LinkedIn account is connected and today's headroom.gtm_sources_reference· The five lanes: fields, caps, and what makes each runnable.gtm_show_sources· How each lane of a play is configured, and why one is blocked.gtm_source_runs· A lane's run history: scanned, dropped, added.gtm_list_approvals· Messages the planner drafted that wait for a human.
Write
12 toolsEach one changes something. Runs and launches spend real quota.
gtm_estimate_icp· About how many companies match an ICP. Writes nothing.gtm_create_play· Create a play from an ICP. Draft by default.gtm_update_icp· Change the ICP a play runs on.gtm_update_play· Pause, resume or launch. Set the daily cap and working hours.gtm_configure_source· Set a lane's fields. Can switch it on in the same call.gtm_set_source· Switch a lane on or off.gtm_preview_source· Dry run of a lane: a sample of who it would keep, no leads written.gtm_run_source· Real run of a lane. Real leads, real quota.gtm_forget_harvested_posts· Clear a post lane's memory so the next run judges today's posts again.gtm_connect_linkedin· Returns the link to connect your LinkedIn account.gtm_approve· Approve one drafted message. The agent asks you before each one.gtm_reject· Reject one drafted message. The agent asks you before each one.
What it deliberately can't
It cannot write a message and send it. There is no invite, DM, comment or like verb. The planner drafts; a person approves.
It cannot approve a message on its own. gtm_approve exists, and the agent asks you before each one. What you say no to never goes out.
It cannot go past your account's ceilings. Caps, hours and the 25% margin under LinkedIn's limits are set on the account, not per prompt.
It cannot connect your LinkedIn account for you. gtm_connect_linkedin returns a link. You complete it in the browser.
Your account is the asset
Your reputation comes first.
Most LinkedIn automation gets accounts flagged because it behaves like a bot: bursts, blank invites, the same message to everyone. Otto behaves like a careful person with a good memory.
Stays 25% under LinkedIn's limits
Otto detects your plan and reputation, sets weekly ceilings below the cap, and raises them slowly as your accept rate holds.
Human pacing, your working hours
Actions spread randomly through the day, never in bursts, never at 3am, never on weekends unless you say so.
Every message is different
Written from the lead's context and your positioning, in your voice. No templates, no merge fields, nothing LinkedIn can pattern-match.
Stops on the first warning
If LinkedIn so much as raises an eyebrow, everything pauses and you're told. You can pause any lead, any play, or all of it in one click.
Pricing
Your LinkedIn agent. €99/month.
Turn an underused LinkedIn account into a source of new business. Otto finds buyers, writes personal messages, and follows up. One flat price. No lead cap.
Your first 7 days are free. We take your card at checkout and charge it when the trial ends — cancel before then and you pay nothing.
Annual saves about 16%. €999 a year instead of €1,188.
Cancel any time, from your billing settings.
VAT added at checkout where it applies.
One subscription covers the browser app and access from Claude or ChatGPT. Otto manages activity within your account limits.
Starter
€99 / mo
No lead cap. One agent for finding buyers, starting conversations, and following up.
- All five lead sources, running daily
- Personal outreach and follow-ups in your voice
- Reply drafts and meeting coordination
- Unlimited plays · unlimited actions per lead
- Conservative limits, pacing, and approval controls
The MCP, answered
What is MCP?
The Model Context Protocol. It is how an assistant like Claude, Cursor or ChatGPT connects to an outside tool and calls it. GTM Otto is an MCP server: add one URL to your client and the assistant gains the tools to describe who you want to meet, set up a play, read the results, and approve the messages that wait for you.
Is my LinkedIn account safe?
The same safety system as the cockpit runs underneath, whatever the prompt says. GTM Otto stays 25% under LinkedIn's limits, warms each person for two days (visit, like, then invite), works inside your hours, respects per-day caps, and stops on the first warning. The assistant cannot raise a ceiling.
What does the MCP cost?
Nothing extra. It is part of the one GTM Otto plan, with a 7-day free trial. Sign-up and the trial start from the chat; your card is taken at checkout and charged when the trial ends.
Which clients work?
Claude web and desktop, Claude Code, Cursor and ChatGPT, and any client that speaks MCP over Streamable HTTP. You connect by URL and sign in once in a popup. Scripts and n8n can use an API key instead.
How fast can I start?
A few minutes. Add the URL, ask for a play, sign in when the Connect card appears, connect your LinkedIn account from the link the assistant gives you, preview the lanes, and say go. First invites land around day two, after the warm-up.
Can Claude message people for me?
No, and by design. The server has no invite, message, comment or like verb. GTM Otto's planner drafts each message from the person's context, in your voice; the assistant can only approve or reject a draft, and it asks you before each one. Nothing is said without you.
Do I still need the cockpit?
Not for the daily work. Everything a play needs can be done from the chat. The browser opens for three steps only: sign-up and the trial, connecting your LinkedIn account, and, if you prefer it, approving messages in a list instead of one by one.
Your next customer is on LinkedIn today.
Add the URL, describe who you want to meet, and let the seat work.
Add to Claude