Stellary Project Management MCP Server

Stellary Project Management MCP Server

Connect AI assistants and coding agents to live Stellary projects through the Model Context Protocol (MCP). The hosted server exposes project, board, collaboration, cockpit, and agent-mission tools while preserving Stellary's existing permissions.

• Endpoint: https://api.stellary.co/mcp
• Transport: Streamable HTTP
• Authentication: OAuth 2.1 with PKCE and refresh-token rotation; bearer PATs remain supported for compatibility

Official MCP Registry listing · Documentation · Guide en français

What you can do

• Discover projects, columns, cards, documents, and cockpit state.
• Create and update cards, move work, assign teammates, and add comments.
• Inspect sprints, priorities, agent status, and pending proposals.
• Run governed agent missions with workspace rules and approval policies.
• Use installed workspace integrations from eligible agent sessions.

An OAuth connection can authorize Me, one or more active workspace agents, or both. The exact tool list is resolved at connection time and checked again for the identity selected on every call. It depends on OAuth scopes, project access, workspace configuration, and each agent's tool and autonomy policies.

Connect in three steps

1. Add the hosted endpoint to an OAuth-capable MCP client.
2. Sign in to Stellary in the browser window opened by the client.
3. Choose a workspace and authorize Me, one or more active agents, or both.

Claude Code

claude mcp add stellary \
  --transport streamable-http \
  https://api.stellary.co/mcp

Cursor and JSON-based clients

{
  "mcpServers": {
    "stellary": {
      "url": "https://api.stellary.co/mcp"
    }
  }
}

A reusable example is available in examples/mcp-client.json. Marketplace install and PAT fallback scopes are documented below.

Install from the Cursor Marketplace

This repository is the Cursor Plugin wrapper for the hosted Streamable HTTP endpoint. It does not start a local stdio or npx server.

1. Open Customize in Cursor and install Stellary from the Cursor Marketplace once the listing is live (submission: publish form).
2. Complete the Stellary OAuth window. Choose a workspace and authorize Me, one or more active agents, or both.
3. Ask Cursor to list your Stellary projects.

Until the listing is public, symlink this repo into ~/.cursor/plugins/local/stellary or add the same hosted URL to Cursor MCP settings / ~/.cursor/mcp.json:

{
  "mcpServers": {
    "stellary": {
      "url": "https://api.stellary.co/mcp"
    }
  }
}

Cursor discovers OAuth from Stellary metadata. The Marketplace package therefore ships no Bearer header and no ${STELLARY_TOKEN} placeholder.

Compatibility PAT (only if OAuth cannot complete)

Create a dedicated token from Account settings → API tokens. Start with projects:read and pilotage:read. Add write scopes only when the client needs them. Keep the secret in user MCP settings — never in this repository:

{
  "mcpServers": {
    "stellary": {
      "url": "https://api.stellary.co/mcp",
      "headers": {
        "Authorization": "Bearer ${env:STELLARY_TOKEN}"
      }
    }
  }
}

The publish checklist for [email protected] / the publish form is in CURSOR_SUBMISSION.md.

Recommended first request

Ask the client to list your Stellary projects. This confirms authentication and project visibility without changing data. Then ask it to inspect one project's columns and cards before enabling write scopes.

Security

• Revoke an OAuth connection from Workspace settings → MCP connections when a client should no longer have access.
• Treat compatibility PATs like passwords and never commit one to a repository.
• Start with read-only scopes and use an expiry date when a PAT is required.
• All requests are still subject to Stellary permissions and rate limits.
• Stellary never sends the client the private tokens attached to your agents.

For a vulnerability, follow SECURITY.md. For setup questions, email [email protected].

Agent directory manifests

This repository is also the public discovery source for agent plugin directories. OAuth-capable surfaces point at the hosted Streamable HTTP endpoint without embedding a secret. Legacy PAT configuration remains documented for clients that cannot complete remote OAuth. None starts a local stdio/npx server.

Surface	Files
cursor.directory / Open Plugins	.mcp.json
Cursor Marketplace	.cursor-plugin/plugin.json, mcp.json, skills/stellary/SKILL.md, CURSOR_SUBMISSION.md
Claude Code Plugin Directory	.claude-plugin/plugin.json, .claude-plugin/marketplace.json, .mcp.json
Gemini CLI Extensions	gemini-extension.json
skills.sh / ClawHub	SKILL.md (npx skills add Anymfah/stellary-mcp)
Grok Build	.grok-plugin/plugin.json
GitHub Copilot / Agent Plugins	plugin.json
OpenAI Plugins / Codex	plugins/stellary/.codex-plugin/plugin.json, plugins/stellary/.mcp.json

Only set STELLARY_TOKEN when a client cannot use OAuth. Never commit a real token. A 400×400 listing icon is in assets/logo-400.png.

About this repository

This public repository is the canonical discovery and configuration source for Stellary's hosted MCP server. It contains the official MCP Registry manifest, client examples, documentation, and automated availability checks. The hosted Stellary application and server implementation are not distributed from this repository.

Thin plugin manifests for Grok Build and GitHub Copilot live in .mcp.json, .grok-plugin/plugin.json, and plugin.json. They point at the hosted endpoint https://api.stellary.co/mcp (Streamable HTTP with OAuth, plus PAT compatibility). A 400×400 listing icon is in assets/logo-400.png.

The metadata and documentation in this repository are licensed under the MIT License. Use of the hosted service is governed by the Stellary terms.