4,500+ servers built on MCP Fusion
Vinkius

Shortcut MCP. Audit your whole project from conversation.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Shortcut MCP on Cursor AI Code Editor MCP Client Shortcut MCP on Claude Desktop App MCP Integration Shortcut MCP on OpenAI Agents SDK MCP Compatible Shortcut MCP on Visual Studio Code MCP Extension Client Shortcut MCP on GitHub Copilot AI Agent MCP Integration Shortcut MCP on Google Gemini AI MCP Integration Shortcut MCP on Lovable AI Development MCP Client Shortcut MCP on Mistral AI Agents MCP Compatible Shortcut MCP on Amazon AWS Bedrock MCP Support

Just plug in your AI agents and start using Vinkius.

Shortcut MCP Server lets your AI agent act as a full project auditor right inside your IDE. Use it to search for specific stories, check every Epic on the roadmap, list all team members, or audit complex workflows without touching the web UI.

What your AI agents can do

Get story details

Retrieves all necessary details for a single, specific story ticket.

List epics

Lists every high-level Epic in your Shortcut workspace.

List iterations

Lists all active sprints or time-boxed iterations for the project.

+ 4 more capabilities included
Search for specific stories

Run search_stories to find tickets based on keywords or criteria across the entire backlog.

Retrieve detailed story information

Use get_story_details to pull every description, sub-task, and piece of history for a single ticket ID.

Audit project roadmaps

List all high-level Epics (list_epics) and ongoing sprints (list_iterations) to track roadmap status without opening the main dashboard.

Map team structure

Pull a list of all workspace members using list_members or identify entire projects via list_projects.

Inspect workflow states

Run list_workflows to see every possible state and transition path an issue can take in your organization.

Supported MCP Clients

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients
Free for Subscribers

Waiting for input…

AI Agent

Shortcut MCP Server: 7 Tools for Project Management

Use these tools to let your AI client read the full context of your Shortcut workspace—from high-level Epics down to individual sub-tasks.

get019d7607

get story details

Retrieves all necessary details for a single, specific story ticket.

list019d7607

list epics

Lists every high-level Epic in your Shortcut workspace.

list019d7607

list iterations

Lists all active sprints or time-boxed iterations for the project.

list019d7607

list members

Retrieves a list of every user member in your Shortcut workspace.

list019d7607

list projects

Lists all distinct projects within the overall Shortcut account structure.

list019d7607

list workflows

Shows every defined workflow and all possible states a story can transition through.

search019d7607

search stories

Searches the entire backlog for stories using keywords or filters.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

  • Import from OpenAPI, Swagger, or YAML specs
  • Create Agent Skills with progressive disclosure
  • Deploy to edge with MCPFusion framework
  • Built in DLP, auth, and compliance on every call
  • Real time usage dashboard and cost metering
  • Publish to catalog or keep private
Start building

Make Your AI Do More

Start with Shortcut, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.

  • Use this MCP plus 4,700+ others, all in one place
  • Add new capabilities to your AI anytime you want
  • Every connection is secured and compliant automatically
  • Track usage and costs across all your servers
  • Works with Claude, ChatGPT, Cursor, and more
  • New servers added to the catalog every week

What you can do with this MCP connector

Your AI client doesn't have to click through endless boards just to get answers. This server gives your agent direct, administrative access to everything in your Shortcut project management environment, letting you treat it like a raw data source instead of a pretty dashboard. You can turn natural conversation into actionable API calls that pull the exact info you need.

Think of this setup as having a full-time auditor on retainer who knows every corner of your backlog and process flow. It lets you interrogate backlogs, audit sprints, and check team structure without ever opening the main web UI or touching a single button. You're working with the system’s underlying data layer.

When you need to find something specific, search_stories searches the entire backlog for stories using keywords or filters; it finds tickets across all projects that match what you’re looking for. If you zero in on one ticket and need every detail—the full description, sub-tasks, and history of changes—you use get_story_details to pull everything associated with a single ticket ID.

For tracking the big picture, you can audit your project roadmaps by running list_epics to get a list of all high-level Epics in your workspace. You'll also run list_iterations to see every active sprint or time-boxed cycle for the whole project. This lets you track roadmap status without having to open up the main dashboard and click through multiple tabs.

