Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Threads MCP Servershow my active threads and suggest what I should work on next"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Threads MCP Server
MCP server exposing Threads CLI data and operations via the Model Context Protocol.
Installation
cd threads-mcp
npm install
npm run buildUsage
With Claude Desktop
Add to your Claude Desktop configuration (claude_desktop_config.json):
{
"mcpServers": {
"threads": {
"command": "node",
"args": ["C:/Users/joshu/Desktop/threads-mcp/dist/server.js"]
}
}
}Development
npm run dev # Run with tsx (no build needed)
npm run build # Compile TypeScript
npm run start # Run compiled version
npm run typecheck # Type check onlyTesting with MCP Inspector
npx @modelcontextprotocol/inspector node dist/server.jsResources
URI | Description |
| All threads |
| Active threads only |
| Hot/warm temperature threads |
| Single thread by ID |
| All containers |
| Single container by ID |
| All groups |
| Single group by ID |
| Entities in a group |
| Full hierarchy tree |
| Suggested next action |
| Progress log for a thread |
Tools
Thread Management
Tool | Description |
| Create a new thread |
| Update thread properties |
| Archive a thread (with optional cascade) |
| Permanently delete a thread |
| Get thread by ID or name |
Progress Tracking
Tool | Description |
| Add progress note to a thread |
| Get progress history |
| Edit a progress entry |
| Delete a progress entry |
Organization
Tool | Description |
| Create organizational container |
| Update container properties |
| Delete a container |
| Create a group |
| Update group properties |
| Delete a group |
| Set entity parent |
| Move entity to group |
| Get immediate children |
| Get path to root |
| Get full subtree |
Query & Search
Tool | Description |
| List threads with filters |
| List containers with filters |
| List all groups |
| Full-text search |
| Suggest next thread to work on |
| Get complete hierarchy |
| Get any entity by ID/name |
| Get container by ID/name |
| Get group by ID/name |
Architecture
threads-mcp/
├── src/
│ ├── server.ts # Entry point, stdio transport
│ ├── lib/
│ │ ├── threads-client.ts # Wrapper for Threads storage
│ │ └── types.ts # MCP-specific types
│ ├── resources/
│ │ ├── index.ts # Resource registration
│ │ ├── threads.ts # Thread resources
│ │ ├── containers.ts # Container resources
│ │ └── groups.ts # Group resources
│ └── tools/
│ ├── index.ts # Tool registration
│ ├── thread-ops.ts # Thread operations
│ ├── progress-ops.ts # Progress operations
│ ├── org-ops.ts # Organization operations
│ └── query-ops.ts # Query operationsData Storage
Data is stored in ~/.threads/threads.json (same as Threads CLI). This server directly reads and writes to that file, maintaining full compatibility with CLI operations.
Example Workflows
Create and track a project
1. Use create_container to create "My Project"
2. Use create_thread to create threads under that container
3. Use add_progress to log updates as you work
4. Use get_next_action to see what to work on nextReview active work
1. Read threads://threads/active resource
2. Or use list_threads with status: "active"
3. Use list_progress to see recent updatesOrganize existing threads
1. Use create_group to create organizational groups
2. Use move_to_group to assign threads
3. Use set_parent to build hierarchyLicense
MIT
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.