{
  "markdown": "# Stellary Project Management MCP Server\n\n[![Validate MCP listing](https://github.com/Anymfah/stellary-mcp/actions/workflows/validate.yml/badge.svg)](https://github.com/Anymfah/stellary-mcp/actions/workflows/validate.yml)\n[![MCP Registry](https://img.shields.io/badge/MCP-Official%20Registry-7c6cff)](https://registry.modelcontextprotocol.io/v0.1/servers/io.github.Anymfah%2Fstellary-project-management/versions/latest)\n[![MCP Badge](https://lobehub.com/badge/mcp/anymfah-stellary-mcp)](https://lobehub.com/mcp/anymfah-stellary-mcp)\n[![stellary-mcp MCP server](https://glama.ai/mcp/servers/Anymfah/stellary-mcp/badges/card.svg)](https://glama.ai/mcp/servers/Anymfah/stellary-mcp)\n[![stellary-mcp MCP server](https://glama.ai/mcp/servers/Anymfah/stellary-mcp/badges/score.svg)](https://glama.ai/mcp/servers/Anymfah/stellary-mcp)\n\nConnect AI assistants and coding agents to live Stellary projects through the\nModel Context Protocol (MCP). The hosted server exposes project, board,\ncollaboration, cockpit, and agent-mission tools while preserving Stellary's\nexisting permissions.\n\n- **Endpoint:** `https://api.stellary.co/mcp`\n- **Transport:** Streamable HTTP\n- **Authentication:** OAuth 2.1 with PKCE and refresh-token rotation; bearer PATs remain supported for compatibility\n\n[Official MCP Registry listing](https://registry.modelcontextprotocol.io/v0.1/servers/io.github.Anymfah%2Fstellary-project-management/versions/latest) ·\n[Documentation](https://stellary.co/docs/mcp/) ·\n[Guide en français](README.fr.md)\n\n## What you can do\n\n- Discover projects, columns, cards, documents, and cockpit state.\n- Create and update cards, move work, assign teammates, and add comments.\n- Inspect sprints, priorities, agent status, and pending proposals.\n- Run governed agent missions with workspace rules and approval policies.\n- Use installed workspace integrations from eligible agent sessions.\n\nAn OAuth connection can authorize **Me**, one or more active workspace agents,\nor both. The exact tool list is resolved at connection time and checked again\nfor the identity selected on every call. It depends on OAuth scopes, project\naccess, workspace configuration, and each agent's tool and autonomy policies.\n\n## Connect in three steps\n\n1. Add the hosted endpoint to an OAuth-capable MCP client.\n2. Sign in to Stellary in the browser window opened by the client.\n3. Choose a workspace and authorize **Me**, one or more active agents, or both.\n\n### Claude Code\n\n```bash\nclaude mcp add stellary \\\n  --transport streamable-http \\\n  https://api.stellary.co/mcp\n```\n\n### Cursor and JSON-based clients\n\n```json\n{\n  \"mcpServers\": {\n    \"stellary\": {\n      \"url\": \"https://api.stellary.co/mcp\"\n    }\n  }\n}\n```\n\nA reusable example is available in\n[`examples/mcp-client.json`](examples/mcp-client.json).\n\nClients without remote OAuth support can still use a dedicated personal access\ntoken from **Account settings → API tokens** as an `Authorization: Bearer`\nheader. Start with read-only scopes and add write scopes only when required.\n\n## Recommended first request\n\nAsk the client to list your Stellary projects. This confirms authentication and\nproject visibility without changing data. Then ask it to inspect one project's\ncolumns and cards before enabling write scopes.\n\n## Security\n\n- Revoke an OAuth connection from **Workspace settings → MCP connections** when\n  a client should no longer have access.\n- Treat compatibility PATs like passwords and never commit one to a repository.\n- Start with read-only scopes and use an expiry date when a PAT is required.\n- All requests are still subject to Stellary permissions and rate limits.\n- Stellary never sends the client the private tokens attached to your agents.\n\nFor a vulnerability, follow [SECURITY.md](SECURITY.md). For setup questions,\nemail [support@stellary.co](mailto:support@stellary.co).\n\n## Agent directory manifests\n\nThis repository is also the public discovery source for agent plugin\ndirectories. OAuth-capable surfaces point at the hosted Streamable HTTP endpoint\nwithout embedding a secret. Legacy PAT configuration remains documented for\nclients that cannot complete remote OAuth. None starts a local stdio/`npx`\nserver.\n\n| Surface | Files |\n| --- | --- |\n| cursor.directory / Open Plugins | [`.mcp.json`](.mcp.json) |\n| Cursor Marketplace | [`.cursor-plugin/plugin.json`](.cursor-plugin/plugin.json), [`mcp.json`](mcp.json) |\n| Claude Code Plugin Directory | [`.claude-plugin/plugin.json`](.claude-plugin/plugin.json), [`.claude-plugin/marketplace.json`](.claude-plugin/marketplace.json), [`.mcp.json`](.mcp.json) |\n| Gemini CLI Extensions | [`gemini-extension.json`](gemini-extension.json) |\n| skills.sh / ClawHub | [`SKILL.md`](SKILL.md) (`npx skills add Anymfah/stellary-mcp`) |\n| Grok Build | [`.grok-plugin/plugin.json`](.grok-plugin/plugin.json) |\n| GitHub Copilot / Agent Plugins | [`plugin.json`](plugin.json) |\n| OpenAI Plugins / Codex | [`plugins/stellary/.codex-plugin/plugin.json`](plugins/stellary/.codex-plugin/plugin.json), [`plugins/stellary/.mcp.json`](plugins/stellary/.mcp.json) |\n\nOnly set `STELLARY_TOKEN` when a client cannot use OAuth. Never commit a real\ntoken. A 400×400 listing icon is in\n[`assets/logo-400.png`](assets/logo-400.png).\n\n## About this repository\n\nThis public repository is the canonical discovery and configuration source for\nStellary's hosted MCP server. It contains the official MCP Registry manifest,\nclient examples, documentation, and automated availability checks. The hosted\nStellary application and server implementation are not distributed from this\nrepository.\n\nThin plugin manifests for Grok Build and GitHub Copilot live in\n[`.mcp.json`](.mcp.json), [`.grok-plugin/plugin.json`](.grok-plugin/plugin.json),\nand [`plugin.json`](plugin.json). They point at the hosted endpoint\n`https://api.stellary.co/mcp` (Streamable HTTP with OAuth, plus PAT\ncompatibility). A 400×400 listing icon is in\n[`assets/logo-400.png`](assets/logo-400.png).\n\nThe metadata and documentation in this repository are licensed under the MIT\nLicense. Use of the hosted service is governed by the\n[Stellary terms](https://stellary.co/terms/).\n",
  "bytes": 6115,
  "sha": "bfa074a3d5c3897cfcd01e0b6eb237278f0d3fce995e40200ed70e5395a3a495",
  "repo_slug": "anymfah/stellary-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_anymfah_stellary_project_manag_d0382d61/readme"
}