Productivity · Local MCP server
Pituitary
Catch spec drift before it catches you. Detect overlap, stale docs, and code drift.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.dusk-network/pituitary- Version
- 1.0.0-beta.12
- Status
- Active
- Category
- productivity
- Transport
- stdio (local process)
- Package
- MCP Bundle (.mcpb)
- Published
- 2026-05-08
- Updated
- 2026-05-08
- Publisher
- dusk-network (GitHub)
- Repository
- github.com/dusk-network/pituitary
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| MCP Bundle (.mcpb) | https://github.com/dusk-network/pituitary/releases/download/v1.0.0-beta.12/pituitary-darwin-arm64.mcpbSHA-256 checksum stated | — | stdio |
| MCP Bundle (.mcpb) | https://github.com/dusk-network/pituitary/releases/download/v1.0.0-beta.12/pituitary-linux-amd64.mcpbSHA-256 checksum stated | — | stdio |
How to connect Pituitary
Pituitary runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/dusk-network/pituitary/releases/download/v1.0.0-beta.12/pituitary-darwin-arm64.mcpb. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client.
Pituitary runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/dusk-network/pituitary/releases/download/v1.0.0-beta.12/pituitary-linux-amd64.mcpb. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client.
Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| Pipedrive CRMMCP server for Pipedrive CRM. 155 tools for deals, persons, organizations, activities, and more. | Local · stdio |
| Pipedrive MCPPipedrive CRM as MCP tools: find deals, people and companies, and move deals through a pipeline. | Local · stdio |
| PipesHubPermissioned search and cited answers over Slack, Drive, Gmail, Jira, and 50+ workplace sources. | Remote & Local · HTTP, stdio |
| PithflowRead-only access to your own Pithflow meeting notes, transcripts, dictionary and usage. | Remote · HTTP |
| Piu Copy MCPGrowthHackers copywriting prompts (Meta/Google Ads, email, VSL) as MCP tools — search & generate. | Remote · HTTP |
| PixeroAI marketing agent for paid social: Meta ads campaigns, ad creative generation, lead delivery. | Remote · HTTP |
| Planhat MCPConnect Planhat CRM to Claude and other MCP clients with 60 local tools across 12 resource types. | Local · stdio |
| PlankaMCP server for PLANKA kanban boards. Full CRUD for cards, tasks, comments, and labels. | Local · stdio |