Matrix / Use with your agent

Use this site with your agent

Everything on this site is also an MCP server. Connect it once, and Claude or ChatGPT can check which of your sales tools have official MCP servers, what each one can change, whether it uses credits, and which recipes fit your stack. You don't paste anything.

The server URL

No sign-in and no account. The bare domain, https://mcp.mcpforgtm.com, works too. Free, with no credits. Status: Up (checked daily with the other endpoints).

Give it a descriptive name

Your assistant decides whether to use a connector mostly from its name. Call it something like this:

In our tests on 2026-10-18, Claude used the server on its own only under a name like that. Named "StackMCP", it was ignored and Claude answered from general knowledge. ChatGPT used it when we @-mentioned it, and not otherwise. If your assistant answers without it, say "Use Sales Tools AI Connector Facts (StackMCP)" or @-mention it.

Connect it

Tested in Claude and ChatGPT on 2026-10-18. The Claude Code and Cursor steps come from their docs and haven't been tested yet. GitHub Copilot isn't tested.

claude mcp add --transport http stackmcp https://mcp.mcpforgtm.com/mcp

{
  "mcpServers": {
    "stackmcp": {
      "url": "https://mcp.mcpforgtm.com/mcp"
    }
  }
}

Try these prompts

1. Use Sales Tools AI Connector Facts (StackMCP): what can I automate with HubSpot, Gong and Slack?

   Copy prompt

2. Audit my stack: Salesforce, Outreach and ZoomInfo. Which ones can change data, use credits or need an admin?

   Copy prompt

3. Find recipes for an SDR using Apollo.

   Copy prompt

4. Compare the Outreach and Salesloft MCP servers. What can each one change, and do they use credits?

   Copy prompt

What it can and can't do

It has eight tools:

• search_tools (find listed servers by app, access, credits or role)
• get_tool (one listing's facts with sources)
• compare_tools (side-by-side facts)
• find_recipes (recipes that fit a stack)
• get_recipe (one recipe in full)
• build_stack_brief (the /build/ prompt for a stack)
• get_recipe_template (the recipe format)
• submit_recipe (sends a recipe for private review)

It can't see your accounts. It knows which tools exist and what their MCP servers can do, from the vendors' own docs, with the date each fact was checked. It doesn't connect to your CRM, your calls or your inbox: connect those tools' own servers for that. "Not confirmed" means the vendor's docs don't settle a question. It doesn't mean no.

There are no admin controls for this server: no organization approval, scope limits, tool switches or audit log. Your app's own connector settings still apply.

Sharing a recipe

If a workflow works for you, your assistant can send it in as a recipe with submit_recipe, the server's only tool that writes anything:

• Your assistant shows you the full recipe first, and sends it only after you approve it.
• It goes to a private review queue (a private GitHub issue). Nothing is published until it's checked against the recipe rules.
• It can use only tools listed on this site, and link only to mcpforgtm.com and the listed vendors' own sites.
• Contact details are optional, stay private, and are used only to credit you if you want.

You can also send a recipe yourself.

Privacy

• No sign-in, no account and no cookies.
• The server keeps no request logs. Your IP address is used only to limit how many requests one address can make (600 a minute, and 5 recipe submissions a minute).
• The server sees only what your assistant sends to its tools, such as the names of your tools. It doesn't see the rest of your chat.
• Submitted recipes go to a private queue that only the site owner reads.

Other ways to use the facts

• Build a recipe for your stack: pick your tools and copy a prompt, or install the recipe builder as a Claude skill.
• All listings as JSON and llms.txt, free to reuse with credit (CC BY 4.0).
• This server's own listing, with the same fact sections as every tool.