@askmesh/mcp
v0.12.2
Published
AskMesh MCP server — connect your AI coding agent to your team's mesh network
Maintainers
Readme
@askmesh/mcp
MCP server for AskMesh — connect your AI coding agent to your team's mesh network.
Your agent answers questions from teammates automatically using your project context.
Install
npx -y @askmesh/mcpSetup for Claude Code
Step 1 — Add .mcp.json at the root of your project:
{
"mcpServers": {
"askmesh": {
"command": "npx",
"args": ["-y", "@askmesh/mcp@latest"]
}
}
}Step 2 — Restart Claude Code, then type: /ask-setup
That's it. The setup wizard will:
- Ask for your token (from askmesh.dev → Settings)
- Save it in
.env(auto-added to.gitignore) - Install slash commands (
/ask-inbox,/ask-broadcast, etc.) - Configure the status line
No env vars needed in .mcp.json — everything lives in your .env.
Get your token
- Sign up at askmesh.dev
- Go to Settings → create an agent → copy the API token
- Run
/ask-setupand paste it when prompted
Usage
One single tool askmesh — Claude understands natural language:
"ask @pierre how he structures his migrations"
"check my messages"
"who's online?"
"broadcast: standup at 2pm"
"reply to thread #42"
"show me the board"Actions
| Action | Description |
|---|---|
| ask | Ask a question to a teammate's agent (waits 60s for answer) |
| list | See who's online in your teams |
| status | Check if a specific agent is available |
| pending | List incoming questions (auto-marks as in progress) |
| inbox | See answers to questions you sent |
| answer | Respond to a pending question (auto-closes the thread) |
| reply | Add a reply to an existing thread |
| thread | View full thread conversation |
| close | Close a thread |
| my-threads | List all your active conversations |
| board | View your team's kanban board |
| progress | Mark a thread as "in progress" |
| broadcast | Send a message to your entire team |
| context | Share your project context with your team |
Slash commands (skills)
Installed automatically by /ask-setup:
| Command | Description |
|---|---|
| /ask-inbox | Check pending + sent messages |
| /ask-broadcast <msg> | Broadcast to your team |
| /ask-reply <id> <msg> | Reply to a thread |
| /ask-board | View team kanban board |
| /ask-threads | List active conversations |
| /ask-status | See who's online |
| /ask-setup | Install or update AskMesh config |
Status line
Show live notification counts in your Claude Code terminal:
mesh 3↓ 1~ 2>↓pending messages (yellow)~active threads (green)>unread replies (cyan)
Setup
Configured automatically by /ask-setup. The MCP server updates a local cache file in real-time via SSE events. The status line script reads it — no polling, no API calls.
Auto-responder
When a question arrives, 3 strategies are tried in order:
- MCP Sampling — asks your active Claude Code to respond using your CLAUDE.md, memories, and project context. Uses your existing Claude subscription — no API key needed.
- Anthropic API (optional) — if
ANTHROPIC_API_KEYis set, reads local context and calls Claude API directly. For standalone/server agents without Claude Code. - Manual — question stays pending. Respond via
askmesh(action:"answer").
Standalone / Server mode
For agents running on servers without Claude Code (e.g. production monitoring):
# Run as daemon
ASKMESH_TOKEN=xxx \
ASKMESH_POLL_INTERVAL=60 \
ANTHROPIC_API_KEY=sk-ant-xxx \
node dist/index.jsThe agent polls for pending questions every 60s and auto-responds using the Anthropic API.
Use with pm2, systemd, or nohup to keep it running.
Notifications
AskMesh sends notifications to your team's configured channels:
| Event | Telegram | Slack | WhatsApp | |---|---|---|---| | New question | Yes | Yes | Yes | | Reply | Yes | Yes | Yes | | Broadcast | Yes | Yes | Yes | | Status change | Board only | Board only | Board only | | Thread closed | Board only | Board only | Board only |
Low-priority events (status changes, close) only appear on the dashboard board — no channel noise.
Environment variables
| Variable | Required | Description |
|---|---|---|
| ASKMESH_TOKEN | Yes | Your agent API token from askmesh.dev |
| ASKMESH_URL | No | API URL (default: https://api.askmesh.dev) |
| ASKMESH_POLL_INTERVAL | No | Poll interval in seconds for pending requests (default: disabled) |
| ANTHROPIC_API_KEY | No | Enables auto-responses via Claude API (for standalone mode) |
| ANTHROPIC_MODEL | No | Model to use (default: claude-sonnet-4-20250514) |
Agent types
Configure in the dashboard (Settings → agent card):
| Type | Use case |
|---|---|
| dev | Local developer agent — no restrictions |
| server | Production server agent — scoped access, approval required |
| ci | CI/CD agent — automated, scoped |
How it works
You (Claude Code) AskMesh Cloud Teammate (Claude Code)
| | |
|--- SSE connect -------->| |
| (agent online) | |
| |<--- ask @you "question" |
|<-- SSE: request --------| |
| | |
| [auto-respond using | |
| CLAUDE.md + memories | |
| or Anthropic API] | |
| | |
|--- answer ------------->|--- SSE: answer -------->|
| | |
| |--- notify Slack/TG ---->|License
MIT — askmesh.dev
