Skip to content

Cursor Project Management with Stellary MCP

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.

Connect CursorOpen the MCP guide
Cursor Agent · local and MCP access

Cursor

Connected

Stellary

Launch workspace

Ready
Project context
Prepare release mission
Activity
Identity, project, and tools remain scoped

Choose repository execution or workspace access

Cursor Agent can run locally through Stellary Desktop. Cursor can also connect to the remote MCP endpoint for project tools and context.

  1. 01

    Prepare

    Install Cursor and make the agent runner available on the target machine.

  2. 02

    Connect

    Detect Cursor Agent in Stellary Desktop or add the MCP endpoint in Cursor.

  3. 03

    Scope

    Link the repository and choose the project or agent identity.

  4. 04

    Execute

    Launch a card mission or call allowed Stellary MCP tools.

  5. 05

    Return

    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.

Running

Checklist

Connect
Scope
Execute

Linked context

project-brief.md

Execute eligible missions on the connected machine in the linked repository.

Run mission

Editor execution, shared project state

Cursor remains the coding surface while Stellary carries the project card, context, assignment, control policy, and team-facing trace.

Cursor Agent runner

Execute eligible missions on the connected machine in the linked repository.

Remote MCP tools

Inspect and update authorized Stellary projects directly from a compatible Cursor MCP client.

Project-level continuity

Keep questions, results, and next actions attached to the original card.

Cursor MCP configuration

JSON
{
  "mcpServers": {
    "stellary": {
      "url": "https://api.stellary.co/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

Run code missions through Stellary Desktop

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.

Use MCP for project-aware editor actions

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.

Cursor Agent runner or Cursor MCP?

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.

Questions about Cursor and Stellary

Can Cursor Agent work directly from a Stellary card?

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.

Is the MCP connection the same as the local runner?

No. MCP exposes workspace tools to Cursor. The local runner executes agent missions on the connected machine and can work inside the linked repository.

Which token should Cursor use for MCP?

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.

Does Stellary copy the repository to the cloud?

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.

Continue the setup

MCP documentationConfigure tokens, transport, tools, and approval behavior.Local AI appsConnect Cursor Agent and link the working repository.AI Kanban boardKeep Cursor missions visible from card to review.

Connect Cursor to the project system

Choose the local runner for repository work or MCP for live workspace tools.

Start with Stellary