Atarim MCP: Connecting Claude, Codex, and Other Coding Agents

If your developers work inside an AI coding assistant — Claude, Codex, or something similar — Atarim MCP connects that assistant directly to your workspace. Once connected, it can read tasks, look up sites, and even trigger approved actions on its own, so a client request captured in Atarim can turn into working code without anyone manually copying details across. Setup is short: copy your Server URL from Atarim, add it to your assistant, and approve a one-time browser prompt — the sections below walk through each part, including the exact setup for Claude, Codex, and other MCP-compatible tools.

Step-by-Step Guide

What This Actually Does

Think of it as a direct line between Atarim and your developer’s AI assistant. Normally, if a client leaves a request in Atarim, someone has to read it, understand it, and go explain it to whatever tool they’re coding in. With Atarim MCP connected, the assistant can just look the information up itself — what site it’s about, what the task says, what’s already been done. “MCP” stands for Model Context Protocol, an open standard that a growing number of AI tools support for exactly this kind of connection — Atarim is simply one of the things they can connect to.

Concretely, once connected, your assistant can:

• Read and manage tasks — pull up a task’s full content, change its status or priority, assign it, tag it, or break it into subtasks, all without anyone switching over to Atarim to do it manually.
• See every site and client in the workspace — list projects, look up a specific site’s details, screenshots, or pages, and check who a client is before starting work.
• Work with your workflows — list, create and edit them, check a draft before saving, switch them on or off, run one on demand, review past runs, and subscribe to a template.
• Manage clients (Beta) — invite a client and create their workspace, set an agency-funded client’s monthly credits, and record engagement value, notes and request allowance.
• See what is waiting for approval — list what is in each project’s Approval Queue (Beta), and record your approve or decline.
• Apply a task’s Do It suggestion to the WordPress site. On a published, private or scheduled page this waits for your approval.
• Produce reports and assets — create and edit reports and pages (artifacts), generate images, take screenshots, convert files, and run Lighthouse and keyword-trend checks.
• Use built-in prompts for a client update, a PM summary, recent activity and what needs attention.
• Trigger an AI design review on a specific page or graphic directly from the conversation.
• Run SEO research — look up search volume, keyword difficulty, competitors, backlink profiles and what’s actually ranking, without leaving the conversation for a separate SEO tool.
• Work on a linked Duda site — connect an Atarim project to a site in your Duda account, then work with its content, store and site data the same way.
• Fire a Zapier action on demand — run a single action on your connected Zapier account when it’s needed, rather than waiting for a Zap to trigger on its own.
• Handle the work around the work — folders, milestones, tags, reference documents and the project’s plugin stack are all reachable too, so an assistant can set a job up and close it out, not just do the middle part.
• Make real changes on a connected WordPress site through the same bridge the rest of Atarim uses — not just read information, but actually execute WordPress actions your assistant has access to. That reach includes the two heaviest jobs on the site: running WP-CLI for work no other action covers, and scanning the site for known vulnerabilities in its plugins, themes and core. Both are described in the Atarim WordPress plugin article.

That last point is the one worth being precise about: connecting your assistant this way doesn’t loosen any of Atarim’s existing safeguards. If something your assistant tries to do would normally need your sign-off in the Approval Queue, it still does. Your assistant has to ask you, and can only record a yes or no that you have clearly given. Connecting MCP changes how the request reaches you, not whether it still needs your approval.

Where to Turn It On

The Server URL is the only thing you need to copy. Authentication is handled for you.

Instructions:

1. In Atarim, from the main dashboard, select Settings.
2. Under Connected Apps, select Atarim MCP.
3. Under Connect an agent, pick Claude, Codex or Other. The setup lines for that agent appear below it, each with a copy control, and a message confirms Copied to clipboard. Claude shows two: a command to run in your terminal for Claude Code, and the server URL, https://api.atarim.io/v1/mcp, for Claude Desktop or claude.ai. Codex shows a command with the address already in it. Other shows the server URL. For the steps below, copy the server URL.
4. Switch to Claude and open Settings, then Connectors.
5. Select Add at the top right, then Add custom connector.
6. In the first field, enter a name: Atarim.
7. In the second field, paste the Server URL you copied.
8. Leave OAuth Client ID and OAuth Client Secret empty — Atarim registers the client automatically.
9. Select Add.
10. A browser page opens headed Connect Claude to Atarim. It explains that Claude will act as you, across every workspace and site you can access. If you aren’t signed in to Atarim, you’ll sign in first and return here.
11. Select Connect. The button shows Connecting…, then the page confirms You’re connected.
12. You’re returned to Claude automatically. If not, select Close this tab.
13. Back in Claude, confirm Atarim now appears in your connector list.
14. Test it — ask Claude which Atarim workspaces you have access to. You should see your own workspaces named back, not a generic answer.

The Browser Prompt You’ll See

After you add the Server URL to your assistant, expect one extra thing to happen the first time:

1. Your assistant opens a browser tab pointing at Atarim.
2. The page explains that your assistant will act as you, across every workspace and site you can access.
3. Select Connect to authorize it — this is a standard, secure login step (OAuth), not an error.
4. Close the tab. Your assistant is now connected.

This happens automatically as part of adding the URL in the steps below — you don’t need to go looking for it, just don’t be surprised when a browser window pops up mid-setup.

Choosing Your Setup Path

All three paths use the same Server URL — the difference is only in how you hand it to your assistant:

