Keelen

What Keelen does

Keelen turns requests about a GitHub project into managed development work. You can create a new repository with a supported project scaffold, import an existing repository, submit feature or bug-fix requests, and define the product vision and current goal that guide later planning.

The workflow maintains a roadmap, expands queued items into tasks, runs coding and verification work, and opens pull requests for review. Project status reports lifecycle state, active work, queued roadmap items, runs, verification results, blockers, pauses, and freshness. Escalations expose decisions that need human input, including planning questions, blocked tasks, platform-policy conflicts, and stalled dependencies.

Keelen also supports specialized project operations. These include UI-review scenario budgets for web applications, Roblox place rollback from retained build artifacts, steering-rule approval and retirement, task replanning, scheduler control, project archiving, and selected security, legal-exposure, and control-gap review workflows.

How it works

The hosted MCP endpoint accepts requests from a compatible client. Onboarding can begin without a token for signup and email verification; subsequent operations use the bearer key issued during setup. GitHub access and AI-engine credentials are connected through the Keelen dashboard and browser approval flows rather than pasted into chat.

Requests are asynchronous. After submitting work, the client receives a thread identifier and a recommended polling interval for get_request_status. Intake can ask follow-up questions, finish with roadmap item identifiers, fail, cancel, or wait for approval. The autonomous loop works from the project roadmap and scheduler state, while plan approval, manual merge, and other project controls determine how work proceeds.

Supported coding engines include Claude Code, Codex, GLM, Kimi, and Grok, subject to the credentials connected to the workspace. The selected engine can also be specified when creating a project.

Setup and configuration

Add the hosted HTTP endpoint to an MCP client, for example:

claude mcp add --transport http keelen https://keelen.ai/mcp

Then provide the contents of Keelen's SETUP.md to the agent and ask it to set up the account. The guided flow covers email verification, AI-engine connection, GitHub authorization, project creation or import, and provisioning. Browser-based steps are completed through dashboard links.

Claude has a separate OAuth surface at https://keelen.ai/claude/mcp. The full headless/API-key surface is https://keelen.ai/mcp; the Claude directory surface omits billing and project-digest tools.

Tools and capabilities

• Create, import, list, archive, and monitor GitHub projects.
• Submit requests, inspect asynchronous intake, answer planning questions, and manage product vision and goals.
• View, reorder, cancel, unpin, rearm, and otherwise maintain roadmap items.
• Inspect escalations and resolve, retry, replan, requeue, or close affected work using typed operations.
• Enable, disable, resume, or immediately process a project's scheduler.
• Approve or retire steering rules that influence future planning, development, and QA prompts.
• Manage web-app UI-review budgets and roll Roblox places back to retained published artifacts.

Limitations and notes

Keelen's queue is not a guarantee that work will finish by a particular time. Capacity, provider limits, missing information, failed checks, and human decisions can pause progress. Changes are checked before merge, and failed checks remain held.

The service runs inside isolated per-tenant sandboxes scoped to the workspace. GitHub access requires explicit approval. Autonomous compute requires an active subscription, while signup, GitHub connection, and project creation are free.

Some actions are owner-only or require a personal connection, including particular planning, review-requeue, platform-policy, and workspace-control operations. Destructive operations such as scheduler changes, task closure, project archiving, and roadmap cancellation should be used with care; history is generally retained, but running machine state may be stopped or discarded.