Self-hosted Shortcut MCP alternatives
Shortcut's server can run locally over stdio, so the process and your token stay on a machine you control even as it talks to Shortcut's backend. Each pick here also installs locally rather than only as a managed endpoint, which suits teams that want the connector running on their own side.
One honest caveat. Self-hosting the server controls where the process and credentials live, but for the hosted-product trackers the planning data still travels to each vendor's API. Obsidian is the standout that keeps content on your own disk, since it reads local Markdown files.
The 8 best self-hosted alternatives
monday.com's server runs locally and manages board items, columns, groups, and API queries from a process you control, for teams that plan in boards rather than Stories.
Set up monday.com →Plane is the closest tracker in shape and open-core: run its server locally to reach the full project API of work items, cycles, and modules, with cycles mapping to Shortcut's Iterations.
Set up Plane →Run locally, the Fetch reference server converts a URL to clean markdown. It is a companion for pulling specs into planning, not a tracker, but it stays entirely on your machine.
Set up Fetch →The Memory reference server runs locally and keeps a knowledge graph of entities, relations, and observations on your own disk, giving an agent recall across sessions alongside a tracker.
Set up Memory →Current-time lookups and timezone conversion from the IANA database are what the locally run Time reference server provides, a small self-contained helper for cross-timezone planning.
Set up Time →Of everything here, Obsidian keeps the most local: its server reads, searches, and edits a Markdown vault on your own disk through the Local REST API plugin, so planning notes never leave the machine.
Set up Obsidian →The community Slack server runs locally over stdio and reads history, DMs, and search with no workspace bot to install. It is the pick when the planning conversation lives in chat rather than a tracker.
Set up Slack →Airtable's maintained server runs locally and is schema-first: inspect a base, then read, search, and write records, fields, and comments, a structured store some teams use the way others use a tracker.
Set up Airtable →
How to choose
Every option here runs on infrastructure you control like Shortcut can. Plane is the closest self-hosted tracker, Monday a board-style fit, and Airtable a structured-records alternative. Obsidian keeps planning notes fully local, Slack covers chat-based planning, and Fetch, Memory, and Time are local utilities. Remember that the hosted-product trackers still send data to their own APIs; only Obsidian keeps the content itself on your disk.
FAQ
- Can the Shortcut MCP server be self-hosted?
- Yes. It ships as a local server you can run over stdio, so the process and your token stay on your own machine while it queries Shortcut's backend. Self-hosting controls the connector rather than where your Stories and Epics are stored.
- Which self-hosted alternative keeps planning data on my own machine?
- Obsidian. It reads and edits a local Markdown vault, so the content stays on your disk. The other trackers here, Monday, Plane, and Airtable, run locally but still send data to their own product APIs, so self-hosting controls the process, not the data path.