To map out who's running what, you can pull a list of all workspace members using list_members. You also use list_projects when you need to identify every distinct project that exists within your overall Shortcut account structure. This gives you a complete scope of the organization’s work.

If you wanna check how things actually flow, you run list_workflows to see every possible state and transition path an issue can take in your company. That's your blueprint for process auditing. You can also use list_workflows to understand every defined workflow and all the specific states a story might pass through.

This comprehensive set of tools means you don’t have to guess where data lives or spend time navigating menus. Your agent handles the heavy lifting, giving you clean, raw data sets instantly—whether that's checking the full scope of your project structure via list_projects, getting a snapshot of all active sprints with list_iterations, or locating one obscure ticket deep in the backlog using search_stories.

It’s pure power for your agent to run these administrative checks and audits right where you write code.

How Shortcut MCP Works

  1. 1 Anchor this core interface directly into your AI agent framework.
  2. 2 Securely store your SHORTCUT_API_TOKEN within the workspace boundary. This locks down security.
  3. 3 Prompt your agent: "Find all bugs reported this week and tell me what Epic they belong to based on their details!"

The bottom line is, you send a natural language prompt, and the server executes multiple API calls using the appropriate tool.

Who Is Shortcut MCP For?

The Product Manager who's tired of clicking through dashboards at 2 am. The Scrum Master who needs an immediate status report across multiple Epics before a meeting. Or the Backend Developer needing to check task details or team assignments without leaving their IDE.

Product Manager

Uses list_epics and search_stories to quickly audit overall roadmap health against reported issues.

Scrum Master

Runs list_iterations and list_workflows to validate sprint scope and understand task progression rules.

Developer Operations (DevOps)

Uses list_members and list_projects to verify team assignments and project ownership before deploying code.

What Changes When You Connect

  • Stop clicking through dashboards. You can interrogate task backlogs and audit sprints using list_epics or list_iterations directly via natural prompts.
  • Need deep context on one ticket? Use get_story_details. It pulls every sub-task, description, and detail for a story without leaving your IDE.
  • Verify team structure instantly. Run list_members to get all user IDs or use list_projects to see the full scope of work happening across different containers.
  • Understand task flow immediately. Checking list_workflows shows you every possible state and transition a story can hit, which is critical for identifying process blockers.
  • Pinpoint issues fast. Instead of manual filtering, use search_stories to find all tickets mentioning 'database timeout' across the whole backlog.

Real-World Use Cases

01

Auditing a stalled roadmap

The PM realizes the Q3 goals are slipping. They prompt their agent: "List all Epics and then list all iterations." The agent runs list_epics followed by list_iterations, instantly showing which sprints haven't been updated in weeks, allowing them to flag bottlenecks immediately.

02

Checking team roles before a meeting

A developer needs to know who owns the 'Billing' project. They prompt: "Show me all projects and then list members for Project X." The agent first calls list_projects to find the ID, then uses list_members to deliver a precise roster of required stakeholders.

03

Debugging an unknown task state

A QA tester finds a story stuck in 'Pending Review.' They prompt: "What are all possible workflows for this project?" The agent runs list_workflows, showing the exact states and transitions, proving if the current status is even valid.

04

Mass incident review

The team needs to check every story referencing 'login failure' from last month. They run a focused prompt: "Search stories for login failures." The agent executes search_stories, returning all relevant ticket IDs, which they can then use with get_story_details for deep context.

The Tradeoffs

Relying on basic keyword searches

Just searching the UI for 'bug' and manually clicking through 50 results to see which Epic they belong to.

Don't search only. First, run list_epics to get a map of all high-level goals. Then, use search_stories with keywords AND reference the target Epic ID in your prompt for context.

Checking project scope manually

Opening the main navigation menu and clicking through every single project listing to ensure nothing was missed.

Run list_projects once. This gives you a clean, exhaustive list of all active projects in one go, saving minutes on setup.

Forgetting process constraints

Assuming a story can move from 'To Do' directly to 'Done' without passing through necessary review stages.

Check list_workflows first. This tells you the actual, required path and states for your project, preventing invalid transitions.

