Issue-to-code context
Retrieve ticket requirements and repository context without manually moving information between tools.
LinearGitHub
CURSOR + WORKING MACHINES
Cursor integrations for engineering work through MCP
Working Machines provides Cursor integrations for external engineering software through a single remote MCP endpoint. Cursor can discover app actions when a task needs them, while Working Machines manages connection identity, provider authorization, policy checks, and action execution.
The connection begins with a compact discovery surface rather than the full catalog. Cursor loads the action contract it needs, operates through a named account connection, and receives a structured response. Working Machines applies authorization and action policy at execution time, outside the prompt.
REAL WORK ACROSS APPLICATIONS
Work across apps, not inside them.
Error-driven development
Search production failures, inspect related deployments, and turn findings into a concrete engineering task.
SentryGitHubLinear
Team handoff
Update the project record and publish an accurate summary after implementation work completes.
LinearSlackNotion
CAPABILITY LAYER
Give Cursor capabilities, not credentials.
Context retrieval
- Find relevant issues and incidents
- Inspect repository metadata
- Retrieve deployment context
Project updates
- Create and update work items
- Attach technical summaries
- Notify collaborators
Controlled access
- Use named connections
- Limit allowed actions
- Keep provider secrets outside Cursor
SETUP
Connect in five steps.
- 01Add the Working Machines server URL to Cursor's MCP settings.
- 02Finish authorization in the browser.
- 03Connect the applications used by the project.
- 04Confirm the actions exposed to the agent match the intended workflow.
- 05Run a discovery query and inspect the selected action before execution.
BOUNDARIES
What to consider.
- Keep action permissions aligned with each repository and team environment.
- Review write operations that create external side effects such as issues, messages, or deployments.
- Tool output becomes part of the active agent interaction and is not inherently anonymized.
ONE CONNECTION. REAL WORK.
Give your agent software it can use.
Connect through MCP or explore the Agent App catalog and choose only the capabilities your workflow needs.