Connect once, and the work flows.
Every request in your editor
Pull tasks and client requests from Atarim into Claude or Codex. No copying tickets, no tab-switching.
Work on the real site
Reach into live WordPress sites and staging through the plugin, and make changes where they count.
Build and ship in one place
Build with Claude Design, then ship the change without leaving your tool.
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 it reaches into the live site, and every builder and plugin below has its own dedicated skill, so the agent works with the tool's real data model: elements, fields, settings, products. No other MCP reaches this deep into WordPress.
Any site: pull the work
Tasks, comments and requests flow into your editor from every site in your workspace, whatever it runs on.
WordPress: reach the site
Through the plugin, the MCP makes real changes on live sites and staging: content, settings, products, plugin-level work.
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.
And a safety net under all of it
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
Connect Atarim to Claude and start pulling requests in minutes.
Try it: ask Claude to list your open requests and pick one to work on.
Read the Claude guide →In Atarim, open Settings → Workspace → MCP and copy your workspace connection URL and key.
Add Atarim as an MCP server in Claude:
--header "Authorization: Bearer <your-key>"
Reconnect Claude. It now sees your Atarim sites, tasks, and comments.
Codex
Same setup, inside Codex.
Try it: ask Codex to pull a client request and start on it.
Read the Codex guide →In Atarim, copy your workspace connection URL and key from Settings → Workspace → MCP.
Add Atarim as an MCP server in your Codex config:
url = "https://mcp.atarim.io/mcp"
bearer_token_env_var = "ATARIM_MCP_KEY"
Reconnect Codex. Your Atarim work is now in reach.
Other tools
The Atarim MCP works with any tool that supports the Model Context Protocol.
Read the setup guide →Point your MCP client at the same Atarim connection URL and key, then add it the way that tool expects. 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. Read-only queries through the MCP are free. More on the Trust page →
Exact paths, commands and guide links shown here are placeholders, to confirm with product before publish.
Bring your client work into your editor.
Connect the Atarim MCP and start shipping from Claude or Codex 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 back into Claude or Codex, 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.