StackSwap MCP

A hosted Model Context Protocol server that gives AI clients access to StackSwap's B2B SaaS GTM stack intelligence — tool catalog, overlap detection, AI-native swap suggestions, stack audits, and partner recommendations.

Live endpoint: https://stackswap.ai/api/mcp Docs: stackswap.ai/mcp Status: Free, no API key, stateless, read-only.

This repo contains public documentation, JSON schemas, and an example client for the hosted MCP server. The server itself is closed-source — it runs as part of stackswap.ai and wraps the same scan engine and tool catalog that powers the web product.

Install

Claude Code

claude mcp add --transport http stackswap https://stackswap.ai/api/mcp

For user-scope (available in every session, not just one project):

claude mcp add --transport http --scope user stackswap https://stackswap.ai/api/mcp

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "stackswap": {
      "url": "https://stackswap.ai/api/mcp",
      "transport": "http"
    }
  }
}

Restart Claude Desktop. A tools indicator appears in the chat compose box.

Cursor / ChatGPT Desktop / Other MCP clients

Add a new HTTP MCP server with URL https://stackswap.ai/api/mcp. No authentication.

Tools

Eight read-only tools. Schemas are in schemas/tools.json (extracted directly from the live tools/list response).

Example usage

Once installed, ask any of the following in your AI client and Claude will route to the right tool:

Tool descriptions are model-readable, so you don't need to know the tool names — Claude picks based on the question.

Example client

A minimal TypeScript example that connects, lists tools, and runs find_overlaps is in examples/client.ts.

npx tsx examples/client.ts

The protocol is plain JSON-RPC 2.0 over HTTP — any language with a JSON parser and an HTTP client can call it.

Endpoint details

Why hosted, not stdio

StackSwap's MCP server runs inside the existing stackswap.ai Next.js application as a single route handler. Hosting it ourselves means:

• No install friction — one claude mcp add line, no npm/pip dependency

• Always current — the underlying tool catalog, overlap registry, and swap data update as the StackSwap product evolves

• Zero local compute — the scan engine runs server-side; clients just send JSON-RPC

The trade-off: it requires an internet connection, and we (StackSwap) see request volume and tool-call patterns. We don't store conversation data or user identifiers — the endpoint is stateless.

Requests, issues, feedback

Open an issue if you want a tool added, a behavior changed, or you've hit a bug. The MCP surface is shaped by what operators actually ask about.

Contact: nick@stackswap.ai

License

MIT — see LICENSE.

This license covers the public documentation, JSON schemas, and example clients in this repository. It does not cover the closed-source server implementation that runs at stackswap.ai/api/mcp.