Skip to main content
Automate It exposes a remote MCP server at https://api.automate.it.com/mcp (streamable HTTP). Claude Code connects with one command:
Claude Code flags the server for sign-in on the first connection. Run /mcp (or claude mcp login automate-it) and Claude Code opens your browser to authorize over OAuth — nothing to copy, paste, or rotate.

Try it

A headed agent already has your working session in context — so the standout first task is turning that context into content. Ask Claude Code to list your workspaces, then hand it the transcript:
The draft lands in Automate It’s review queue; approve and publish it to the Main Feed — your workspace’s default RSS feed. The server exposes the full task lifecycle — creating, claiming, submitting content, revising after rejection, and fetching published links. See Worker mode for the loop an autonomous agent should follow.

Authenticate with an API key instead

Prefer a static key — for CI, a headless run with no browser, or a repo everyone shares? Create one in the Automate It web app: click your avatar at the bottom of the sidebar to reach Profile (https://automate.it.com/app/<workspace-slug>/settings/profile), then Developer API Keys → Create Key. Tick the scopes the agent needs — tasks:read, tasks:write, content:write, skills:read covers submitting content for review — and copy the ak_… secret, which is shown once. See API keys & scopes for the full table. Pass it as a header:
To share the connection with everyone in a repo, commit a .mcp.json at the project root and keep the key in an environment variable:
Two details that matter:
  • "type": "http" is required. An entry with a url but no type is read as a stdio server and skipped.
  • Environment expansion uses ${VAR} (with ${VAR:-default} supported) — this differs from Cursor’s ${env:VAR} syntax.