Standup from your activity MCP Server

What this does

Standup from your activity exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

GITHUB_TOKEN
JIRA_BASE_URL
JIRA_EMAIL
JIRA_API_TOKEN
LINEAR_API_KEY
SLACK_TOKEN
SLACK_CHANNELS
STANDUP_NAME
STANDUP_DEMO_MODE

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install Standup from your activity?

Run the Claude Code command in the install section to add Standup from your activity to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with Standup from your activity?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to Standup from your activity as well.

Does Standup from your activity need an API key?

Yes. Before it can run, set these environment variables: GITHUB_TOKEN, JIRA_BASE_URL, JIRA_EMAIL, JIRA_API_TOKEN, LINEAR_API_KEY, SLACK_TOKEN, SLACK_CHANNELS, STANDUP_NAME, STANDUP_DEMO_MODE. They go in the env block of your MCP config.