Integrations and add-ons

Everything that connects AI Worker to your tools: your own Codex or Claude, your browser, your website and your CRM. Some are ready now, the rest are being prepared.

Codex · Claudeskill and MCP
Chrome · Edge · Firefoxbrowser extension
WordPresschat plugin
Available

Skill for Codex and Claude

Your Codex or Claude, on your own subscription, sets up AI Worker from your description: a task for an AI employee, a web chat with its knowledge, a persona, a contact collection or a dialog scenario. It writes a settings file you import, or works through the account directly when MCP is connected.

All plans
Download the skill (zip)GitHub
Available

MCP server of your account

Connect Codex, Claude Code or any MCP client to your account with the API key. The AI sees your chats and tasks, proposes changes from the same list as the setup wizard and applies them only after you agree.

Every plan
How to connect
Available

Claude Code plugin

The skill and the MCP connection in one install: add our GitHub repository needtome/aiworker-skills to Claude Code as a plugin source (Claude Code calls it a marketplace) and install the plugin — two commands below. Put your API key into the environment variable AIWORKER_API_KEY.

Every plan
How to installGitHub
Available

Events straight to your Claude or Codex

MCP cannot wake an idle Claude Code or Codex — AI agents can. A CRM, a form or a task sends an event to your route, and a small listener on your computer wakes your open Claude Code session or runs Claude Code or Codex in the background, with your instruction for the event.

Business plan and above
How it works
Coming soon

Browser extension

Runs your tasks in your own browser — Chrome, Edge or Firefox — with your logins and your IP, in a separate tab. You connect it once with a code from the panel; the browser then takes tasks by itself.

Coming soon

WordPress plugin for the web chat

Adds the AI Worker web chat to a WordPress site without editing the theme and keeps the chat's knowledge in sync with your posts and pages.

Coming soon

n8n and Make: Web Tasks & Conversations

Create browser tasks from plain-language instructions (scraping, parsing, Telegram, freelance projects, and leads), run them on the AI Worker server or in your browser through the extension, and send messages to connected conversations. Start workflows on task events or poll for new results. Connect with your AI Worker sign-in (OAuth) or an API key. The connector API is open; the n8n community node and Make app are being prepared for publication.

Every AI-employee plan, from Mini
Connector API
Available

REST API and webhooks

Contacts, campaigns, dialogs and messages through the API; signed webhooks to your CRM on new messages, handoffs, bookings and refusals. Tasks can also start from a webhook of a CRM, a shop or a form.

Business plan and above
API reference

What MCP can do

  • See the account: web chats, personas, AI employees, tasks with their sites, criteria, schedule and status.
  • Explain what a task did with a link: whether it found the element, when, the AI score and reason, whether it was mailed; the last runs of a task.
  • Change things like the setup wizard: create a task, a web chat or a contact collection; change a task's criteria, sites, schedule, where results go; run, pause or switch on a task; start or pause a contact collection; edit a chat's greeting, quick questions, FAQ, look and knowledge sources; edit persona and employee instructions; store an API key of a task.
  • Export settings to a file and import a file (a check first, then creation).
  • Every change is proposed first and applied only on a separate command after you agree.

What is inside the skill

  • Instructions for working with tasks the right way: create, edit, read the run logs.
  • The settings file format with every field, and its JSON Schema.
  • Instructions and the list of every available API method.
  • The list of wizard actions for MCP and ready example files.

Connect Codex or Claude

Step 1. Get the API key

  1. Open Settings → Integrations in the panel and press «Issue key».
  2. The key is shown once. Press «Download as file» — the file aiworker-key.txt appears in your Downloads folder.

Step 2. Ask your AI to install everything

Copy this and send it to your Codex or Claude Code:

Install the AI Worker MCP server and the aiworker skill from the repository https://github.com/needtome/aiworker-skills. The API key is in the file ~/Downloads/aiworker-key.txt: move it into the environment variable AIWORKER_API_KEY without showing the key on screen, then delete that file.

The AI saves the key and connects MCP and the skill. Restart Codex or Claude Code when it asks.

If you want to store the key yourself

The key goes into the environment variable AIWORKER_API_KEY. Replace your-key with the key from the panel and run one command.

Mac — open the Terminal app (Spotlight: ⌘ + Space, «Terminal»):

echo 'export AIWORKER_API_KEY="your-key"' >> ~/.zshrc

Windows — open PowerShell (Start → «PowerShell»):

setx AIWORKER_API_KEY "your-key"

Linux — in a terminal:

echo 'export AIWORKER_API_KEY="your-key"' >> ~/.bashrc

Close and reopen the terminal, Codex or Claude Code. Then ask your AI:

