{
  "markdown": "# keelen-mcp\n\n**Steer Keelen, the AI coding agent for GitHub, from your chat.**\n\nBuild apps and internal tools, or keep a defined backlog moving with the\napproval and merge controls you choose. Keelen turns requests into a standing\nroadmap, plans tasks, runs checks and opens pull requests in your repository.\n\nPaste [SETUP.md](SETUP.md) into a compatible MCP client and say **\"set me up.\"**\nYour agent guides account setup and project creation. You confirm your email\nand complete AI credential connection, GitHub approval and any billing steps\nin the browser. Once connected, use chat to submit requests, set priorities\nand answer questions about the work.\n\nUse your own supported **AI subscription or API key** with Claude Code,\nCodex, GLM, Kimi or Grok. Keelen adds no markup to AI usage.\n[See how the MCP workflow works](https://keelen.ai/mcp-server/?utm_source=mcp-server&utm_medium=github-readme&utm_campaign=readme).\n\nThis repo is documentation only. It describes the hosted [Model Context\nProtocol](https://modelcontextprotocol.io) (MCP) server at\n`https://keelen.ai/mcp`. Keelen runs the coding workflow as a hosted service;\nthis repository contains its documentation and client configuration examples.\n\n![Recorded Keelen MCP setup walkthrough](keelen-setmeup.gif)\n\nThe recording shows an earlier setup flow. Follow the current instructions\nbelow for account verification and browser approvals.\n\n## Work you can hand over\n\n- Build an app or progress the fixes, tests and small features on a solo\n  project's roadmap.\n- Build an internal request portal, reporting dashboard or integration while\n  you focus on your main work. Deployment, colleague sign in and access rules\n  belong to the software you build and the hosting you choose.\n- Queue defined work for a team or client repository, including outside\n  staffed hours, then review the resulting pull requests and decisions.\n- Run Security, Legal and Controls reviews, triage findings and send selected\n  code work into the roadmap. These are bounded reviews, not penetration\n  tests, legal advice or certification. Repeated reviews can be triggered\n  through MCP by your own agent or external scheduler; Keelen has no built in\n  scan scheduler.\n\nThese are example uses, not customer deployments or ready made templates.\nYou set priorities and choose plan approval, manual merge or other supported\ncontrols for each project. Keelen checks changes before they can merge and\nholds failed checks. Capacity, provider limits, missing information and\ndecisions can pause progress; a queue is not a promise of finished work by a\nparticular time.\n\n## AI engines and credentials\n\nConnect credentials in the Keelen dashboard, never in the MCP chat. The\nworkspace API key used by your MCP client is separate from these credentials.\n\n| AI engine | Supported connection |\n| --- | --- |\n| Claude Code | Claude Pro or Max sign in, or an Anthropic API key |\n| Codex | ChatGPT sign in, or an OpenAI API key |\n| GLM | Z.ai API key |\n| Kimi | Kimi Code membership key or Moonshot Open Platform API key |\n| Grok | SuperGrok sign in or xAI API key |\n\nEngine availability can differ by role. Grok here means the coding engine;\nit does not establish Grok Bot compatibility as an MCP client. OpenRouter\nis currently limited to Keelen's own test and benchmark projects and is not\nenabled for customer repositories.\n\n## Connect and set up\n\nFor Claude Code, connect the server without a token, then hand your agent\nthe setup instructions:\n\n```\nclaude mcp add --transport http keelen https://keelen.ai/mcp\n```\n\nThen paste the contents of [`SETUP.md`](SETUP.md) into your agent and say\n**\"set me up\"**. It will ask for your email and the verification code that\nlands in your inbox. It then guides you through connecting an AI engine,\napproving GitHub access, creating or importing a project, and provisioning.\nFollow the dashboard links for the steps that require your browser.\n\nThe whole flow on one page, with the 50-second demo:\n<https://keelen.ai/mcp-server/?utm_source=mcp-server&utm_medium=github-readme&utm_campaign=setup>\n\nUsing a different client? See the per-client guides:\n\n- [Claude Code](clients/claude-code.md)\n- [Claude Desktop](clients/claude-desktop.md)\n- [Codex](clients/codex.md)\n- [Cursor](clients/cursor.md)\n- [Windsurf](clients/windsurf.md)\n- [Generic / other MCP clients](clients/generic.md)\n\nBuilding a Roblox game? Keelen can generate art, audio, meshes, skyboxes, and\nanimated characters from plain-language requests — see\n[`roblox-assets.md`](roblox-assets.md).\n\n## Tools (abbreviated)\n\nThe server exposes 41 tools. Two work with no key at all (`signup`,\n`verify_email`); the rest need the bearer key `verify_email` gives you. Full\nreference with parameters and behavior: [`TOOLS.md`](TOOLS.md).\n\n| Group | Tools |\n| --- | --- |\n| Getting started | `signup`, `verify_email` |\n| Onboarding | `get_onboarding_status`, `open_dashboard`, `connect_github`, `list_github_repos`, `import_project`, `get_provisioning_status`, `get_billing` |\n| Projects & roadmap | `list_projects`, `create_project`, `archive_project`, `delete_project`, `submit_request`, `get_request_status`, `answer_request`, `refine_request`, `set_product_vision`, `set_product_goal`, `get_product_vision`, `get_product_goal`, `list_roadmap`, `reorder_roadmap`, `cancel_roadmap_item`, `clear_horizon_pin`, `project_status`, `list_escalations`, `resolve_escalation`, `retry_blocked_task`, `rearm_roadmap_item`, `resolve_platform_policy_conflict`, `replan_task`, `close_task`, `control_scheduler`, `set_ui_review_scenario_cap`, `rollback_roblox_place` |\n| Reviews | `run_security_review`, `run_legal_exposure_review`, `get_legal_exposure_findings`, `run_control_gap_review`, `get_control_gap_findings` |\n\nThe server speaks MCP protocol revision `2026-07-28` as well as the earlier\nhandshake revisions, from the same endpoint — no client action is required\neither way. Details in [`clients/generic.md`](clients/generic.md#protocol-support);\nnotable contract changes are recorded in [`CHANGELOG.md`](CHANGELOG.md).\n\n[`PORTFOLIO.md`](PORTFOLIO.md) documents the separate portfolio surface,\nwhich is not generally available. Its scoped OAuth interface is distinct\nfrom the primary MCP server described here.\n\n## FAQ\n\n**Is my code touched before I agree to anything?** No. Connecting the MCP\nserver tokenless only lets you sign up and verify your email — it can't see,\nread, or modify any repository. `connect_github` requires an explicit\nGitHub App install you approve in your browser, and every following build\nruns inside an isolated per-tenant sandbox scoped to your own workspace.\n\n**What does it cost?** Signing up, connecting GitHub, and creating a project\nare all free. Actually running the autonomous loop (compute) requires an\nactive subscription — `get_billing()` returns a Stripe checkout link the\nmoment you're ready. A free/unpaid workspace can do everything up through\nproject creation. Work can start once billing is active,\nthe project's loop is enabled and its setup requirements are satisfied.\n\n**How do I revoke access?** Every key minted through this flow (or the\ndashboard) can be individually revoked. Go to your Keelen dashboard →\n**Settings → API keys** and delete the key. Revoking takes effect\nimmediately; your agent will need a fresh key (rerun the signup flow, or\nmint a new one from the dashboard) to keep calling the server.\n\nSee [`SECURITY.md`](SECURITY.md) for the full security model: what the MCP\nserver can and can't reach, rate limits, and key handling.\n\n## Support\n\nQuestions or issues: **support@keelen.ai**\n",
  "bytes": 7565,
  "sha": "5d88a3272c9b11fb6572dcf8c720c5c1ce6643f30a7496109c206822a0f5095b",
  "repo_slug": "jamie7893/keelen-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_jamie7893_keelen_e4956b46/readme"
}