How to Connect AtomicMCP to Claude
AtomicMCP connects your Atomicat workspace to Claude so you can ask questions, review pages, analyze funnels, and work on marketing tasks through natural language. Claude is the recommended AI client for page creation, page editing, cloning, and multi-step Atomicat workflows.
This guide walks through the full connection setup from start to finish.
What You Need Before Connecting
| Requirement | Why it matters |
|---|---|
| Atomicat account with AtomicMCP access | The connector reads data from your workspace. |
| Claude account with custom connector support | Connector settings must be available in your Claude plan. |
| Correct workspace signed in to Atomicat | The MCP URL ties to the workspace you authenticate with. |
| Trusted device/browser | You will complete an Atomicat sign-in during setup. |
AtomicMCP is different from MIA, which is Atomicat's built-in assistant. Use AtomicMCP when you want to work from Claude and bring Atomicat context into that environment.
Step 1: Copy Your MCP Server URL from Atomicat
- Log in to Atomicat.
- Open AtomicMCP from the sidebar (under Tools).
- Find Your MCP Server URL on the AtomicMCP screen.
- Click Copy URL.
The URL is a sensitive connection detail—share it only with trusted teammates. See MCP Server URL for security guidance.
Important: Some AI clients need the full endpoint with /mcp appended. If Claude rejects the base URL, try the same URL ending in /mcp.
Step 2: Open Claude Connector Settings
- Open Claude (web or desktop, depending on your setup).
- Go to Settings.
- Open Connectors.
- Choose Add custom connector (or the equivalent option in your Claude version).
Connector labels can vary slightly by Claude rollout. Look for Connectors, Integrations, or Custom connectors.
Step 3: Paste the MCP Server URL
- In the connector setup form, paste the MCP Server URL you copied from Atomicat.
- Name the connector clearly (for example Atomicat or AtomicMCP).
- Save or continue to the authentication step.
Always copy the URL fresh from the AtomicMCP screen. Do not reuse old screenshots, shared notes, or URLs from another workspace.
Step 4: Authenticate with Atomicat
- When Claude prompts you to connect, follow the sign-in flow.
- Log in with the Atomicat account that should access the workspace.
- Approve the connection when asked.
If the wrong account opens, sign out of Atomicat in your browser and repeat authentication with the correct user.
Step 5: Enable AtomicMCP in a Claude Conversation
Adding the connector does not automatically activate it in every chat.
- Start a new Claude conversation or open an existing one.
- Open the connector or tools menu inside the chat.
- Enable AtomicMCP (or your named Atomicat connector) for that conversation.
You should now be able to ask Atomicat-related questions in that chat.
Step 6: Test the Connection
Start with a simple, low-risk prompt to confirm the connector works:
- “Show me my top pages this month.”
- “Review my landing page structure and suggest conversion improvements.”
- “Help me plan a new product page for this offer.”
If Claude responds with workspace-aware context, the connection is working. If not, see Troubleshooting below.
What You Can Do After Connecting
| Use case | Example prompt |
|---|---|
| Page review | “Review my landing page for headline clarity and CTA placement.” |
| Page editing | “Suggest improvements to the hero section on my sales page.” |
| Funnel analysis | “Compare funnel performance for the last 30 days.” |
| Lead review | “Summarize recent leads and common patterns. ” |
| Quiz planning | “Turn this offer into a quiz funnel with qualifying questions.” |
Claude is especially strong for step-by-step builder work and multi-step workflows that touch pages, funnels, or cloning.
Best Practices
- Be specific about the page, funnel, project, or date range you want Claude to inspect.
- Ask Claude to explain before making changes when the task affects live pages or funnels.
- Review every suggestion in Atomicat before publishing, deleting, or sending traffic.
- Keep passwords, payment data, and private customer records out of prompts.
- Reconnect after AtomicMCP updates if Atomicat shows a newer version is available.
See MCP security and Example prompts for more guidance.
Troubleshooting
| Problem | What to try |
|---|---|
| AtomicMCP not visible in chat | Enable the connector in the current conversation's tools menu. |
| URL rejected | Copy the URL again; try appending /mcp if Claude expects the full endpoint. |
| Wrong workspace data | Re-authenticate with the correct Atomicat account. |
| Tools list looks outdated | Check version status on the AtomicMCP screen and reconnect. |
| Claude cannot edit pages | Confirm permissions and ask Claude to plan first; review in Atomicat before publishing. |
Outcome
Claude is now connected to your Atomicat workspace through AtomicMCP. You can ask marketing questions, review assets, and run guided workflows from Claude while keeping Atomicat as the source of truth for live changes.
Related Docs
FAQ
Why does Claude not see AtomicMCP in a chat?
The connector may be installed but not enabled for that conversation. Open the connector or tools menu inside Claude and turn on AtomicMCP for the current chat.
Should I use Claude or ChatGPT for editing pages?
Claude is the stronger recommendation for page creation, page editing, cloning, and workflows that need careful step-by-step structure in the builder.
Is the MCP Server URL a password?
No, but it is still a sensitive connection detail. You must authenticate with Atomicat during setup, and you should only share the URL with trusted workspace users.
Do I need to reconnect after an AtomicMCP update?
Yes, when Atomicat shows a newer MCP version is available. Reconnecting reloads the latest tools and behavior in Claude.
Can Claude publish pages automatically?
Claude can suggest changes and guided actions, but you should always review and approve changes inside Atomicat before publishing live pages or funnels.