When It Fits, When It Doesn't

Use this MCP Server if you need to perform multiple, connected actions across the entire Shortcut ecosystem—like 'Find all bugs in Project A that belong to Epic B.' This is about auditing relationships. Don't use it if you just need a single piece of information (e.g., 'What are the details for ticket 123?'). For that, get_story_details is enough. If you only need a general overview of what projects exist, running list_projects is simpler than building a complex prompt. Always start by listing high-level containers (list_epics, list_projects) to scope your query before diving into specific stories with search_stories.

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Shortcut. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

How we secure it →

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This server provides 7 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.

Available Capabilities

get_story_details list_epics list_iterations list_members list_projects list_workflows search_stories

Tracking project status shouldn't take 20 clicks.

Today, figuring out the full status of a feature requires navigating between the Project board, cross-referencing Epics on another dashboard tab, and manually checking which team member was assigned to what specific story. You end up in copy/paste hell just trying to build a simple report.

With this MCP server, you prompt your agent: 'What's the status of the billing module?' The agent executes `list_epics` and then filters down using `search_stories`. It gives you the answer—the data—in text form. No clicking required.

Shortcut MCP Server: Audit your whole project from conversation.

Before this, if a developer needed to know what states a story could even enter, they had to find the documentation or ask a PM. It was an interruptive process that slowed down flow and required context switching.

Now, run `list_workflows`. You see every defined state ('In Dev,' 'Ready for QA,' etc.) immediately. This gives you instant knowledge of your process boundaries, letting developers move faster because they know the rules.

Common Questions About Shortcut MCP

How do I find a specific story using search_stories? +

Just ask your agent to run search_stories with keywords. You can specify 'database timeout' or 'login failure,' and it hits the entire backlog.

What is list_epics used for? +

list_epics lists all major Epics in your workspace. This lets you see the top-level goals—the big roadmap items—without needing to filter through thousands of individual stories.

Can I use get_story_details on a specific ticket? +

Yes, that's its job. You pass it the story ID, and it pulls every piece of associated data for you: all sub-tasks, notes, descriptions, etc.

What is the difference between list_projects and list_members? +

list_projects gives you a directory of work containers. list_members tells you which people exist in the system; they are separate lists used for different types of context.

How should I authenticate my connection to use `list_workflows` securely? +

You must provide a dedicated API token within your agent's environment. This token controls the scope of access, ensuring your AI client can only read project data you explicitly authorize.

How does using `list_workflows` help map all possible issue states? +

It lists every defined workflow and its associated status tags. This reveals exactly which statuses (e.g., 'To Do' or 'In Review') a story can legally transition into within the Shortcut system.

When running deep searches with `search_stories`, what should I expect if the API hits a rate limit? +

The server handles standard API rate limiting through structured error responses. Your agent must implement retry logic, specifically checking for HTTP 429 status codes to manage flow interruptions gracefully.

Does `list_iterations` handle large datasets by allowing pagination? +

Yes, the tool supports cursor-based pagination. When a request exceeds the default page size, subsequent calls must use the provided next cursor token to retrieve all remaining data chunks.

Can the integration alter, comment in, or edit stories directly? +

By structural design, this module is strictly bound as an observational lens. Operations such as search_stories, list_epics, and get_story_details parse and extract massive context. It omits explicitly write mechanisms preventing your autonomous agent from accidentally sabotaging valid roadmap components permanently.

Why use the token via MCP instead of normal webhook integrations? +

Webhooks exclusively wait for explicit platform triggers passively. The MCP configuration hands your prompt active, unadulterated runtime authority to scan iterations, grab user arrays, and interrogate backlog metadata aggressively instantly dynamically. It permits pulling, rather than simply listening blindly.

Can the integration directly access workspaces not associated with the token creator? +

No. The highly sensitive REST API access token acts inherently as a mapped functional clone of the exact user credentials operating at generation time. Searching workflows, epics, and members evaluates precisely against the internal permissions bounds of the token creator robustly limiting toxic footprint.

More in this category

You might also like

Built & Managed by Vinkius 30s setup 7 tools

We've already built the connector for Shortcut. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 7 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.