Connect once, and the work flows.
Every request in your editor. Pull tasks, comments and client emails from Atarim into Claude, Codex or any MCP client. No copying tickets, no tab-switching. Close the task from where you fixed it.
Work on the real site. Through the plugin, your agent reaches into live WordPress sites and staging with the same 700+ site tools the Inner Circle uses, and makes changes where they count.
Run the agency, not just the fix. Trigger a review, build a workflow, check the Stack, scan for vulnerabilities, research a keyword, write the client report. Anything with a consequence waits for a human to approve it.
Everything in Atarim, as a tool your agent can call.
The MCP is not a task feed. It is the whole platform, grouped below by what an agency actually does in a week. Reads are cheap. Writes on live sites stop at the Approval Queue.
Tasks, comments and boards
The work queue itself: search across the whole book, create, assign, tag, set status and priority, add subtasks, post internal notes, link to the exact task in the app.
Sites, pages and designs
Every project in the workspace, its pages and screenshots, uploaded design files with pinned feedback, and the shared Email Inbox.
Reviews and reports
Run an AI design review on a page, a whole site or a design file against a review intent, then publish the result as an artifact the client can comment on.
Workflows
Build, validate and edit node-based workflows: triggers, conditions, branches, integrations. Browse the template library. Dry-run before you save.
The Inner Circle and skills
Assign Pixel, Lexi, Index, Navi, Glitch or Claro to a task and they reply. Read the workspace brand brief and the skills library the experts follow, or edit them.
The Stack and security
The chosen plugin per category, detection against the real inventory, install requests that wait for approval, and a CVE-matched vulnerability scan with honest verdicts.
WordPress, through the plugin
Every connected site exposes 700+ tools over its own MCP server: content, media, plugins, themes, design, diagnostics, and a cluster per builder and plugin.
SEO and AI visibility
Keywords, domains, backlinks, SERP, pages and local research, plus who ChatGPT cites and whether the site shows in AI Overviews. Search the operations for free, run the one you need.
Media and files
Generate or edit images across several frontier models, render a screenshot of any URL or HTML, and convert files between formats. Pixel's raw materials, yours too.
The AI bridge to WordPress.
On their own, Claude and Codex cannot touch a WordPress site. The Atarim MCP is the bridge that makes the work real. Through the plugin, every connected site exposes 700+ tools, grouped by cluster: content, media, users, plugins, themes, design, diagnostics, and one cluster per detected plugin. Every builder below has its own skill, so the agent works with the tool's real data model: elements, fields, settings, products.
Security scan, with honest verdicts
Reads every plugin, theme and core version on the site, matches the CVE database, and says update, update-insufficient, no fix, or replace. It never calls an unassessed site secure.
The Stack, detected not guessed
Your agency's chosen plugin for each of 14 categories, checked against what is really installed. A missing one becomes an install request in the Approval Queue, never an install.
Page builders
a dedicated skill per builder, in its own element modelCustom fields and content
Field frameworks and content models, read and written natively.
SEO
Whichever SEO plugin the site runs, the agent works inside it.
Commerce and code
Products, settings and code-level changes on the real site.
The work around the work
The agency layer: tasks, reviews, reports and automations.
Four ways back, under all of it
The hosting and the platforms, linked per project.
Connect the account once, link each client site to its server, store or zone, and your agent addresses it by the project name. Reads run at once. Every write comes back as a pending approval with a plain-sentence intent naming the server and the change. Cancelling accounts and changing plans is not available to the AI at all.
rocket.net
Coming soon200+ tools: PHP versions, cache, backups, staging, domains, SSL, WP-CLI, file management.
Cloudways
Coming soonServers and applications, staging and cloning, SSL, DNS, SSH, monitoring, malware scanning, WAF.
Servebolt
Coming soonBolts and sites, Git deployments, certificates, CDN, databases, cron, full-page cache, PHP.
InstaWP
Coming soonSite creation, PHP settings, backups, maintenance tools, billing.
Cloudflare
Coming soonDNS, cache and firewall. Search the API freely; every execute waits for approval with a named zone.
Shopify
Coming soonAdmin operations against the store behind a project. Live-theme writes always pend for approval.
Duda
Blogs, content library, native eCommerce, stats, forms, collections and bookings, per linked site.
Zapier
The workspace's own Zapier connection reaches thousands of apps with the actions you choose.
One standard, at every level.
Everything that ships through the MCP is held to what a good website does: an open, platform-agnostic specification of the technical details that matter on a website, mapped to the web's own standards. Ten categories, 156 checks.
Foundations
20 checksSEO
14 checksAccessibility
25 checksSecurity
17 checksWell-known URIs
10 checksAgent readiness
20 checksPerformance
25 checksPrivacy
6 checksResilience
6 checksInternationalisation
13 checksHeld to The Website Specification, an open standard mapped to WCAG, WHATWG, W3C and IETF sources. specification.website →
Set up in a few minutes.
Claude
One command for Claude Code, one URL for Claude Desktop and claude.ai. No keys to copy.
Try it: ask Claude to list your open requests and pick one to work on.
View the full setup guide →In Atarim, open Settings → Connected Apps → Atarim MCP and pick Claude.
For Claude Code, run this in your terminal:
claude mcp add --scope user --transport http atarim https://api.atarim.io/v1/mcpOn Claude Desktop or claude.ai, add Atarim as a connector with this server URL instead:
https://api.atarim.io/v1/mcpSign in with your Atarim account when the browser opens. Claude now sees every workspace and site you can access.
Codex
Same setup, inside Codex.
Try it: ask Codex to pull a client request and start on it.
View the full setup guide →Run this in your terminal:
codex mcp add atarim --url https://api.atarim.io/v1/mcpSign in with your Atarim account when the browser opens. Your Atarim work is now in reach.
Other tools
The Atarim MCP works with any tool that supports the Model Context Protocol over HTTP.
View the full setup guide →Add an MCP server in your tool's settings with this server URL. Pick the remote or HTTP option, not a locally-run command:
https://api.atarim.io/v1/mcpSign in with your Atarim account when prompted. If your tool speaks MCP, it can pull your Atarim work.
Action on live sites is reversible and under your control: revisions on every change, backups before risky operations, rollback at every stage. Every write waits in the Approval Queue for a human. More on the Trust page →
The MCP connection acts as you, with your Atarim account's permissions. Agents can act on every workspace and site you have access to, and nothing more.
Bring your whole agency into your editor.
Connect the Atarim MCP and start shipping from Claude, Codex or any MCP client today.
Free to connect. Works with the sites you already manage in Atarim.
Your clients point. You ship.
Anyone can click any part of a website and leave a comment: a client, a stakeholder, a teammate. No login, no training, and a screenshot is captured for them. The MCP surfaces those comments in your agent, so the feedback left on the page becomes the work queue in your editor. The request comes in on the site. The work goes out from your tool.
A client comments on the page. No login, no training.
It lands in Atarim as a task, with a screenshot, tagged and assigned.
You pull it into Claude or Codex and ship.