Skip to main content

MCP Server URL

The MCP Server URL is the connection address your AI client uses to reach AtomicMCP. Atomicat shows the base server URL on the AtomicMCP screen with a copy button. Connector setup may require the endpoint to end in /mcp, depending on the AI client.

How to use it​

  1. Open AtomicMCP in Atomicat.
  2. Find Your MCP Server URL.
  3. Click Copy URL.
  4. Paste it into the connector setup flow in your AI client.
  5. If the client asks for the full MCP endpoint, use the copied URL with /mcp appended.
  6. Sign in to Atomicat when the AI client asks you to authenticate.

Atomicat also shows connection tabs for supported clients, including Claude, ChatGPT, and desktop-style setup. The desktop configuration shown by Atomicat uses an HTTP transport and a server entry named atomicat.

Keep it accurate​

Always copy the URL from the current Atomicat interface. Do not rely on old screenshots, shared notes, URLs copied from another workspace, or values pasted into a previous AI-client setup.

Atomicat's MCP page also shows current and connected version information when available. If Atomicat says an update is available, reconnect or refresh your connector so the latest tools, descriptions, and fixes become available in your AI client.

What the connector unlocks​

AtomicMCP is designed so AI clients can work with Atomicat marketing context, including pages, analytics, funnels, and leads when tools and permissions allow it. The exact available tools can change by MCP version and account permissions, so use the AtomicMCP screen as the source of truth.

Security guidance​

  • Share the URL only with trusted workspace users who are allowed to connect AI tools.
  • Do not post the URL in public chats, tickets, documents, or videos.
  • If someone leaves your team, review connected tools and account permissions.
  • Use your own Atomicat login during connection; do not share credentials.
  • Approve MCP tool calls carefully in your AI client, especially actions that can edit pages, read leads, or change campaign assets.

Troubleshooting​

  • If a client rejects the base URL, try the full endpoint ending in /mcp.
  • If tools do not appear, reconnect the client and complete Atomicat authentication again.
  • If the client shows an old tool list, check the version status on the AtomicMCP page and reconnect.
  • If authentication opens the wrong account, sign out of Atomicat in the browser and repeat the connection with the correct user.
  • If your AI client does not support remote MCP connectors, use one of the client-specific guides linked below.

Frequently asked questions​

Is the Server URL my password?

No, but it is still a sensitive connection detail. Atomicat authentication is required during setup, but you should only share the URL with trusted users.

What if the copied URL does not work?

Copy it again from Atomicat, make sure you are signed in to the right workspace, and check whether your AI client supports remote MCP connectors.

Should I paste the base URL or the /mcp URL?

Use the format your AI client asks for. Atomicat displays the base server URL, while connector configuration often uses the same URL with /mcp appended.

Why do I need to reconnect after an update?

Reconnecting lets the AI client reload AtomicMCP's latest tools, descriptions, and versioned behavior.