AtlasGTM MCP lets compatible AI clients such as Claude securely interact with a user’s AtlasGTM workspace through the Model Context Protocol (MCP).
After you connect, you can use MCP to work with your AtlasGTM go-to-market data and perform supported actions from your AI client—without leaving that client.
Before you connect
You need:
- An AtlasGTM account
- MCP access enabled for your AtlasGTM account
- A Claude account and client that supports MCP connectors
- Permission to approve the OAuth connection for that AtlasGTM account
Connect AtlasGTM MCP to Claude
AtlasGTM MCP uses a standard OAuth authorization flow. You do not paste passwords or API keys into Claude.
- Sign in to AtlasGTM.
- In Claude, start adding the AtlasGTM MCP connector.
- Claude opens the AtlasGTM authorization flow.
- Sign in to AtlasGTM if you are prompted.
- Review the requested permissions.
- Approve the connection.
- Return to Claude.
- AtlasGTM MCP is available for supported prompts and actions.
MCP endpoint: https://connect.atlasgtm.io/api/mcp
Paste this URL when Claude asks for the AtlasGTM MCP server URL. Complete authorization in the browser when prompted.
What AtlasGTM MCP can do
What you can do depends on the permissions granted to the connected AtlasGTM account. Typical customer capabilities include:
Surfaces
- Read AtlasGTM surfaces
- Create or update supported surface requests
GTM / DNA
- Read GTM/DNA information in your workspace
- Create or update supported GTM/DNA information
Brand
- Read supported brand information
- Create or update supported brand information
Agents
- Read supported agent information
Sites
- Create and manage supported site content and actions
- Publishing may require the appropriate permission and confirmation
Permissions
The connector can only perform actions allowed for the connected AtlasGTM account. Standard customer-facing permissions include:
surfaces.read— Read your Atlas Surface requests (revenue kits, pages, and apps).surfaces.write— Create supported Atlas Surface requests from your MCP client.dna.read— Read your Product & GTM DNA profiles.dna.write— Create or update supported Product & GTM DNA data.brand.read— Read supported Brand Studio kits and design tokens.brand.write— Create or update supported Brand Studio kits.agents.read— Read your activated Atlas agents.sites.write— Create, edit, and publish static sites in your own AtlasGTM workspace. Publishing may require confirmation.
If an action is not available, the connected account may not have that permission.
Example prompts
Try prompts like these after the connector is connected. Write or publish actions may require additional permission or confirmation.
- “Show me my AtlasGTM surfaces and summarize their current status.”
- “Show me the GTM/DNA information available in my AtlasGTM workspace.”
- “Create a draft AtlasGTM site using the information available in my workspace, but do not publish it.”
Optional multi-step example: “Review my available GTM information, create a draft surface based on it, and prepare a draft site without publishing anything.”
Troubleshooting
I receive a 401 or authentication error
The OAuth connection may not be authenticated, or it may have expired. Reconnect or re-authorize the AtlasGTM connector in Claude, then try again.
MCP access is not available
The AtlasGTM account used for the connection must have MCP access enabled. Sign in to AtlasGTM, confirm MCP access for that account, and retry the connection.
An action says I do not have permission
The requested action may require a capability that is not available to the connected account. Use an account that has the needed permission, or choose a prompt that matches the permissions you approved. Do not try to bypass permissions.
The connector is not responding
Reconnect the AtlasGTM connector and retry. If the problem continues, contact AtlasGTM support.
Privacy and data handling
AtlasGTM MCP operates against the connected AtlasGTM workspace. Only connect an account you are authorized to use. Data available through the connector is the data that account can already access in AtlasGTM.
For details about how AtlasGTM collects and uses personal information, see the AtlasGTM Privacy Policy.
Security
- Never share passwords in prompts.
- Never share OAuth tokens or client secrets.
- Only authorize AtlasGTM MCP for an account you are authorized to use.
- Review requested permissions before you approve the connection.
Support
Questions or privacy requests: support@atlasgtm.io