com.mcparmory/shortcut
PYPI · MCPARMORY-SHORTCUT · 2 COMPONENTS · SCANNED SEP 20
Track stories, organize sprints, and manage project workflows across your team
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Install-script risk not yet assessed.Unverified
- 2 of 41 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 130 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 15239 tokens (~116/item across 131 items; 131 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 22 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 131 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the com.mcparmory/shortcut MCP server?
com.mcparmory/shortcut runs locally as a PyPI package, launched with uvx mcparmory-shortcut. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcparmory-shortcut
claude mcp add com-mcparmory-shortcut -- uvx mcparmory-shortcut
{
"mcpServers": {
"com-mcparmory-shortcut": {
"command": "uvx",
"args": [
"mcparmory-shortcut"
]
}
}
} {
"servers": {
"com-mcparmory-shortcut": {
"command": "uvx",
"args": [
"mcparmory-shortcut"
]
}
}
} codex mcp add com-mcparmory-shortcut -- uvx mcparmory-shortcut
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-shortcut": {
"type": "local",
"command": [
"uvx",
"mcparmory-shortcut"
],
"enabled": true
}
}
} openclaw mcp add com-mcparmory-shortcut --command uvx --arg mcparmory-shortcut
mcp_servers:
com-mcparmory-shortcut:
command: "uvx"
args: ["mcparmory-shortcut"] {
"McpServers": {
"com-mcparmory-shortcut": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcparmory-shortcut"
]
}
}
} assistant mcp add com-mcparmory-shortcut -t stdio -c uvx -a mcparmory-shortcut
{
"mcpServers": {
"com-mcparmory-shortcut": {
"command": "uvx",
"args": [
"mcparmory-shortcut"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +12
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.80 functional
- 17 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/mcparmory-shortcut@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Dependencies 41 packages
| Packages resolved | 41 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_reaction_to_story_comment Add Reaction to Story Comment ~148
Add an emoji reaction to a comment on a story. Use emoji short-codes (e.g., `:thumbsup::skin-tone-4:`) to express reactions.
| Name | Type | Req | Description |
|---|---|---|---|
| comment-public-id | string | yes | The unique identifier of the comment to react to. Must be a positive integer. |
| emoji | string | yes | The emoji short-code to add or remove as a reaction (e.g., `:thumbsup::skin-tone-4:`, `:heart:`, `:laughing:`). Use standard emoji short-code format with colons. |
| story-public-id | string | yes | The unique identifier of the story containing the comment. Must be a positive integer. |
No output schema declared.
No examples provided.
create_category Create Category ~111
Create a new Category in Shortcut for organizing Milestones or Objectives. Categories help structure and group related work items by type.
| Name | Type | Req | Description |
|---|---|---|---|
| external_id | string | – | An optional external identifier for this Category, useful when importing from another tool. Must be between 1 and 128 characters if provided. |
| name | string | yes | The display name for the new Category. Must be between 1 and 128 characters. |
| type | – | – | The entity type this Category is associated with. Currently supports Milestone or Objective types. |
No output schema declared.
No examples provided.
create_document Create Document ~77
Creates a new document with the specified title and content. Supports both markdown and HTML content formats via the content_format parameter.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The document content. Can be formatted as markdown or HTML depending on the content_format parameter. |
| title | string | yes | The document title. Must be between 1 and 256 characters long. |
No output schema declared.
No examples provided.
create_epic Create Epic ~335
Create a new Epic in Shortcut. An Epic is a large body of work that can be broken down into Stories and related to Objectives and Groups.
| Name | Type | Req | Description |
|---|---|---|---|
| converted_from_story_id | string | – | The numeric ID of a Story that was converted into this Epic. Use this when promoting an existing Story to Epic status. |
| deadline | string | – | The date by which this Epic must be completed. Specify as an ISO 8601 formatted date-time string. |
| description | string | – | A detailed explanation of the Epic's purpose and scope. Limited to 100,000 characters. |
| epic_state_id | string | – | The numeric ID of the Epic State that defines the Epic's workflow status (e.g., Backlog, In Progress, Done). |
| external_id | string | – | An external identifier for this Epic, useful when importing from other tools or systems. Limited to 128 characters and should be unique within your workspace. |
| group_ids | array | – | An array of Group UUIDs to associate with this Epic. Groups help organize and categorize Epics within your workspace. |
| name | string | yes | The Epic's title or name. Required field, must be between 1 and 256 characters. |
| objective_ids | array | – | An array of Objective IDs to associate with this Epic. Objectives provide strategic alignment for the Epic. |
| planned_start_date | string | – | The date when work on this Epic is planned to begin. Specify as an ISO 8601 formatted date-time string. |
| requested_by_id | string | – | The UUID of the team member who requested this Epic. Used to track Epic ownership and accountability. |
No output schema declared.
No examples provided.
create_epic_comment Create Epic Comment ~151
Add a threaded comment to an Epic. The comment can be authored by the API token holder or another team member, and optionally linked to an external system via an external ID.
| Name | Type | Req | Description |
|---|---|---|---|
| author_id | string | – | The UUID of the team member who authored this comment. If not provided, defaults to the user associated with the API token. |
| epic-public-id | string | yes | The unique identifier of the Epic where the comment will be posted. |
| external_id | string | – | An optional external identifier for this comment, useful when importing comments from other tools. Maximum length is 128 characters. |
| text | string | yes | The comment text content. Must be between 1 and 100,000 characters. |
No output schema declared.
No examples provided.
create_epic_health Create Epic Health ~132
Create a new health status record for an Epic to track its current state. This allows you to document whether the Epic is progressing as planned, facing risks, or has encountered issues.
| Name | Type | Req | Description |
|---|---|---|---|
| epic-public-id | string | yes | The unique identifier of the Epic for which you're creating a health status. Must be a valid 64-bit integer. |
| status | string | yes | The health status level for the Epic. Must be one of: 'At Risk', 'On Track', 'Off Track', or 'No Health'. |
| text | string | – | An optional detailed explanation or context for the health status being recorded. |
No output schema declared.
No examples provided.
create_group Create Group ~217
Create a new group with members and workflows. Groups can be used to organize and manage collections of members and their associated workflows.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | A detailed description of the group's purpose and scope, up to 4096 characters. |
| display_icon_id | string | – | A UUID-formatted icon ID to use as the group's avatar. If not provided, a default icon will be assigned. |
| member_ids | array | – | Array of member IDs to add to the group upon creation. Members can be added or modified after creation. |
| mention_name | string | yes | The mention handle for the group, between 1 and 63 characters. Used for @-mentions and programmatic references (e.g., @engineering-team). |
| name | string | yes | The display name of the group, between 1 and 63 characters. This is the human-readable identifier shown in the UI. |
| workflow_ids | array | – | Array of workflow IDs to associate with the group. Workflows define the processes and automations available to group members. |
No output schema declared.
No examples provided.
create_iteration Create Iteration ~203
Create a new iteration (sprint or planning cycle) with a specified name, date range, and optional description. Optionally add groups as followers to the iteration.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | A detailed description of the iteration's purpose or scope. Limited to 100,000 characters. |
| end_date | string | yes | The end date of the iteration in ISO 8601 format (e.g., 2019-07-01). Required and must be a valid date string. |
| group_ids | array | – | An array of group UUIDs to add as followers to this iteration. Currently, the web UI supports only one group association at a time. |
| name | string | yes | The name of the iteration. Must be between 1 and 256 characters. |
| start_date | string | yes | The start date of the iteration in ISO 8601 format (e.g., 2019-07-01). Required and must be a valid date string. |
No output schema declared.
No examples provided.
create_label Create Label ~125
Create a new label in Shortcut to organize and categorize work items. Labels help teams tag and filter issues, stories, and other work across projects.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional descriptive text explaining the label's purpose or usage. Limited to 1024 characters. |
| external_id | string | – | Optional external identifier for labels imported from other tools. Use this to maintain references to the original tool's ID. Must be between 1 and 128 characters if provided. |
| name | string | yes | The display name for the label. Must be between 1 and 128 characters. |
No output schema declared.
No examples provided.
create_linked_file Create Linked File ~241
Create a new linked file in Shortcut that references an external file from an integrated service like Google Drive, Dropbox, Box, OneDrive, or a direct URL. Optionally associate the file with a specific story.
| Name | Type | Req | Description |
|---|---|---|---|
| content_type | string | – | The MIME type describing the file's format (e.g., text/plain, application/pdf). Limited to 128 characters. |
| description | string | – | A brief explanation of the file's purpose or contents. Limited to 512 characters. |
| name | string | yes | The display name for the linked file. Must be between 1 and 256 characters. |
| story_id | string | – | The numeric ID of the story to associate this linked file with. If omitted, the file is created without a story association. |
| type | string | yes | The source service or integration type for the file. Must be one of: google (Google Drive), url (direct link), dropbox (Dropbox), box (Box), or onedrive (OneDrive). |
| url | string | yes | The full URL pointing to the linked file. Must be a valid HTTP or HTTPS URL and cannot exceed 2048 characters. |
No output schema declared.
No examples provided.
create_milestone Create Milestone ~105
Create a new Milestone in Shortcut. Note: This operation is deprecated; use create_objective for new implementations.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | Optional array of Category IDs to attach to the Milestone. Provide as a list of numeric identifiers. |
| description | string | – | Optional description of the Milestone. Can be up to 100,000 characters. |
| name | string | yes | The name of the Milestone. Must be between 1 and 256 characters. |
No output schema declared.
No examples provided.
create_objective Create Objective ~112
Create a new Objective in Shortcut to define goals and track progress. Objectives can be organized with categories and include detailed descriptions.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | An array of Category IDs to associate with this Objective for organizational purposes. Each ID should reference an existing Category. |
| description | string | – | A detailed description of the Objective. Can be up to 100,000 characters to provide comprehensive context and guidance. |
| name | string | yes | The name of the Objective. Must be between 1 and 256 characters. |
No output schema declared.
No examples provided.
create_project Create Project ~209
Creates a new Shortcut project within a specified team. The project name is required, and you can optionally configure iteration length, description, start date, abbreviation, and external identifiers.
| Name | Type | Req | Description |
|---|---|---|---|
| abbreviation | string | – | A short abbreviation for the project, typically 3 characters or fewer, used in story summaries. Limited to 63 characters. |
| description | string | – | A detailed description of the project's purpose and scope. Limited to 100,000 characters. |
| external_id | string | – | An external identifier for the project, useful when migrating from another tool. Limited to 128 characters. |
| iteration_length | string | – | The duration of each iteration cycle in this project, specified in weeks. |
| name | string | yes | The display name for the project. Must be between 1 and 128 characters long. |
| start_time | string | – | The project's start date in ISO 8601 date-time format. |
| team_id | string | yes | The numeric ID of the team that will own this project. |
No output schema declared.
No examples provided.
create_reply_to_epic_comment Create Reply to Epic Comment ~179
Create a nested reply to an existing Epic Comment. This allows you to add threaded discussion to Epic Comments within an Epic.
| Name | Type | Req | Description |
|---|---|---|---|
| author_id | string | – | The UUID of the team member who authored this reply. If not provided, defaults to the user associated with the API token making the request. |
| comment-public-id | string | yes | The unique identifier of the parent Epic Comment to which you are replying. Must be a positive integer. |
| epic-public-id | string | yes | The unique identifier of the Epic containing the parent comment. Must be a positive integer. |
| external_id | string | – | An optional external identifier for this comment, useful when importing comments from other tools. Maximum length is 128 characters. |
| text | string | yes | The text content of the reply. Must be between 1 and 100,000 characters. |
No output schema declared.
No examples provided.
create_stories Create Stories ~65
Create multiple stories in a single batch request. Each story is created with the same configuration options available in individual story creation.
| Name | Type | Req | Description |
|---|---|---|---|
| stories | array | yes | An array of story objects to create. Each story object uses the same schema as individual story creation. Order is preserved in processing. |
No output schema declared.
No examples provided.
create_story Create Story ~423
Create a new story in your Shortcut workspace. You must specify either a workflow_state_id or project_id (but not both); workflow_state_id is recommended as projects are being sunset.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | Whether the story should be archived upon creation. |
| comments | array | – | An array of comments to add to the story immediately upon creation. |
| deadline | string | – | The story's due date in ISO 8601 format. |
| description | string | – | The story's description text. Supports up to 100,000 characters. |
| estimate | string | – | The point estimate for this story's complexity. Can be null to leave unestimated. |
| external_id | string | – | An external identifier for this story, useful when importing from other tools. Supports up to 1,024 characters. |
| iteration_id | string | – | The numeric ID of the iteration this story belongs to. |
| name | string | yes | The story's title. Must be between 1 and 512 characters. |
| parent_story_id | string | – | The numeric ID of the parent story, making this story a sub-task. Only applicable when the Sub-task feature is enabled. |
| requested_by_id | string | – | The UUID of the team member who requested this story. |
| story_links | array | – | An array of story links to attach to this story. Each link establishes a relationship between stories. |
| story_template_id | string | – | Associates this story with a story template by its UUID. No template content is automatically inherited. |
| story_type | string | – | Categorizes the story as a feature, bug, or chore. |
| sub_tasks | array | – | An array of sub-tasks to create or link. Each entry can reference an existing story or define a new sub-task. Only applicable when the Sub-task feature is enabled. |
| tasks | array | – | An array of tasks to associate with this story. |
| workflow_state_id | string | – | The numeric ID of the workflow state for this story. Either this or project_id must be provided, but not both. |
No output schema declared.
No examples provided.
create_story_comment Create Story Comment ~178
Add a comment to a story. Comments can be standalone or threaded as replies to existing comments.
| Name | Type | Req | Description |
|---|---|---|---|
| author_id | string | – | The UUID of the team member authoring the comment. If not provided, defaults to the user associated with the API token. |
| external_id | string | – | An external identifier for the comment, useful when migrating comments from other tools. Maximum length is 1,024 characters. |
| parent_id | string | – | The ID of the parent comment to thread this comment under as a reply. If omitted, the comment will be a top-level comment on the story. |
| story-public-id | string | yes | The unique identifier of the story where the comment will be posted. Must be a valid 64-bit integer. |
| text | string | yes | The comment text content. Supports up to 100,000 characters. |
No output schema declared.
No examples provided.
create_story_from_template Create Story from Template ~911
Create a new story in your Shortcut workspace based on a story template, with the ability to customize or override template values for all story attributes.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | Whether the story should be archived. Defaults to false if not specified. |
| comments | array | – | An array of comment objects to add to the story upon creation. |
| custom_fields_add | array | – | An array of custom field assignments, each specifying a custom field ID and its enum value. These are added to template values. Cannot be combined with custom_fields_remove. |
| custom_fields_remove | array | – | An array of custom field IDs to remove from the template's custom field values. Cannot be combined with custom_fields_add. |
| deadline | string | – | The story's due date in ISO 8601 format (e.g., 2024-12-31T23:59:59Z). |
| description | string | – | The story's description text. Limited to 100,000 characters. |
| estimate | string | – | The numeric point estimate for story complexity. Can be null to leave unestimated. |
| external_id | string | – | An external identifier for this story, useful when importing from other tools. Limited to 1,024 characters. |
| external_links_add | array | – | An array of external links to add to the story in addition to any provided by the template. Cannot be combined with external_links_remove. |
| external_links_remove | array | – | An array of external links to remove from the template's external links. Cannot be combined with external_links_add. |
| file_ids_add | array | – | An array of file IDs to attach to the story in addition to files from the template. Cannot be combined with file_ids_remove. |
| file_ids_remove | array | – | An array of file IDs to remove from the template's attached files. Cannot be combined with file_ids_add. |
| follower_ids_add | array | – | An array of member UUIDs to add as followers in addition to followers from the template. Cannot be combined with follower_ids_remove. |
| follower_ids_remove | array | – | An array of member UUIDs to remove from the template's followers. Cannot be combined with follower_ids_add. |
| iteration_id | string | – | The numeric ID of the iteration (sprint) this story belongs to. |
| labels_add | array | – | An array of label names or IDs to add to the story in addition to labels from the template. Cannot be combined with labels_remove. |
| labels_remove | array | – | An array of label names or IDs to remove from the template's labels. Cannot be combined with labels_add. |
| linked_file_ids_add | array | – | An array of linked file IDs to attach to the story in addition to files from the template. Cannot be combined with linked_file_ids_remove. |
| linked_file_ids_remove | array | – | An array of linked file IDs to remove from the template's linked files. Cannot be combined with linked_file_ids_add. |
| name | string | – | The story's title. Required if the template does not provide a name. Must be between 1 and 512 characters. |
| owner_ids_add | array | – | An array of member UUIDs to add as owners in addition to owners from the template. Cannot be combined with owner_ids_remove. |
| owner_ids_remove | array | – | An array of member UUIDs to remove from the template's owners. Cannot be combined with owner_ids_add. |
| parent_story_id | string | – | The numeric ID of the parent story, making this story a sub-task. Only applicable when the Sub-task feature is enabled. |
| requested_by_id | string | – | The UUID of the workspace member who requested this story. |
| story_links | array | – | An array of story links to attach to this story, establishing relationships with other stories. |
| story_template_id | string | yes | The UUID of the story template to use as the basis for this story. Required. |
| story_type | string | – | The story's type classification. Must be one of: feature, chore, or bug. |
| sub_tasks | array | – | An array of sub-task definitions to associate with the story. Each entry can link to an existing story or create a new sub-task. Only applicable when the Sub-task feature is enabled. |
| tasks | array | – | An array of task objects to create and associate with the story. |
| workflow_state_id | string | – | The numeric ID of the workflow state this story should be placed in. |
No output schema declared.
No examples provided.
create_story_link Create Story Link ~155
Create a semantic relationship between two stories by specifying how one story acts upon another. The subject story performs an action (blocks, duplicates, or relates to) on the object story, establishing a directional dependency or association.
| Name | Type | Req | Description |
|---|---|---|---|
| object_id | string | yes | The numeric ID of the story being acted upon (the object of the relationship). |
| subject_id | string | yes | The numeric ID of the story performing the action (the subject of the relationship). |
| verb | string | yes | The relationship type expressed as an active voice verb. Must be one of: 'blocks' (subject prevents object from progressing), 'duplicates' (subject and object represent identical work), or 'relates t… |
No output schema declared.
No examples provided.
create_task_in_story Create Task in Story ~155
Create a new task within a Story. Tasks are actionable items that can be marked complete and optionally linked to external systems via an external ID.
| Name | Type | Req | Description |
|---|---|---|---|
| complete | boolean | – | Optional boolean flag to set the task's completion status. Defaults to false (incomplete) if not provided. |
| description | string | yes | A text description of the task. Must be between 1 and 2048 characters. |
| external_id | string | – | Optional identifier for linking this task to an external system or tool. Useful when importing tasks from other platforms. Maximum length is 128 characters. |
| story-public-id | string | yes | The unique identifier of the Story where the task will be created. Must be a valid 64-bit integer. |
No output schema declared.
No examples provided.
delete_category Delete Category ~53
Permanently delete a category by its unique identifier. This operation removes the category and cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| category-public-id | string | yes | The unique identifier of the category to delete, provided as a 64-bit integer. |
No output schema declared.
No examples provided.
delete_custom_field Delete Custom Field ~51
Permanently delete a custom field by its unique identifier. This operation removes the custom field and all associated data.
| Name | Type | Req | Description |
|---|---|---|---|
| custom-field-public-id | string | yes | The unique UUID identifier of the custom field to delete. |
No output schema declared.
No examples provided.
delete_doc Delete Document ~61
Permanently deletes a Doc and all its associated data. Requires admin access to the document. Connected clients will be notified of the deletion via SSE events.
| Name | Type | Req | Description |
|---|---|---|---|
| doc-public-id | string | yes | The unique public identifier of the Doc to delete, formatted as a UUID. |
No output schema declared.
No examples provided.
delete_epic Delete Epic ~54
Permanently delete an Epic by its unique identifier. This operation removes the Epic and cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| epic-public-id | string | yes | The unique identifier of the Epic to delete, specified as a 64-bit integer. |
No output schema declared.
No examples provided.
delete_epic_comment Delete Epic Comment ~72
Permanently delete a comment from an epic. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| comment-public-id | string | yes | The unique identifier of the comment to delete. Must be a positive integer. |
| epic-public-id | string | yes | The unique identifier of the epic containing the comment. Must be a positive integer. |
No output schema declared.
No examples provided.
delete_file Delete File ~51
Permanently delete a previously uploaded file by its unique identifier. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| file-public-id | string | yes | The unique identifier of the file to delete, provided as a 64-bit integer. |
No output schema declared.
No examples provided.
delete_iteration Delete Iteration ~59
Permanently delete an iteration by its public ID. This action cannot be undone and will remove the iteration and all associated data.
| Name | Type | Req | Description |
|---|---|---|---|
| iteration-public-id | string | yes | The unique public identifier of the iteration to delete, provided as a 64-bit integer. |
No output schema declared.
No examples provided.
delete_label Delete Label ~53
Permanently delete a label by its unique identifier. This operation removes the label and cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| label-public-id | string | yes | The unique identifier of the label to delete, specified as a 64-bit integer. |
No output schema declared.
No examples provided.
delete_linked_file Delete Linked File ~62
Permanently delete a previously attached linked file by its unique identifier. This operation removes the file association and cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| linked-file-public-id | string | yes | The unique identifier of the linked file to delete. Must be a valid 64-bit integer. |
No output schema declared.
No examples provided.
delete_milestone Delete Milestone ~59
Delete a milestone by its public ID. Note: This operation is deprecated; use delete_objective instead for new implementations.
| Name | Type | Req | Description |
|---|---|---|---|
| milestone-public-id | string | yes | The unique identifier of the milestone to delete, specified as a 64-bit integer. |
No output schema declared.
No examples provided.
delete_objective Delete Objective ~51
Permanently delete an Objective by its public ID. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| objective-public-id | string | yes | The unique public identifier of the Objective to delete, specified as a 64-bit integer. |
No output schema declared.
No examples provided.
delete_project Delete Project ~70
Permanently delete a project. Projects can only be deleted if all associated stories have been moved or deleted; attempting to delete a project with remaining stories will result in a 422 error.
| Name | Type | Req | Description |
|---|---|---|---|
| project-public-id | string | yes | The unique identifier of the project to delete, provided as a 64-bit integer. |
No output schema declared.
No examples provided.
delete_stories_bulk Delete Stories in Bulk ~79
Permanently delete multiple archived stories in a single operation. This bulk deletion operation allows you to remove several stories at once by providing their IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| story_ids | array | yes | A list of story IDs to delete. Provide the IDs as an array of strings or numbers representing the stories you want to remove. All stories must be archived before deletion. |
No output schema declared.
No examples provided.
delete_story Delete Story ~51
Permanently delete a story by its public ID. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| story-public-id | string | yes | The unique public identifier of the story to delete. Must be a valid 64-bit integer. |
No output schema declared.
No examples provided.
delete_story_comment Delete Story Comment ~76
Remove a comment from a story. This permanently deletes the specified comment and cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| comment-public-id | string | yes | The unique identifier of the comment to delete. Must be a positive integer. |
| story-public-id | string | yes | The unique identifier of the story containing the comment to delete. Must be a positive integer. |
No output schema declared.
No examples provided.
delete_story_link Delete Story Link ~69
Removes the relationship between two stories by deleting the specified Story Link. This operation severs the connection without affecting the individual stories themselves.
| Name | Type | Req | Description |
|---|---|---|---|
| story-link-public-id | string | yes | The unique identifier of the Story Link to delete. This is a 64-bit integer that uniquely identifies the relationship between stories. |
No output schema declared.
No examples provided.
delete_task Delete Task ~76
Permanently delete a Task from a Story. This operation removes the Task and all associated data.
| Name | Type | Req | Description |
|---|---|---|---|
| story-public-id | string | yes | The unique identifier of the Story containing the Task to delete. Must be a positive integer. |
| task-public-id | string | yes | The unique identifier of the Task to delete. Must be a positive integer. |
No output schema declared.
No examples provided.
delete_webhook_integration Delete Webhook Integration ~62
Permanently delete a webhook integration by its public identifier. This action cannot be undone and will remove all associated webhook configurations.
| Name | Type | Req | Description |
|---|---|---|---|
| integration-public-id | string | yes | The unique public identifier of the webhook integration to delete, provided as a 64-bit integer. |
No output schema declared.
No examples provided.
get_category Get Category ~49
Retrieve detailed information about a specific category using its unique identifier. Returns the category's properties and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| category-public-id | string | yes | The unique identifier for the category as a 64-bit integer. |
No output schema declared.
No examples provided.
get_current_member Get Current Member ~24
Retrieves detailed information about the authenticated member, including profile data and account settings.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_custom_field Get Custom Field ~54
Retrieve a specific custom field by its unique identifier. Returns the complete configuration and metadata for the custom field.
| Name | Type | Req | Description |
|---|---|---|---|
| custom-field-public-id | string | yes | The unique identifier of the custom field to retrieve, formatted as a UUID. |
No output schema declared.
No examples provided.
get_doc Get Document ~57
Retrieve a Doc by its public ID, including its full content. Optionally request HTML-formatted content using the content_format query parameter.
| Name | Type | Req | Description |
|---|---|---|---|
| doc-public-id | string | yes | The unique identifier of the Doc to retrieve, formatted as a UUID. |
No output schema declared.
No examples provided.
get_entity_template Get Entity Template ~58
Retrieve detailed information about a specific entity template using its unique identifier. This operation returns the complete configuration and metadata for the requested entity template.
| Name | Type | Req | Description |
|---|---|---|---|
| entity-template-public-id | string | yes | The unique identifier of the entity template, formatted as a UUID. |
No output schema declared.
No examples provided.
get_epic Get Epic ~55
Retrieve detailed information about a specific Epic by its unique identifier. Returns the Epic's properties and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| epic-public-id | string | yes | The unique identifier of the Epic to retrieve. Must be a valid 64-bit integer. |
No output schema declared.
No examples provided.
get_epic_comment Get Epic Comment ~93
Retrieves detailed information about a specific comment on an Epic. Use this to fetch comment content, metadata, and other details by providing both the Epic ID and the Comment ID.
| Name | Type | Req | Description |
|---|---|---|---|
| comment-public-id | string | yes | The unique identifier of the specific comment to retrieve. Must be a positive integer. |
| epic-public-id | string | yes | The unique identifier of the Epic that contains the comment. Must be a positive integer. |
No output schema declared.
No examples provided.
get_epic_health Get Epic Health ~56
Retrieve the current health status of a specified Epic. This provides insights into the Epic's overall condition and progress.
| Name | Type | Req | Description |
|---|---|---|---|
| epic-public-id | string | yes | The unique identifier of the Epic. Must be a valid 64-bit integer. |
No output schema declared.
No examples provided.
get_file Get File ~45
Retrieve detailed information about a specific uploaded file using its unique public identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| file-public-id | string | yes | The unique identifier for the file, provided as a 64-bit integer. |
No output schema declared.
No examples provided.
get_group Get Group ~48
Retrieve detailed information about a specific group using its unique public identifier. Returns the group's metadata and configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| group-public-id | string | yes | The unique identifier of the group, formatted as a UUID. |
No output schema declared.
No examples provided.
get_iteration Get Iteration ~69
Retrieve detailed information about a specific iteration by its public ID. Use this to fetch iteration metadata, status, and associated data.
| Name | Type | Req | Description |
|---|---|---|---|
| iteration-public-id | string | yes | The unique identifier for the iteration as a 64-bit integer. This ID is used to look up and retrieve the specific iteration's details. |
No output schema declared.
No examples provided.
get_key_result Get Key Result ~56
Retrieve detailed information about a specific Key Result by its unique identifier. Returns the Key Result's properties and current state.
| Name | Type | Req | Description |
|---|---|---|---|
| key-result-public-id | string | yes | The unique identifier of the Key Result to retrieve, formatted as a UUID. |
No output schema declared.
No examples provided.
What is the com.mcparmory/shortcut MCP server?
com.mcparmory/shortcut is an MCP server listed in the public MCP registry as com.mcparmory/shortcut. Track stories, organize sprints, and manage project workflows across your team. This page covers its PyPI package (mcparmory-shortcut).
Is the com.mcparmory/shortcut MCP server safe to use?
com.mcparmory/shortcut scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mcparmory/shortcut MCP server expose?
com.mcparmory/shortcut exposes 131 tools: list_categories, create_category, get_category, update_category, delete_category, and 126 more. Their descriptions and schemas cost roughly 15,239 tokens of context every time the server is loaded.
Is the com.mcparmory/shortcut MCP server still maintained?
com.mcparmory/shortcut is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.