Install the AI Worker MCP server and the aiworker skill from the repository https://github.com/needtome/aiworker-skills. The API key is in the environment variable AIWORKER_API_KEY.

Do not paste the key into the chat with the AI and do not keep it in notes or shared documents: others may read it there.

By hand

Claude Code — the plugin (skill + MCP)

/plugin marketplace add needtome/aiworker-skills
/plugin install aiworker@aiworker-skills
/reload-plugins

Claude Code — MCP only

claude mcp add --transport http aiworker https://kra.name/app/api/mcp \
  --header "Authorization: Bearer $AIWORKER_API_KEY"

Codex — in ~/.codex/config.toml

[mcp_servers.aiworker]
url = "https://kra.name/app/api/mcp"
bearer_token_env_var = "AIWORKER_API_KEY"

Claude in the browser or the app

  1. Customize → Connectors → add a custom connector.
  2. Address: https://kra.name/app/api/mcp.
  3. Request header: Authorization: Bearer <API key>.
  4. Use either the connector or the Claude Code plugin, not both on one computer.

Install the skill only

The easy way: ask your AI

Write to your Codex or Claude Code:

Install the aiworker skill from the repository https://github.com/needtome/aiworker-skills — the folder plugins/aiworker/skills/aiworker.

By hand

  1. Download the archive aiworker-skill.zip.
  2. Unzip it — you get the folder aiworker.
  3. Put the folder:
    • Claude Code — into ~/.claude/skills/
    • Codex — into ~/.agents/skills/
  4. Claude in the browser or the app: Customize → Skills → «+» → upload the zip as it is.

The same in the terminal:

curl -L https://kra.name/skills/aiworker-skill.zip -o /tmp/aiworker-skill.zip
unzip -o /tmp/aiworker-skill.zip -d ~/.claude/skills   # Claude Code
unzip -o /tmp/aiworker-skill.zip -d ~/.agents/skills   # Codex

Connect to ChatGPT

Your AI Worker account connects to ChatGPT as a plugin (MCP server): ChatGPT sees your chats, personas, tasks and what they found with the AI scores, and can propose changes — they apply only after you agree in the conversation. No key to copy: you sign in with your AI Worker account.

This connects your account straight to your ChatGPT: it works with it right in the browser or the ChatGPT app — no Codex, no Claude Code, nothing to install on your computer.

  1. Open chatgpt.com/plugins → «Add» → custom MCP server.
  2. Name — AI Worker, server URL — https://kra.name/app/api/mcp, authentication — OAuth. Leave «Advanced OAuth settings» as they are: ChatGPT discovers them itself.
  3. Tick «I understand and want to continue» and create the plugin.
  4. The AI Worker page opens: sign in to the panel (password or Google) and press «Allow access».
  5. Done: pick the AI Worker plugin in a chat and ask, for example: «show what the task found this week and with which scores».

Works on any paid plan. Disconnect any time in the panel: «Settings → Integrations». claude.ai connects the same way: «Settings → Connectors → Add custom connector», the same address.

Events straight to your Claude or Codex

  • Create a route in the panel: AI employee tasks → AI agents — which agent (Claude Code or Codex), how to wake it and what to do with each event.
  • Events come from the route's own address (your CRM, shop or form posts JSON to it), from the task step «Hand to AI agent», or from the API.
  • Answers to your requests: when your AI filed a request for something AI Worker cannot do yet, it gets the developers' answer by itself with its next AI Worker call and tells you at once — nothing to set up.
  • Open session: tell your Claude Code «listen to AI Worker events of route orders». It starts the listener with its Monitor tool; every event wakes that session, and the agent marks the event done itself.
  • In the background: tell Claude Code or Codex «install the AI Worker background listener for route orders» — it starts with the computer (launchd, systemd or Task Scheduler) and runs the agent without a window for each event. Don't resume in the background a session you have open in an app at the same time.
  • Only a content-free «there is an event» signal goes through our server; the listener fetches the event with your API key. Events are kept for 30 days.

Copy and send this to your AI (replace orders with your route name):

Codex — a background service that wakes Codex on every event:

Connect AI Worker events to Codex for the route orders: install the aiworker-listen listener from the aiworker skill in run mode as a background service that starts when I log in. The API key is in the environment variable AIWORKER_API_KEY. Check that the service is running and show me how to stop it.

Claude Code — in this open session:

Listen to AI Worker events of the route orders and handle each one by the route's instruction.

What to ask

  • «Create a task: every 30 minutes check new Laravel jobs on freelancehunt and upwork, send me the ones from $300»
  • «Make a web chat for a dental clinic with the consultant Anna and these questions and answers…»
  • «Why did the task “Jobs” not send me this project?» — when MCP is connected

Every change goes in two steps: the AI first shows what it will change and applies it only after your «yes».