Read stories, search one explicit page of stories, and inspect workflows in your Shortcut workspace. Uses your own API token; no story writes or managed OAuth.
What you can do (3)
What you can do
Available commands: 3 (3 read, 0 write). Enable only the commands your application needs.
| Command | Effect |
|---|---|
Search stories — shortcut.stories.search |
Read |
Get story — shortcut.stories.get |
Read |
List workflows — shortcut.workflows.list |
Read |
Connect and use
Open the integration's connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.
Get your provider credentials
Follow these steps for Shortcut, then enter the issued values in the connection form below.
- In Shortcut, open Settings → Account → API Tokens and generate a token for your own account. Shortcut tokens inherit your account permissions; use a dedicated account with only the workspace access you need. In Tooluse.net, open Tools → Shortcut → Connect and paste the token into “Shortcut API token”, then save. Enable the needed commands on an Tooluse.net API key and give that key to your client. This integration reads story metadata and workflows; search returns one page with nextToken for an explicit next call. It does not write stories, and managed OAuth is not implemented. Revoke or rotate the token in Shortcut and replace it in the saved connection.
Where to enter credentials
In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.
| Connection field | Requirement |
|---|---|
| Shortcut API token | Required |
Open API keys and create a Tooluse.net key for the enabled commands.
Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.
Configure Claude Code, Codex or Cursor once
Permissions and results
If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.
Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.
Call from your client
Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.
Configure Claude Code, Codex or Cursor once
Discover your enabled tools
List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.
curl 'https://api.tooluse.net/v1/tools' \
-H "Authorization: Bearer $TOOLUSE_API_KEY"
Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.
HTTP call
curl 'https://api.tooluse.net/v1/tool-calls' \
-H "Authorization: Bearer $TOOLUSE_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: replace-with-a-new-call-id' \
--data '{
"type": "tool_use",
"id": "toolu_example",
"name": "svc_FROM_YOUR_TOOL_LIST",
"input": {
"query": {
"query": "is:unstarted",
"page_size": 20
}
}
}'
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Commands
Search stories — shortcut.stories.search
Search one explicit page of Shortcut stories with slim provider results. Returns safe story metadata, total and nextToken. Pass nextToken as query.next with the same query and page_size; no automatic pagination. The provider exposes only the first 1,000 matches.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
query |
object | Required | additionalProperties: false |
|
query.query |
string | Required | Shortcut search expression. See the official search operators guide. | minLength: 1; maxLength: 4096 |
query.page_size |
integer | Required | Number of results in this page, from 1 to 250. | minimum: 1; maximum: 250 |
query.next |
string | Optional | Opaque nextToken returned by the previous response. Keep query and page_size unchanged. | minLength: 1; maxLength: 4096 |
Full JSON Schema
Example input
{
"query": {
"query": "is:unstarted",
"page_size": 20
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Get story — shortcut.stories.get
Read safe metadata for one Shortcut story by numeric story ID. Descriptions, comments, tasks and private custom fields are omitted.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
path |
object | Required | additionalProperties: false |
|
path.story-public-id |
integer | Required | Positive numeric Shortcut story ID. | minimum: 1; maximum: 9007199254740991 |
Full JSON Schema
Example input
{
"path": {
"story-public-id": 123
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
List workflows — shortcut.workflows.list
List workspace workflow IDs, names and state IDs, names and types. This provider endpoint has no pagination; one bounded response is returned.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
This tool has no input parameters.
Full JSON Schema
Example input
{}
At most 1 provider requests per invocation; timeout: 30 seconds.
Errors
Check the key's expiry, revocation, workspace and allowed operations.
Reuse the same idempotency key only for the same request.
The connection or provider limit has been reached. Check the receipt before retrying.
Test the connection
Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.