gtmmcps.Find a tool

Connection guide

Give your agent
a tool it can use.

Find the server, add it to your client, then check which tools it exposes. The walkthrough below shows where each part fits.

HOSTED GTMMCPs MCP

Find the right tools from your agent.

Connect your MCP client to search the catalog, read tool records, and retrieve cited documentation passages. The service runs on Cloudflare and is available without this computer running.

MCP endpoint

https://gtmmcps-knowledge.andrew-e2b.workers.dev/mcp

Streamable HTTP. Protocol version 2025-03-26. No vendor credentials are needed for directory queries. No API key is currently required.

Cursor configuration

{
  "mcpServers": {
    "gtmmcps": {
      "url": "https://gtmmcps-knowledge.andrew-e2b.workers.dev/mcp"
    }
  }
}

Add this entry to your existing ~/.cursor/mcp.json.

Search across GTM workflows, including prospecting, enrichment, outreach, marketing, and RevOps. Records distinguish official, community, and unknown MCP support. Discovery is expanding; the catalog does not yet include every GTM MCP.

get_changes
Read retained catalog and documentation observations by tool or date, with pagination. A first observation is not a product launch. Check retention and truncation flags before describing the history. Read recent observations.
search_discoveries
Browse or search potential MCPs by task or name, with pagination and source receipts. These records are discovered, not vendor-verified or tested. Browse the discovery snapshot.
compare_contact_data
Compare initial MoltSets and FullEnrich research by work email, personal email, or mobile phone. Keep the source dates and ask for volume and coverage requirements before judging cost.
find_mcps
Find candidates by task, with optional official support and API access filters.
get_tool_record
Read a tool record with sources and documentation coverage.
ask_documentation
Retrieve brief cited passages for a tool and question. Your agent composes the answer and preserves any evidence gaps.

Start with the job.

Ask your agent: “Which tools can find contact information, and what access do they require?” It can search candidates, inspect the research, and follow the documentation evidence.

Compare contact-data options.

Ask: “Compare MoltSets and FullEnrich for work emails or mobile numbers.” The compare_contact_data tool returns sourced pricing, access, signup links, and missing cost inputs. It does not establish a globally cheapest option or create vendor accounts.

Documentation coverage is partial. A retrieved passage does not establish that an integration works. Keep source URLs and retrieval dates in answers; say when the evidence does not answer the question. This service searches research and documentation; it does not run actions in the listed GTM tools.

Use the HTTP API directly

POST JSON to https://gtmmcps-knowledge.andrew-e2b.workers.dev/api/query with a tool name and arguments:

{
  "tool": "find_mcps",
  "arguments": {
    "task": "find work email addresses",
    "official_only": true,
    "limit": 5
  }
}

Tool schemas · Service health · Service discovery JSON

From tool list
to tool call.

MCP gives an agent a way to use software.
Select a step to see what happens.

DiscoveryGTMMCPs

Records and source links

Your workspaceAgent + client

Task and permissions

ConnectionMCP server

Tools and input schemas

ExecutionGTM tool

Action and result

Directory record

Start with the tool you need.

Use the directory to find a vendor or community MCP server. Open the cited docs and check the endpoint, access requirements, and last-checked date.

Illustrated workflow. This page does not connect to a server or make tool calls.

Try a documented endpoint.

Exa publishes this hosted MCP URL. Its documentation describes anonymous access with rate limits; some capabilities require authentication. This example was checked against Exa’s documentation on 17 October 2026. It is separate from the catalog’s September research snapshot.

Hosted server URL

Use this in a client that supports remote MCP servers.

https://mcp.exa.ai/mcp

Cursor configuration

Add this entry to ~/.cursor/mcp.json. Keep any servers already in your file.

{
  "mcpServers": {
    "exa": {
      "url": "https://mcp.exa.ai/mcp"
    }
  }
}

Source: Exa setup guide and Exa server documentation.

Check the tools before using them.

Once the client can reach the server, ask it to list the available tools. Check the tool description and required inputs before making a call. For example, Exa documents a web search tool named web_search_exa. Let the client read its current schema rather than copying stale arguments from a tutorial.

Hosted server

The client sends MCP requests to a server URL. Authentication, limits, and available tools depend on the provider.

Local server

The client starts an installed program and communicates over standard input and output. A repository link is where you find setup instructions; it is not a remote MCP endpoint.

Let the client handle the protocol.

MCP setup depends on the protocol version supported by the client and server. Older versions use an initialization handshake. The 2026-07-28 specification uses self-describing requests and optional server discovery. Use a compatible client or SDK instead of assuming every server follows the same handshake.

Source: MCP specification update.

Read the catalog as an agent or browse GTM tools.