Twist
Let your agent read and post in Twist channels and threads so async team updates stay in sync with your shipping work.
Overview
com.pulsemcp/twist is a MCP server for the Grow phase that manages Twist channels, threads, and messages from your AI coding client.
What is this MCP server?
- MCP tools for Twist channels, threads, and messages
- Requires TWIST_BEARER_TOKEN and TWIST_WORKSPACE_ID environment variables
- Runs via npx twist-mcp-server (stdio, version 0.2.2)
- Experimental PulseMCP subfolder—async team messaging from the agent
- MCP integration for Twist API—not email or Slack
- Server version 0.2.2
- Two required env vars: TWIST_BEARER_TOKEN (secret) and TWIST_WORKSPACE_ID
- npm identifier twist-mcp-server with stdio transport
Community signal: 70 GitHub stars.
What problem does it solve?
Async team decisions live in Twist while your agent works in the repo, forcing copy-paste and missed thread context.
Who is it for?
Solo builders and tiny teams on Twist who want MCP-driven summaries, replies, and channel hygiene during daily operations.
Skip if: Slack-only teams, synchronous standup chat, or orgs that cannot issue Twist API bearer tokens.
What do I get? / Deliverables
Your agent can list, read, and act on Twist conversations alongside code changes using workspace-scoped API credentials.
- Agent-driven reads and writes on Twist channels and threads
- Workspace-scoped messaging operations without manual app switching
- Thread context usable in the same session as code and docs edits
Recommended MCP Servers
Journey fit
Twist fits Grow when a solo builder or micro-team compounds coordination around releases, support, and customer feedback loops. Lifecycle covers ongoing team messaging, thread follow-ups, and operational handoffs—not one-off landing experiments.
How it compares
Twist API MCP bridge, not a generic web scraper or an on-device agent skill.
Common Questions / FAQ
Who is com.pulsemcp/twist for?
Builders and micro-teams using Twist for async messaging who want Claude Code or Cursor to interact with channels and threads via MCP.
When should I use com.pulsemcp/twist?
Use it in Grow lifecycle workflows when you need the agent to draft thread replies, capture decisions, or coordinate releases without leaving the editor.
How do I add com.pulsemcp/twist to my agent?
Set TWIST_BEARER_TOKEN and TWIST_WORKSPACE_ID, then add npx -y twist-mcp-server as a stdio MCP server in your client configuration.