How do I connect Twist Ai MCP Server to Claude?

Run `claude mcp add twist-ai -- npx -y @doist/twist-ai` in Claude Code, or add the same command and arguments under mcpServers in Cursor's mcp.json or Claude Desktop's claude_desktop_config.json, then restart the client. The blocks above are ready to paste.

Is Twist Ai MCP Server free?

The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.

What can Twist Ai MCP Server do?

Twist Ai MCP Server documents 10 tools to the agent, including buildLink, createThread, fetchInbox. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.

Twist Ai

Unclaimed

by Doist

The tools required for a Twist MCP server

Set up this server

Compare servers My Stack

01 / Choose your client

02 / Before you connect

Authentication is not specified. Check the project instructions before connecting.

Install the runtime required by the project and make it available to your client.

Project instructionsEnvironment variable names (optional)

Use names from the project instructions, separated by commas. Enter names only, never secret values.

03 / Add the configuration

Source: generated from public install instructions

claude mcp add --transport stdio 'twist-ai' -- 'npx' '-y' '@doist/twist-ai'

Run in your terminal after replacing any placeholders.

04 / Check it in your client

Open your client’s MCP settings and confirm the server connects and lists its tools. A copied configuration does not confirm a working connection.

Is this your MCP server?

This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.

Claim this server

Security profile

Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works

10 of 10 tools

Documented tools (10)

From project documentation. A server handshake does not verify each tool’s description or behavior.

buildLink

Build URLs to Twist resources

createThread

Create a new thread in a channel. Accepts an optional displayInInbox boolean (default false). When true, the thread is unarchived after creation so it appears in the author's Inbox. See also TWISTCREATETHREADDISPLAYININBOX.

fetchInbox

Fetch threads and conversations from the inbox

loadConversation

Load a specific conversation with its messages

loadThread

Load a specific thread with its comments

markDone

Mark threads or conversations as done (read and/or archived)

react

Add reactions to threads, comments, conversations, or messages

reply

Reply to threads or conversations

searchContent

Search across a workspace for threads, comments, and messages

userInfo

Get information about the current user and their workspaces

Tool change history

Compared across complete checks of the same configuration. Tools were listed, not invoked. Input-schema changes are not measured here.

No complete tool checks yet.

FAQ

Questions about Twist Ai MCP Server

How do I connect Twist Ai MCP Server to Claude?: Run `claude mcp add twist-ai -- npx -y @doist/twist-ai` in Claude Code, or add the same command and arguments under mcpServers in Cursor's mcp.json or Claude Desktop's claude_desktop_config.json, then restart the client. The blocks above are ready to paste.
Is Twist Ai MCP Server free?: The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
What can Twist Ai MCP Server do?: Twist Ai MCP Server documents 10 tools to the agent, including buildLink, createThread, fetchInbox. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.