Zurück zum Blog
Updates

SPSX Import, New MCP Tools, and Bitbucket Update

Import Spedy Selection Packages directly into new tickets, use new MCP tools for subtickets and ticket links, get started faster with streamlined onboarding, and connect Bitbucket with Atlassian API tokens.

Spedy Team3 min readAuf Deutsch lesen
SPSX Import, New MCP Tools, and Bitbucket Update
#spsx#import#mcp#subtickets#ticket-links#onboarding#bitbucket#integrations

Four updates in this release: SPSX import brings structured selections directly into the ticket creation flow, seven new MCP tools let you work with subtickets and ticket links from Claude, Cursor & friends, onboarding is leaner, and the Bitbucket integration now uses Atlassian API tokens.


SPSX Import: Bring Selection Packages into Tickets

Spedy now supports importing Spedy Selection Packages (.spsx) when creating new tickets. An SPSX file contains structured selections, screenshots, and comments -- for example, from a browser extension session.

How the import works

  1. Open the Create Ticket dialog
  2. Drag a .spsx file into the import zone or click Import .spsx
  3. Spedy parses the package and automatically fills in title, description, and priority
  4. A compact preview shows the imported selections with screenshots and comments
  5. Adjust the pre-filled fields as needed and create the ticket
  6. The original SPSX file is automatically attached to the ticket

The import zone accepts both drag-and-drop and file selection. A loading indicator shows progress during parsing. You can remove an imported package at any time before creating the ticket.


The Spedy MCP server now includes seven new tools. You can work with subtickets and ticket links directly from Claude Desktop, Cursor, or any other MCP-compatible tool.

Subticket tools

Tool What it does
tickets_create_subticket Create a child ticket under a parent ticket
tickets_list_subtickets List all subtickets of a ticket
tickets_convert_to_subticket Convert a standalone ticket into a subticket
tickets_promote_to_standalone Detach a subticket from its parent
Tool What it does
tickets_create_link Create a link between two tickets (Blocks, Is blocked by, Relates to, Duplicates)
tickets_list_links List all links of a ticket
tickets_delete_link Delete a ticket link

All new tools accept both the display ID (e.g. AG-12) and the UUID -- no extra lookup steps needed. The board is resolved automatically from the ticket.


Streamlined Onboarding

The onboarding wizard now takes new users to their first board in 4 steps instead of 6:

Step What happens
Welcome Greeting and overview
Create Board Set up your first project board
Choose Plan Pick Pro Trial or Starter
Done Quick intro to next steps

The previous steps for agents, team invitations, and feature configuration have been removed. You invite team members via Settings → Members when you're ready.


Bitbucket: Atlassian API Tokens

Atlassian has retired the legacy App Passwords for Bitbucket. The Bitbucket integration in Spedy now uses Atlassian API tokens with scopes.

New setup flow

  1. Go to id.atlassian.com and create an API token with scopes (not the legacy scopeless format)
  2. Select your Bitbucket workspace
  3. Grant the required scopes:
    • Read: read:repository, read:webhook, read:user, read:pullrequest, read:workspace
    • Write: write:repository, write:webhook, write:pullrequest
    • Delete: delete:webhook
  4. In Spedy under Settings → Integrations → Bitbucket: use your Atlassian account email (not your Bitbucket username) and the new API token

If your existing Bitbucket integration is working, you don't need to change anything. Only use the new flow when setting up a new connection or when your token has expired.


New Priority Icons

Priority icons in ticket lists and on the board now show ascending bars instead of the previous arrow symbols:

  • Low: 1 bar
  • Medium: 2 bars
  • High: 3 bars
  • Critical: Alert icon

Priority is now immediately recognisable at a glance, even in compact list views.


Kanban: Cleaner Ticket Cards

The kanban board no longer shows the status directly on ticket cards. The column itself already indicates the status -- the additional display was redundant. The status remains visible in dashboard and list views.

Frequently asked questions

Quick answers to the most common questions about this topic.

What is an SPSX file?
A Spedy Selection Package (.spsx) is a ZIP archive containing structured selections, screenshots, and comments. It is created by tools like the Spedy Browser Extension and can be imported directly when creating a ticket.
Where do I import an SPSX file?
In the Create Ticket dialog. You'll find an import zone where you can drag and drop the .spsx file or select it via the button.
What new MCP tools are available?
Seven new tools: create, list, convert, and promote subtickets, plus create, list, and delete ticket links. All accept either a display ID (e.g. AG-12) or UUID.
Do I need to reconnect my Bitbucket integration?
Only if you're still using a legacy App Password. Atlassian has retired App Passwords. Create an Atlassian API token with scopes at id.atlassian.com and reconnect.
What changed in the onboarding?
The wizard now has 4 steps instead of 6: Welcome → Create Board → Choose Plan → Done. You invite team members afterwards via Settings → Members.
SPSX Import, New MCP Tools, and Bitbucket Update | Spedy Blog