Twist MCP server
MCP server for Twist team messaging — manage channels, threads, and messages.
80 stars49 downloads/wk
Reviews
Write oneNobody has reviewed Twist yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Twist tools (6, 2 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
add_message_to_threadwrite actionPost a new message to an existing Twist thread. This tool allows you to contribute to ongoing conversations by adding your response, update, or comment to a thread. Messages are added chronologically and all thread participants are notified based on their notification preferences. Example response: Successfully added message to thread: - Message ID: 345678 - Thread ID: 789012 - Posted: 6/27/2025,
close_threadClose an existing Twist thread with an optional closing message. This tool marks a thread as closed, preventing further replies while keeping the thread accessible for reference. A closing message is automatically added to indicate the thread has been closed. Example response: Successfully closed thread: - Thread ID: 789012 - Closing message: "Thread closed - Issue resolved" - Closed at: 6/27/2025
create_threadwrite actionCreate a new thread (conversation) in a Twist channel. Threads are the core organizational unit in Twist, allowing teams to have focused, asynchronous discussions on specific topics. Each thread starts with a title and an initial message that sets the context. Example response: Successfully created thread: - Title: "Q4 Planning Discussion" - ID: 789017 - Channel ID: 123457 - Created: 6/27/2025, 3:
get_channelRetrieve detailed information about a specific Twist channel along with its threads. This tool provides comprehensive metadata about a channel including its name, description, creation date, status, and optionally lists threads within the channel. By default, it includes open threads but this can be disabled or customized. Example response: Channel Details: - Name: #engineering - ID: 123457 - Desc
get_channelsList all channels in your Twist workspace. Channels are the primary way to organize conversations in Twist, similar to channels in Slack or rooms in other chat applications. This tool retrieves all channels you have access to in the configured workspace. Example response: Found 5 active channels: - #general (ID: 123456) - General team discussions - #engineering (ID: 123457) - Engineering team upda
get_threadRetrieve a complete thread conversation including all messages. This tool fetches the full context of a discussion, showing the thread metadata and every message posted in chronological order. Essential for understanding the complete conversation history. Example response: Thread: "Bug Report: Login Issues" ID: 789013 Channel ID: 123457 Created: 6/27/2025, 9:00:00 AM Status: Active Messages (3 tot
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan45 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 28 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
How Twist compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 85/100
- higher than 70% of 48,243 servers
- Tools
- 6
- the typical server has 7
- Tools that change things
- 33%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 80
- more than 95% of 28,706 servers
- Downloads a week
- 49
- more than 39% of 12,306 servers with a package
What its tools let an agent do: 3 read · 2 create · 1 change
Install Twist in Claude Code, Cursor or VS Code
Runs npx -y twist-mcp-server on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add twist -- npx -y twist-mcp-server
What the publisher says
From the Twist repository's README, as published. We do not edit it. Read it on GitHub
PulseMCP's MCP Servers
We build reliable servers thoughtfully designed for MCP Client-powered workflows.
Design principles
You can have confidence that any Pulse-branded MCP server was built with these north stars in mind:
- Purpose-built. LLM-powered MCP clients offer uniquely new user interaction patterns that necessitate a different layer of abstraction than the REST API's from a pre-AI era. We thoughtfully scope drawing lines like building a new server, versus incorporating a new feature in another server. Or deciding where one slew of REST API endpoints might be better packaged as a single Tool call. And more.
- Easy set up. Many MCP servers die before ever getting a chance to be used. We offer guides and a frustration-free experience to get going with our MCP servers inside your favorite MCP clients.
- Time savings. By minimizing the number of tool chain steps or conversational turns you need to accomplish a task, our MCP servers will save you (and your agents) time waiting for a task to be completed.
- Inference cost savings. By minimizing the number of tokens you need to consume to a accomplish a task, our MCP servers will save you on your LLM inference bills.
- Reliability. You should have confidence that you can deploy our servers in a production application serving mass market consumers or business clients.
- Future-proof. We sit on the bleeding edge of the MCP specification, working to push the ecosystem forward. As such, you can be sure that if you commit to baking our server into your workflow, it will self-improve over time to take advantage of the latest and greatest MCP features.
Servers Available
Productionized Servers
These are PulseMCP-branded servers that we intend to maintain indefinitely as our own offerings.
The MCP Registry column controls whether the server is published to the official MCP Registry (com.pulsemcp/) by the publish-mcp-registry.yml workflow.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Twist: common questions
- Is Twist MCP server safe?
- Yes, by our scan: it is graded A (85/100). Read the Twist safety report
- How do I install Twist?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Twist need an API key?
- Yes. The registry entry asks for
TWIST_BEARER_TOKEN. - Is Twist maintained?
- The last commit was 66 days ago (2026-08-30). The latest release is v0.2.3.
- How does Twist compare with other MCP servers?
- safety score 85/100 (higher than 70% of 48,243 servers); tools 6 (the typical server has 7); tools that change things 33% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.