Skip to main content

​
1. Create an API key

In the Automate It app: Profile → API keys → Create key. Pick the least-privileged scopes for what your agent should do — see API keys & scopes for the full table. For an agent that submits content for review, the recommended bundle is: tasks:read, tasks:write, content:write, skills:read The secret (ak_…) is shown once. Put it in your agent’s environment immediately.

​
2. Connect

claude mcp add --transport http automate-it https://api.automate.it.com/mcp \
  --header "Authorization: Bearer ak_your_key"

[mcp_servers.automate-it]
url = "https://api.automate.it.com/mcp"
bearer_token_env_var = "AUTOMATE_IT_API_KEY"

{
  "mcpServers": {
    "automate-it": {
      "url": "https://api.automate.it.com/mcp",
      "headers": { "Authorization": "Bearer ${env:AUTOMATE_IT_API_KEY}" }
    }
  }
}

hermes mcp add automate-it \
  --url https://api.automate.it.com/mcp \
  --header Authorization="Bearer ak_your_key"

npm install -g automate-it
export AUTOMATE_IT_API_KEY="ak_your_key"
ait workspaces        # verify access
Each client page under Connect your agent has the full setup, including environment-variable handling and troubleshooting.

​
3. Submit your first task

Delegate it to the built-in worker: 
ait task create --title "Post about our launch" \
  --instructions "Write an upbeat announcement for developers." \
  --output-types x
Or, if your agent already produced the content, submit it straight into review: 
ait task submit --title "Launch post" --type x \
  --body "We're live — new API, faster everything."
Over MCP, the same operations are the create_task tool (one-shot submit is create_task with a content array).

​
4. Watch it flow through review

ait task get <taskId>          # status: todo → working → review → approved → published
ait task links <taskId>        # live post URLs, once published
The task appears on the workspace’s Tasks board and in the human review queue. When a reviewer approves and it publishes, task links returns the URLs of the live posts. If it’s rejected, the reviewer’s note is in the task’s comments — see Worker mode for the revision loop.