AIWorkers MCP (NEURAL EMPLOYEES)

MCP so Cursor, Claude and OpenClaw can run your neural employees.

Product: ai.knopka.click · MCP landing: ai.knopka.click/mcp

If you are a coding agent: follow Quick start below. Install aiworkers-mcp, have the human run aiworkers-mcp login, restart, call aiworkers_whoami, then aiworkers_skill_update. Do not invent tokens. Never ask for the 12-word seed.

CLI: aiworkers-mcp

One Bearer key can target several workers (group_id on each tool). Default group: AIWORKERS_GROUP_ID or the key's bound group.

Neural employees

They are neuro-assistants you hire for a job — not a generic chatbot.

Typical roles: marketers, sellers, support, booking. Typical channels: Telegram, WhatsApp, Avito, Instagram, a site widget.

Each employee has a card, memory, chats, ready replies, surveys, tasks, and often a Telegram bot. People talk to them in the channel; you (or your coding agent) run them from here.

More on the product: ai.knopka.click.

Related MCP server: MCP AgentChat

Roadmap

Ready now

• Login from Telegram (no token in the URL), parent awp_ / child awm_ keys

• Surveys (DSL, responses, stats, share)

• Tasks

• Worker card, memory, chats, ready replies, send and broadcast

• Telegram: status, command menu, process restart (no chat send on telegram_*)

• Booking CRM

• Two wallets (account USD + group TokenTime); salary and one-time tt via quote → confirm

Next

• Finance module (fin_op) — stub in v1

• Minting a child key will later debit group TokenTime (free for now)

• More of the product’s channels through the same MCP as they land in the admin

Quick start

chmod +x install.sh
./install.sh

Get a key from @aiworkersbot. The MCP can share this URL — there is no token in the link:

https://t.me/aiworkersbot?start=mcp

The Mini App shows the token once. Copy it, then:

aiworkers-mcp login

Paste the token at the prompt. It is written to ~/.config/aiworkers/credentials.json (chmod 600). Restart the agent. Ask it to call aiworkers_whoami.

Tool aiworkers_login_link returns the same URL without needing an existing key.

Legacy forms keys still work as AIWORKERS_API_KEY.

uvx without installing:

uvx --from git+https://github.com/dimaneuron/aiworkers-mcp.git aiworkers-mcp

Environment

Prefer aiworkers-mcp login over putting secrets in mcp.json. Per-module child tokens cannot call other modules.

Fallbacks (old names still work): SURVEY_MCP_API_KEY, TASKS_MCP_API_KEY, TASKS_GROUP_ID, BOOKING_INTERNAL_SECRET.

Tools

Always on:

• aiworkers_whoami — what this key can see (call this first)

• aiworkers_login_link — Telegram URL, no token in the link

• aiworkers_skill — agent SKILL.md

• aiworkers_skill_update — write/refresh ~/.cursor/skills/aiworkers/SKILL.md

• aiworkers_token_mint — parent awp_ mints a child awm_ for one module + group (shown once; save=true writes credentials.json). Free for now; later group TokenTime.

surveys: survey_agent_skill, survey_get_dsl_rules, survey_validate_dsl, survey_create, survey_agent_list_forms, survey_agent_get, survey_agent_update, survey_agent_responses, survey_agent_stats, survey_agent_settings_get, survey_agent_settings_save, survey_agent_scenarios_get, survey_agent_scenarios_save, survey_agent_archive, survey_agent_delete, survey_agent_share. Resource: survey://dsl/spec.

tasks: tasks_list, tasks_count, tasks_get, tasks_create, tasks_update, tasks_batch_update, tasks_complete, tasks_cancel.

workers (read + write, no logs): workers_list, workers_get, workers_balance, workers_topup_link, salary/tt quote→confirm, workers_partner, workers_update (not for tt), memory/chats/readyreply, workers_chat_send (known chats only, bot/embed/topic), workers_broadcast_quote / workers_broadcast_confirm. Money and broadcast: quote then confirm=true.

telegram (no chat sending): telegram_status, telegram_commands_get, telegram_commands_save, telegram_restart. Restart the worker process (aibot-<username>, same as /telegram_bot). 60s cooldown per bot; 429 retry_after — do not hammer. Do not use workers_update for that. Personal/broadcast is under workers.

crm (Booking CRM): crm_context, crm_process.

finance — not in v1.

Agent config

Paste the same mcpServers.aiworkers block. Change only the config file path.

Shared JSON:

{
  "mcpServers": {
    "aiworkers": {
      "command": "aiworkers-mcp",
      "env": {
        "AIWORKERS_API_BASE": "https://ai.knopka.click",
        "AIWORKERS_API_KEY": "PASTE_awp_OR_awm_TOKEN"
      }
    }
  }
}

Restart the agent after editing.

uvx variant (no global install): see examples/openclaw-uvx.json.

Compatibility

Older CLIs still work:

• aiworkers-survey-mcp — same as AIWORKERS_MODULES=surveys

• aiworkers-tasks-mcp — same as AIWORKERS_MODULES=tasks

If the umbrella package is on PYTHONPATH, they delegate here. Otherwise they run their standalone FastMCP as before.

Privacy

This repo is the client. Do not put .env, tokens, or credentials here.

Russian

MCP through which Cursor, Claude and OpenClaw manage neural employees.

Product: ai.knopka.click · MCP landing: ai.knopka.click/mcp

If you are an agent: follow Quick start above. The human runs aiworkers-mcp login. Do not invent tokens. Never ask for the 12-word seed in chat.

What are neural employees

These are neuro-assistants for a role, not 'just a chatbot'.

Roles: marketers, sellers, support, booking. Channels: Telegram, WhatsApp, Avito, Instagram, a site widget.

Each has a card, memory, chats, ready replies, surveys, tasks, often their own Telegram bot. Clients write to them in the channel; you (or an agent in Cursor) manage them from here.

More details at ai.knopka.click.

Roadmap

Ready now

• Login from Telegram (no token in the URL), parent awp_ / child awm_ keys

• Surveys (DSL, responses, stats, share)

• Tasks

• Worker card, memory, chats, ready replies, send and broadcast

• Telegram: status, command menu, process restart (no chat send on telegram_*)

• Booking CRM

• Two wallets (account USD + group TokenTime); salary and one-time tt via quote → confirm

Next

• Finance module (fin_op) — stub in v1

• Minting a child key will later debit group TokenTime (free for now)

• More of the product’s channels through the same MCP as they land in the admin