StackSwap — B2B GTM stack intelligence (hosted, Streamable HTTP, 17 tools)

What is StackSwap?

StackSwap is a hosted Model Context Protocol (MCP) server that gives AI clients access to StackSwap's B2B SaaS GTM stack intelligence — including a tool catalog, vendor fact sheets, overlap detection, swap suggestions, stack audits, n-way comparisons, category landscapes, buyer questions, renewal-negotiation playbooks, and a full-text operator knowledge base. It is free, requires no API key, is stateless, and offers 17 tools (16 read-only + 1 write tool for submitting corrections).

How to use StackSwap?

Configure your MCP client to point to the live endpoint https://stackswap.ai/api/mcp using Streamable HTTP transport. For Claude Code, run claude mcp add --transport http stackswap https://stackswap.ai/api/mcp; for Claude Desktop, add a JSON entry to the config file. For other MCP clients (Cursor, ChatGPT Desktop, etc.), add a new HTTP MCP server with that URL — no authentication needed.

Key features of StackSwap

• Hosted MCP server — no local install required
• 17 tools: 16 read-only + 1 write (submit_correction)
• Fuzzy-search 400+ GTM tools with monthly cost
• Hand-verified overlap registry (104 pairs) with savings
• AI-native swap recommendations with annual savings
• Full-text search across 50+ operator articles
• N‑way comparison of 2–6 tools in a markdown matrix
• Renewal-negotiation playbooks per vendor with leverage points

Use cases of StackSwap

• Ask "What does Smartlead cost?" and get tool details with pricing confidence.
• Request "Smartlead vs Apollo for outbound?" and receive a head-to-head comparison plus recommended pick.
• Paste a careers page and infer the company's entire GTM stack with confidence levels.
• Audit a stack (e.g., HubSpot, Salesforce, Outreach, ZoomInfo, Gong) to get current spend, optimized spend, and recoverable savings.
• Inquire "My Salesforce renewal is in 60 days — what's my leverage?" for a renewal-negotiation playbook.

FAQ from StackSwap

How is StackSwap different from running a local stdio MCP server?

StackSwap is hosted — no install friction, always current with the evolving tool catalog and overlap registry, and requires zero local compute. The trade-off is needing an internet connection and that StackSwap sees request volume and tool-call patterns (but no conversation data or user identifiers are stored).

What are the runtime requirements or dependencies?

There are no server-side dependencies for users. Clients only need a JSON parser and an HTTP client — the protocol is plain JSON-RPC 2.0 over HTTP. No API key or authentication is needed.

Where does my data live and is it stored?

The endpoint is stateless. StackSwap does not store conversation data or user identifiers. Only request volume and tool-call patterns are observed for operational purposes.

Are there any rate limits or known transport limitations?

Rate limit: none (reasonable use). CORS: *. Supported protocol versions: 2025-06-18, 2025-03-26, 2024-11-05. Transport is Streamable HTTP.

How do I submit a correction or provide feedback?

Use the submit_correction write tool to submit a catalog correction (pricing, features, gotchas, scores). It is queued for human admin review and never propagates unreviewed. For feature requests or bugs, open an issue on the GitHub repository or email [email protected].