Bring live Stellary projects, cards, documents, and controlled actions into Claude Desktop without copying the workspace into a separate conversation.
Claude Desktop
Connected
Stellary
Launch workspace
The remote MCP endpoint gives Claude Desktop a tool surface backed by the caller identity and the current Stellary project permissions.
01
Issue a personal access token for interactive use as yourself.
02
Add the Stellary Streamable HTTP endpoint and authorization header.
03
Start by listing accessible projects before selecting exact IDs.
04
Read documents, inspect cards, and call the tools your identity may use.
05
Confirm that every write reached the expected project object.
Mission STL-128
Issue a personal access token for interactive use as yourself.
Checklist
Linked context
Query the current workspace instead of pasting a stale export into the conversation.
Claude Desktop can reason with real cards and documents while Stellary remains the source of truth for access, actions, and the resulting project state.
Query the current workspace instead of pasting a stale export into the conversation.
A personal access token keeps the same workspace and project boundaries as the person using it.
Tool results identify the project action so the user can reopen and inspect it in Stellary.
{
"mcpServers": {
"stellary": {
"url": "https://api.stellary.co/mcp",
"headers": {
"Authorization": "Bearer YOUR_PERSONAL_ACCESS_TOKEN"
}
}
}
}Claude Desktop normally represents the person asking questions. A personal access token gives the client stable authentication while preserving that user’s workspace and project permissions.
Do not use the transport-only MCP_TOKEN when the tools need a resolved user or workspace agent identity.
List the accessible projects and cards before asking Claude to act. Exact identifiers avoid fuzzy name matching and make long-lived workflows safer.
After a write, reopen the card, document, or cockpit item in Stellary to verify the real source of truth changed as expected.
Pasted project context
Stellary MCP
Freshness
Pasted project context
Accurate only when copied.
Stellary MCP
Reads the current project state.
Scope
Pasted project context
Whatever the user included.
Stellary MCP
Workspace and project permissions apply.
Actions
Pasted project context
Suggestions copied back manually.
Stellary MCP
Allowed tools can update the source system.
Verification
Pasted project context
Conversation is the only trace.
Stellary MCP
The resulting project object remains inspectable.
No for MCP access. Claude Desktop connects to the remote Stellary endpoint. Stellary Desktop is only needed for local runners and repositories on your machine.
Yes, if the personal access token belongs to a user with the required project permission and the selected MCP tool permits that action.
Yes for a dedicated external agent workflow. That changes the identity and causes writes to follow the configured agent tool policy and autonomy mode.
Stellary uses a stateless Streamable HTTP transport and creates a fresh transport for each request, so clients do not need to preserve a Stellary MCP session identifier.
Create a personal access token, connect the endpoint, and begin with project discovery.
Create a Stellary workspace