Shortcut MCP server for AI agents

Live

API KEY

ISSUE TRACKING

Project Management

Shortcut gives your agent issue tracking for software teams: create and update stories and epics, plan iterations, track objectives and key results, and search across stories, epics, and docs.

  • Per-user credentials: each call uses the actual user's API key, never a shared bot.
  • Encrypted per-tenant vault: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: pre-call scope check, 90-day SIEM-exportable audit chain.
Shortcut
agent · Acme Q3
Run
Which stories in the current iteration are still in progress?
S
shortcut_list_iteration_stories
104ms
Engineering agent
11 stories in Sprint 42 are still in progress. 3 are bugs and 2 have no owner yet.
Sources: 1 iteration, 11 stories
shortcut
11 stories
18:29
Message Claude...

Tools your engineering agent reaches for on Shortcut, scoped per user.

CALL ANY TOOL
124 tools for issue tracking in Shortcut: create, update, and search stories, manage epics, iterations, objectives, and docs, comment on and link stories, and organize labels, groups, and workflows.
shortcut_create_category
Create category
Create an objective category in Shortcut. Returns the created category (ID, name, color, type). Use this to add a category for grouping objectives.
Parameters
Name
Type
Required
Description
name
string
Required
The name of the new Category. Example: Growth.
color
string
Optional
The hex color to be displayed with the Category (for example, "#ff0000"). Example: #3366ff.
external_id
string
Optional
This field can be set to another unique ID. In the case that the Category has been imported from another tool, the ID in the other tool can be indicated here. Example: JIRA-1234.
type
string
Optional
The type of entity this Category is associated with; currently Milestone or Objective is the only type of Category. Example: example.
shortcut_create_epic_comment
Create epic comment
shortcut_create_label
Create label
shortcut_create_project
Create project
shortcut_create_story_from_template
Create story from template
shortcut_delete_category
Delete category
shortcut_delete_epic_comment
Delete epic comment
shortcut_delete_linked_file
Delete linked file
shortcut_delete_story
Delete story
shortcut_get_category
Get category
shortcut_get_doc
Get doc
shortcut_get_epic_health
Get epic health
shortcut_get_group
Get group
shortcut_get_linked_file
Get linked file
shortcut_get_project
Get project
shortcut_get_story_history
Get story history
shortcut_link_doc_to_epic
Link doc to epic
shortcut_list_categories
List categories
shortcut_list_entity_templates
List entity templates
shortcut_list_epics
List epics
shortcut_list_iteration_stories
List iteration stories
shortcut_list_linked_files
List linked files
shortcut_list_project_stories
List project stories
shortcut_query_stories
Query stories
shortcut_search
Search
shortcut_update_category
Update category
shortcut_update_epic
Update epic
shortcut_update_health
Update health
shortcut_update_linked_file
Update linked file
shortcut_update_story
Update story

For more tools, view docs.

Build your Agent
Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.
Python · LlamaIndex
import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Shortcut tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["shortcut"], toolNames: [
    "shortcut_query_stories",
    "shortcut_create_story",
    "shortcut_list_iteration_stories"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "List the stories in the current iteration that are still in progress" }] });
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["shortcut"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "List the stories in the current iteration that are still in progress" }],
  tools,
});

// Execute the tool call with the user's vaulted Shortcut API key
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["shortcut"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "List the stories in the current iteration that are still in progress" }],
  tools,
});

// Tool call runs with the user's vaulted Shortcut API key
await sk.tools.executeTool(msg.content, "user_123");
import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["shortcut"] }, pageSize: 100,
});

const agent = new Agent({
  name: "engineering_agent",
  model: "gemini-2.5-pro",
  instruction: "Shortcut tools scoped to this user",
  tools,
});

await agent.run("List the stories in the current iteration that are still in progress");
Try these prompts
Copy any prompt into your agent. Each maps directly to a Shortcut tool. Click to copy, paste into your agent, done.
Stories
Copy the prompt
Copied
Create a bug story for the login timeout and assign it to me.
Copy the prompt
Copied
Find stories labeled billing that are not done yet.
Copy the prompt
Copied
Add a comment to this story with the repro steps.
Epics and iterations
Copy the prompt
Copied
List the stories in the Checkout Redesign epic.
Copy the prompt
Copied
Create an iteration named Sprint 43 for the next 2 weeks.
Copy the prompt
Copied
Show the current health of the Mobile Launch epic.
Objectives and docs
Copy the prompt
Copied
List our objectives and the epics under each one.
Copy the prompt
Copied
Update the weekly active users key result to 1,200.
Copy the prompt
Copied
Create a doc with the release plan and link it to this epic.
SEE HOW AUTH WORKS
Each user connects their own Shortcut API key once, and Scalekit sends it with every call. Keys stay vaulted, every call is scope checked, and every action is logged.
1
Authorize
Your user connects
Shortcut
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Shortcut
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Shortcut
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Shortcut
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other project management and developer connectors.
Engineering Teams
Engineering standup agent
Pulls commits from GitHub and GitLab, tracks issue movement in Jira, and posts a per-engineer standup brief to Slack. Each engineer's activity is read on their own delegated OAuth.
Engineering Teams
Auto release notes agent
Reads merged GitHub PRs, groups them into structured release notes, publishes the page to Notion, and announces the release in Slack. Every call runs on the engineer's own delegated OAuth.
Engineering Teams
DevOps assistant agent
Polls GitHub for failing checks and stale PRs, opens Linear issues for the ones that need work, and posts a daily digest to Slack. It acts as the engineer, not a shared service account.
Test other agents
See the same per-user auth pattern across other project management and developer connectors.
ENGINEERING
Engineering standup agent
Pull commits from GitHub and GitLab, track Jira issue movement, and post a per-engineer standup brief to Slack.
ENGINEERING
Auto-release notes agent
Group merged GitHub PRs into structured release notes, publish the page to Notion, and announce the release in Slack.
ENGINEERING
DevOps assistant agent
Poll GitHub for failing checks and stale pull requests, open Linear issues for the ones that need work, and digest to Slack.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
01.
Shared tokens break per-user analytics
A shared Shortcut API key looks fine in a demo. In production every story update looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.
// shared key
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Shortcut today. Ten connectors tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access Shortcut as the user or through a shared key?
As the user. Each user connects their own Shortcut API key once, and Scalekit sends it with every call. Audit logs attribute every story, epic, and comment change to that user, not a shared service account.
Where is the Shortcut API key stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. To rotate it, the user reconnects with a new API key. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.
Can I limit what the agent does in Shortcut?
Yes. Filter by tool name in listScopedTools to expose only what you want, for example story and epic tools without shortcut_delete_story or shortcut_delete_stories, which permanently deletes archived stories in bulk. Scalekit also enforces scope checks before every API call.
What happens when a user revokes Shortcut access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.
How does the agent find the right Shortcut stories?
Two ways. shortcut_query_stories matches structured filters such as owner, epic, iteration, team, label, workflow state, and date ranges. shortcut_search takes a free-text query with Shortcut search operators and returns matching stories and epics, and optionally iterations and objectives.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""shortcut"": {
""url"": ""https://mcp.scalekit.com/shortcut"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.shortcut]
url = ""https://mcp.scalekit.com/shortcut""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""shortcut"": {
""url"": ""https://mcp.scalekit.com/shortcut"",
""type"": ""http""
}
}
}