aacworkflow-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@aacworkflow-mcplist my aacworkflow agents"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
aacworkflow-mcp
MCP server that lets Claude and Claude Code drive AACWorkflow: tasks (issues), agents, projects, squads, autopilots and analytics.
Bring your own token. Every user runs their own copy with their own AACWorkflow token — there is no shared server and no central credential store. Your token scopes you to the workspaces (companies) you belong to, and you can drive several from one install.
Quick start (any AACWorkflow user)
Create a token: aacworkflow.com → your workspace → Settings → Tokens → create. Copy the
mul_…value.Connect it to Claude Code (no clone needed — runs straight from GitHub):
claude mcp add aacworkflow --scope user \ -e AACWORKFLOW_TOKEN=mul_your_token \ -- npx -y github:AAChibilyaev/aacworkflow-mcpStart a new Claude Code session and ask: "list my aacworkflow agents", "create a task and assign it to the Маркетолог agent", "show this week's usage".
Multiple companies / workspaces
If your token belongs to one workspace it is used automatically. If you belong to several, either:
set a default: add
-e AACWORKFLOW_WORKSPACE_ID=<id>, orpass
workspace_idper call — runlist_workspacesfirst to see the ids.
Related MCP server: Automatisch MCP Server
Remote / hosted — work from anywhere (Claude Code, claude.ai, ChatGPT)
The same code also runs as a hosted, multi-tenant HTTP endpoint. Host it once; any registered AACWorkflow user connects with their own token in the Authorization header and drives their own workspaces (companies). No shared credentials.
Run the server
# from source
npm install && npm run build && PORT=8787 npm run start:http
# or Docker
docker build -t aacworkflow-mcp . && docker run -p 8787:8787 aacworkflow-mcpPut it behind HTTPS (any reverse proxy / Coolify / Cloudflare) → e.g. https://mcp.example.com/mcp.
Endpoints: POST/GET/DELETE /mcp (MCP Streamable HTTP) and GET /health.
Connect from Claude Code (remote)
claude mcp add aacworkflow --transport http https://mcp.example.com/mcp \
--header "Authorization: Bearer mul_your_token"Connect from ChatGPT (custom connector / developer mode)
Settings → Connectors → Add custom connector → MCP server URL https://mcp.example.com/mcp, auth header Authorization: Bearer mul_your_token.
Marketplace / directory listing
Personal use needs only the hosted URL above. To publish in the directories (Anthropic Connectors directory / OpenAI Apps), the platforms require OAuth 2.1 and a vendor review submitted from your own org account — the bearer-token endpoint here is ready for private/team use today; OAuth can be layered on for public listing.
Claude Desktop
~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"aacworkflow": {
"command": "npx",
"args": ["-y", "github:AAChibilyaev/aacworkflow-mcp"],
"env": { "AACWORKFLOW_TOKEN": "mul_your_token" }
}
}
}Restart Claude Desktop.
Local install (development)
git clone https://github.com/AAChibilyaev/aacworkflow-mcp
cd aacworkflow-mcp && npm install && npm run build
claude mcp add aacworkflow -e AACWORKFLOW_TOKEN=mul_xxx -- node "$PWD/dist/index.js"Tools (34)
Account/workspace:
whoami,list_workspaces,list_members,list_runtimesAgents:
list_agents,get_agent,create_agent,update_agent,list_agent_templates,create_agent_from_template,list_agent_tasksTasks (issues):
list_issues,get_issue,create_issue,update_issue,assign_issue_to_agent,rerun_issue,comment_issue,list_comments,search_issuesProjects / labels:
list_projects,create_project,list_labels,create_labelSquads:
list_squads,get_squad,create_squadAutopilots:
list_autopilots,get_autopilot,trigger_autopilot,list_autopilot_runsAnalytics:
dashboard_usage_daily,dashboard_usage_by_agent,dashboard_agent_runtime
Dispatch work to an agent:
create_issuewithassignee_type:"agent"+assignee_id, orassign_issue_to_agenton an existing issue — the agent's runtime daemon picks it up and runs it.
Config
Env | Default | |
| — | required ( |
|
| self-hosted? point here |
| — | optional default workspace |
Security
Your token is read only from the environment you pass at install time and sent
only to your AACWORKFLOW_SERVER_URL over HTTPS. It is never written to the
repo, logged, or shared. Revoke it anytime in Settings → Tokens.
MIT licensed.
This server cannot be installed
Maintenance
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/AAChibilyaev/aacworkflow-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server