Connecting Claude

Claude Code (command-line):

Add Atarim:

claude mcp add --scope user --transport http atarim https://api.atarim.io/v1/mcp

Start Claude Code:

claude

Manage servers (typed inside Claude Code, not the terminal):

/mcp

List servers:

claude mcp list

Remove Atarim:

claude mcp remove atarim --scope user

Check it’s installed:

claude --version

Claude Code

Claude Code is configured from the terminal rather than a settings screen, and the server is added per project unless you say otherwise.

Instructions:

1. Open a terminal.
2. Run the following, using the Server URL copied from Atarim:claude mcp add --transport http atarim https://api.atarim.io/v1/mcp
3. To make Atarim available in every project rather than only the current one, include --scope user:claude mcp add --scope user --transport http atarim https://api.atarim.io/v1/mcp
4. Start a new Claude Code session.
5. Enter /mcp to open the list of MCP servers.
6. Select atarim, then choose Authenticate.
7. Complete the approval step in the browser tab that opens.
8. Return to the terminal. Atarim now shows as connected.

Claude Desktop:

Atarim isn’t listed in Claude’s connector directory, so it’s added as a custom connector.

Instructions:

1. In Atarim, copy the Server URL from Settings → Atarim MCP.
2. In Claude, open Settings, then Connectors.
3. Select Add, then Add custom connector.
4. In the first field, enter a name: Atarim.
5. In the second field, paste the Server URL: https://api.atarim.io/v1/mcp
6. Leave OAuth Client ID and OAuth Client Secret empty. Atarim handles this automatically.
7. Select Add.
8. Complete the approval step described above.
9. Atarim now appears in your connector list, and its tools are available in conversations.

Connecting Codex

Codex uses the same Server URL, entered through its own command.

Instructions:

1. Open a terminal.
2. Run the command below, using your actual Server URL from the Atarim MCP settings page.

codex mcp add atarim --url https://api.atarim.io/v1/mcp

If you prefer editing the settings file directly instead of using that command, add these lines to it:

[mcp_servers.atarim]
url = "https://api.atarim.io/v1/mcp"

Other MCP-compatible tools

MCP is an open standard, so the shape of this is the same anywhere: find the connector settings and paste the URL.

Instructions:

1. Open that assistant’s own settings.
2. Look for a Connectors, Integrations or MCP servers section. MCP is an open standard, so most AI coding assistants support this even without Atarim-specific instructions.
3. Paste in the Server URL from Atarim.
4. If asked for a connection type, choose remote or HTTP rather than a locally-run option — Atarim’s server is on the web, not on your computer.
5. Complete the approval step.

Once connected, the server identifies itself as Atarim, so that’s the name to look for in your assistant’s server list.

Confirming it worked

Worth doing properly — a connector that reports as connected can still be pointed at the wrong workspace.

Instructions:

1. Check that your assistant lists Atarim as connected. In Claude Code, enter /mcp; in Codex, run codex mcp list.
2. Ask a question that confirms both the connection and what it can reach:Which Atarim workspaces do I have access to?You should see the workspaces your Atarim account already has — and nothing else.
3. Then try a real lookup:List the open tasks on [site name] in Atarim.

If the assistant answers generally without naming real workspaces or tasks, it isn’t reaching Atarim. Check that it lists Atarim as connected, and that you completed the approval step rather than closing the browser tab early.

What your assistant can access

Nothing extra. A connected assistant can see and act on exactly what your own Atarim account can — no more. There’s no separate permissions screen to configure; the connection follows the access rules your account already has.

Each person connects with their own Atarim account, so everyone’s assistant is limited to their own access. If you want to limit what an assistant can reach, adjust what that person’s Atarim account can reach.

Anything that would normally need your approval stays gated. Your assistant can tell you a request needs a decision, but it can’t make that decision for you.

Working with WordPress sites

Reading and managing Atarim data works for any site in your account. Acting on a website itself — editing content, changing settings — requires the Atarim plugin installed and connected on that site.

Your assistant identifies a site by its Atarim record rather than its web address, so it will usually list your sites first to find the right one.

Some actions wait for your approval before anything happens: installing or activating a plugin; WordPress actions the site marks as destructive, such as updating or deleting a plugin, replacing a theme file or running WP-CLI; edits to published, private or scheduled pages; Do It on a published page; and any change to a connected rocket.net or InstaWP account. Your assistant pauses and asks you to approve or decline. A request nobody decides on within 14 days is declined automatically, and nothing runs. Reading, Atarim tasks and comments, Duda changes and Zapier actions run straight away.

Credits

Most actions over MCP are free in Atarim, because your assistant does the thinking. A few draw on your Atarim credits: AI design reviews, SEO research, image generation, and asking an Atarim AI expert to reply on a task.

Disconnecting

Disconnect from within your assistant:

• Claude: Settings → Connectors, then remove the Atarim connector.
• Claude Code: claude mcp remove atarim --scope user
• Codex: remove the Atarim entry from your MCP server list or configuration file.

Removing the connector there ends that assistant’s access to Atarim.

FAQs

Conclusion

Setup takes a few minutes per developer: copy the Server URL, add it to their assistant, approve the one-time browser prompt, then confirm it actually works with a real question. Once that's done, it fades into the background — your developers just ask their assistant about a site or task, and it already knows, with every gated action still routing through your Approval Queue (Beta) exactly as before.