@isteamhq/mcp

MCP server for is.team — connect AI agents to your project boards.

Setup

Claude Code / Claude Desktop

Add to your MCP config (.mcp.json or Claude Desktop settings):

{
  "mcpServers": {
    "is-team": {
      "command": "npx",
      "args": ["-y", "@isteamhq/mcp"],
      "env": {
        "IST_API_TOKEN": "ist_your_token_here"
      }
    }
  }
}

Get your API token

1. Go to is.team and open Account Settings

2. Navigate to the API tab

3. Generate a new token

4. Copy the ist_xxx token into the config above

Tools

v3.0 ships ~113 tools total — task & card lifecycle (33), canvas (12), workspace primitives (9), team ops (6), sprints (5), niche (12), real-time/chat (5), plus 34 integration tools (GitHub, Drive, Slack, Figma, Calendar). The full surface is grouped below.

Card & task essentials

Boards & cards (canvas columns)

Notes / canvas

Workspace / team

Sprints (agile flow)

Forms (read-only)

Notifications

Real-time + chat

Integrations (34 tools)

GitHub (12), Google Drive (8), Slack (7), Figma (3), Google Calendar (5). See list_integrations.

Real-time notifications

Use subscribe_card to watch a card for new tasks. When a task is created or moved into the card, you'll receive an automatic notification — no polling needed.

"Subscribe to card col-xxx and work on any new tasks that appear."

The AI agent will receive instant notifications and can start working immediately.

Background daemon mode (v2.0+)

Run Claude as a persistent background daemon that auto-executes any task assigned to a chosen card. The daemon survives terminal closure, restarts itself on crashes, and relays Claude's output back to the card chat so you can monitor progress entirely from is.team.

Agent name (v2.1+)

Every setup run now asks for a 6-character agent name (letters + digits). The name appears on the agent's badge in the is.team dashboard, so when you run multiple agents — one per project, one per machine, one foreground and one in background — you can tell them apart at a glance. Use different names for each terminal/project. Examples: HOME01, MACM01, DEV001, LAPTP1, PROD01.

The name is stored in the project's .mcp.json under the IST_AGENT_NAME env var (and in ~/.isteam/daemon.json when running in daemon mode). If you ever need to change it, re-run setup or edit the file by hand.

Setup

npx @isteam/mcp@latest setup --token ist_xxx

When asked Run in background as a daemon?, answer y. The wizard will:

1. List your cards — pick the one the daemon should watch

2. Ask for a permission mode (acceptEdits recommended)

3. Ask for a working directory (defaults to current)

4. Install a launchd agent (macOS) or systemd user unit (Linux)

5. Start the daemon

Now assign a task to the chosen card and Claude will start working automatically — no terminal needed.

Managing the daemon

npx @isteam/mcp daemon status        # show current state + config summary
npx @isteam/mcp daemon logs --follow # tail the live log
npx @isteam/mcp daemon start|stop|restart
npx @isteam/mcp daemon uninstall     # remove the service

How it works

• macOS: ~/Library/LaunchAgents/team.is.mcp-daemon.plist

• Linux: ~/.config/systemd/user/isteam-mcp-daemon.service

• Config: ~/.isteam/daemon.json (0600 — contains your API token)

• Logs: ~/.isteam/daemon.log + ~/.isteam/daemon-error.log

Each task spawns a one-shot claude --print subprocess with the repo's MCP config loaded. Claude reads the task, executes it, posts a summary back to the card chat, and moves the task to the next pipeline card.

Platform support

Enable LLM access on a card

Before an AI agent can interact with a card:

1. Click the AI Integration button on the card header

2. Enable LLM Access

3. Enable Flow Actions (for create/update/move/complete)

4. Enable Comments (for adding comments)

Environment variables

License

MIT