GTM Otto
MCP server by GTM Otto · mcp
GTM Otto grows a company on LinkedIn: a PLAY sources people who match an ICP through up to five SOURCING LANES, warms them (visit → like → comment), invites them and opens a conversation — with a human gate on anything that speaks. How to work with it: 1. gtm_whoami first. Every read (gtm_whoami, gtm_list_plays, gtm_show_play) carries a next field — the one step to take now (choose_plan, create_play, connect_linkedin, configure_sources, activate, approve_messages, warming_up, …) with the tool or URL for it. Follow it instead of guessing. 2. Not signed in yet? gtm_whoami and gtm_sources_reference work anyway. The first protected call shows the human a Connect card (OAuth); after they sign in, retry the same call. Plan and LinkedIn are chosen from the chat too: next hands back the URL or gtm_connect_linkedin's link. 3. Read gtm_sources_reference BEFORE configuring a lane. Lanes are addressed by (playId, key); configuring ≠ switching on; a lane with nothing to run on is refused when…
Endpoint: https://agent.gtmotto.com/mcp
Verification: observed. Source: crawl.
Capabilities (25)
- gtm_whoami
- gtm_list_plays
- gtm_show_play
- gtm_play_stats
- gtm_linkedin_status
- gtm_estimate_icp
- gtm_create_play
- gtm_sources_reference
- gtm_show_sources
- gtm_source_runs
- gtm_configure_source
- gtm_set_source
- gtm_preview_source
- gtm_run_source
- gtm_forget_harvested_posts
- gtm_update_icp
- gtm_update_play
- gtm_connect_linkedin
- gtm_list_approvals
- gtm_approve
- gtm_reject
- first_play
- weekly_review
- instantly_handoff