aacworkflow-mcp
Enables Claude and Claude Code to manage AACWorkflow tasks, agents, projects, squads, autopilots, and analytics through natural language.
README
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-mcp -
Start 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>, or - pass
workspace_idper call — runlist_workspacesfirst to see the ids.
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-mcp
Put 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_runtimes - Agents:
list_agents,get_agent,create_agent,update_agent,list_agent_templates,create_agent_from_template,list_agent_tasks - Tasks (issues):
list_issues,get_issue,create_issue,update_issue,assign_issue_to_agent,rerun_issue,comment_issue,list_comments,search_issues - Projects / labels:
list_projects,create_project,list_labels,create_label - Squads:
list_squads,get_squad,create_squad - Autopilots:
list_autopilots,get_autopilot,trigger_autopilot,list_autopilot_runs - Analytics:
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 | |
|---|---|---|
AACWORKFLOW_TOKEN |
— | required (mul_…) |
AACWORKFLOW_SERVER_URL |
https://aacworkflow.com |
self-hosted? point here |
AACWORKFLOW_WORKSPACE_ID |
— | 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.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.