Skip to main content
GTMAPIs supports agent workflows as a developer-experience layer for API-first GTM infrastructure. The primary buyers are still outbound agencies and GTM engineers who need reliable validation workflows, predictable credit economics, and clear result semantics. There are two MCP connection modes:

Hosted MCP

Hosted MCP does not require users to paste unrestricted live API keys into remote agent clients. MCP clients connect to:
The hosted endpoint uses MCP Streamable HTTP and the MCP HTTP authorization flow: Hosted MCP currently exposes the first safe tool slice: Hosted tokens are audience-bound to https://www.gtmapis.com/api/mcp; they are not public API keys and are not forwarded to the public validation API.

Local MCP

The local package runs as a stdio MCP server and calls the canonical public API with a restricted GTMAPIs API key from the local MCP client environment. Product-backed tools are registered only for the active public product catalog. Premium Catch-All Recovery uses recovery-specific scopes and tools.

Create a Scoped Local Agent Key

1

Open API Keys

2

Create a restricted key

Choose only the scopes the local agent needs. For credit lookup, select credits:read. For single validation, select email:validate:single. For bulk validation and async jobs, select email:validate:bulk.
3

Store it in the MCP client config

Put the key in the client environment as GTMAPIS_API_KEY. Do not paste unrestricted live keys into shared agent configs.

Claude Desktop Local Setup

After the package is available in your package manager, add this server to your Claude Desktop MCP configuration:
For local development from a checkout of this repository, use an absolute path:
Restart Claude Desktop after editing the config.

Generic Local MCP Client

Use stdio transport and launch the server as a local process:
GTMAPIS_BASE_URL is optional. Leave it unset for production so tools call the canonical public API host.

Example Agent Requests

Ask your MCP-enabled agent:

Security Notes

  • Hosted MCP uses bearer tokens issued for https://www.gtmapis.com/api/mcp; do not send public API keys as hosted MCP bearer tokens.
  • Local MCP uses X-API-Key credentials through the MCP client environment, not browser code.
  • Create a restricted key per local agent or automation.
  • Revoke local API keys from the dashboard when an agent, contractor, or workflow no longer needs access.
  • Use /v1/validate/bulk or /v1/validate/batch for multi-email public API workflows instead of asking an agent to fan out many single-email calls.
  • Use only products and operations in the current public catalog.

Authentication

Create keys, understand scopes, and store credentials safely.

OpenAPI Spec

Machine-readable public API reference for available-now endpoints.

Quickstart

Make your first validation request.

Rate Limits

Build agent workflows that respect retry and rate-limit headers.