Standup from your activity MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add standup-mcp -- npx -y standup-mcp

{
  "mcpServers": {
    "standup-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "standup-mcp"
      ]
    }
  }
}

[mcp_servers.standup-mcp]
command = "npx"
args = ["-y", "standup-mcp"]

{
  "mcpServers": {
    "standup-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "standup-mcp"
      ]
    }
  }
}

{
  "servers": {
    "standup-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "standup-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: GITHUB_TOKEN (GitHub read-only personal access token. Enables commits, PRs, and reviews. Leave all sources unset to use the built-in demo data), JIRA_BASE_URL (Your Jira Cloud site, e.g. https://your-company.atlassian.net), JIRA_EMAIL (Atlassian account email the API token belongs to), JIRA_API_TOKEN (Jira API token from id.atlassian.com. Read-only use), LINEAR_API_KEY (Linear personal API key (read-only). Enables issue state changes and comments), SLACK_TOKEN (Slack token with read scopes. Enables scanning your own messages for blocker language), SLACK_CHANNELS (Optional comma-separated channel ids to scan when message search is unavailable), STANDUP_NAME (Optional display name for the standup's owner), STANDUP_DEMO_MODE (Set to true to force the demo dataset even when credentials are present).