GTM Otto vs Qampi
A side-by-side look at the GTM Otto and Qampi MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Q
QampiSocial MediaLinkedIn outreach from your agent: find prospects, add leads, run campaigns, read results.33EmergingAuth: not declaredVerdict: choose GTM Otto for social media work over a hosted endpoint; choose Qampi for social media. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose GTM Otto when
- You need dedicated capabilities in the Social Media domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
gtm_whoami, gtm_list_plays, gtm_show_play.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Q Qampi | |
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 52/100 · Good | 33/100 · Emerging |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
Tools & capabilities
GTM Otto tools 21
gtm_whoamiOrg, plan, lead meter, and the `next` step to follow. Start here.gtm_list_playsEvery play with product, status, seat and pipeline spread.gtm_show_playOne play in full: ICP, lanes, autonomy ladder, cap, working hours, seat.gtm_play_statsThe pipeline over four windows, each with its delta versus the window before.gtm_linkedin_statusThe play's seat state and today's headroom against LinkedIn's limits.gtm_sources_referenceThe reference for every sourcing lane. Read before configuring one.gtm_show_sourcesAll five lanes of a play: config, switch, blockers, last run, memory.gtm_source_runsRun history of one lane, newest first.gtm_list_approvalsDrafted messages waiting for a human, with their approval ids.gtm_estimate_icp"About N companies match" for a candidate ICP. Writes nothing.gtm_create_playCreate a fully configured play. Draft by default; `activate` flag.gtm_update_icpChange a play's seven ICP facets. Only the ones you name.- +9 more on the listing page
Qampi tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
GTM Otto
{
"mcpServers": {
"gtm-otto": {
"url": "https://agent.gtmotto.com/mcp"
}
}
}
Qampi
No confirmed install command for Qampi yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
GTM Otto is categorized under Social Media and uses a remote HTTP/SSE transport. Qampi belongs to Social Media and uses an install path we have not confirmed yet. Pick GTM Otto for social media work and Qampi for social media.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Qampi has no confirmed install command yet — follow its own setup instructions.
GTM Otto has no declared pricing — check the project's own site. Qampi has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add gtm-otto and qampi as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, GTM Otto has a quality signal of 52/100 (Good) with 0 views, 0 installs and 1 GitHub stars. Qampi has 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.
