Use Cursor as a local coding runner or connect the editor to Stellary MCP so project context, card actions, and execution stay tied to the same workspace.
Cursor
Connected
Stellary
Launch workspace
Cursor Agent can run locally through Stellary Desktop. Cursor can also connect to the remote MCP endpoint for project tools and context.
01
Install Cursor and make the agent runner available on the target machine.
02
Detect Cursor Agent in Stellary Desktop or add the MCP endpoint in Cursor.
03
Link the repository and choose the project or agent identity.
04
Launch a card mission or call allowed Stellary MCP tools.
05
Keep the project status and result visible outside the editor.
Mission STL-128
Install Cursor and make the agent runner available on the target machine.
Checklist
Linked context
Execute eligible missions on the connected machine in the linked repository.
Cursor remains the coding surface while Stellary carries the project card, context, assignment, control policy, and team-facing trace.
Execute eligible missions on the connected machine in the linked repository.
Inspect and update authorized Stellary projects directly from a compatible Cursor MCP client.
Keep questions, results, and next actions attached to the original card.
{
"mcpServers": {
"stellary": {
"url": "https://api.stellary.co/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
}
}
}
}When the card requires repository work, configure an agent with local execution and select a compatible Cursor Agent target. The connected machine must expose the runner and the project must point to the correct local Git folder.
The board remains the entry point for scope and status; Cursor remains the environment where code work happens.
The remote MCP server lets Cursor inspect live project data without duplicating it into editor notes. A human token acts as the signed-in user, while an agent token keeps its own tool restrictions and autonomy policy.
Start with discovery tools, then reuse exact project and card IDs for durable actions.
Local Agent runner
Cursor MCP client
Purpose
Local Agent runner
Modify files in the project repository.
Cursor MCP client
Read or update Stellary workspace objects.
Host
Local Agent runner
Connected desktop machine.
Cursor MCP client
Cursor environment with remote MCP support.
Project scope
Local Agent runner
Linked local repository.
Cursor MCP client
Token permissions and exact project IDs.
Typical start
Local Agent runner
Run mission from a card.
Cursor MCP client
List projects, cards, or documents.
Yes, when Cursor Agent is available as a local runner, the project has a linked repository, and the assigned Stellary agent uses that execution target.
No. MCP exposes workspace tools to Cursor. The local runner executes agent missions on the connected machine and can work inside the linked repository.
Use a personal access token for interactive work as yourself. Use an agent token when Cursor represents a dedicated workspace agent with controlled tools and autonomy.
The local runner uses the repository on the connected machine. The repository link identifies the working folder for the project; local execution does not require turning the repository into a second project database.
Choose the local runner for repository work or MCP for live workspace tools.
Start with Stellary