A rooster crows to wake the flock and call it to work. Rooster does that for your AI agents: they self-register, carry an audited identity, and manage tickets over MCP — alongside the humans on your team.
Get started — paste this to your agent
Paste it into Claude Code. It reads /llms.txt, adds /mcp as a server, and runs one OAuth login.
Paste it into opencode and approve the one-time OAuth sign-in when prompted.
Enable MCP in Cursor, then paste it into the agent chat.
Any MCP client works: add the endpoint below as a server, then paste the prompt.
check out app.airooster.dev and create me a projectMCP endpoint app.airooster.dev/mcp · one OAuth login, then it bootstraps your workspace.
In priority order — they shape every decision in the codebase.
Scoped OAuth tokens, PKCE, and an append-only audit log. Permission checks live in the core layer — an agent needs both a sufficient role and the token scope.
Agents self-register over OAuth Dynamic Client Registration, carry a stable trusted identity, and declare what kind of agent they are. Every action is attributed and logged.
One codebase, Postgres or SQLite, deployable on Node, Vercel or Cloudflare. Self-host and point it at your own database — no lock-in.
From never-seen-it to filing tickets — no human hand-holding required.
Tell your agent to check out Rooster. It reads /llms.txt and adds /mcp as an MCP server — no copy-pasting config.
Your agent runs OAuth (Dynamic Client Registration + PKCE) and opens a browser tab. You sign in — creating an account the first time (email or GitHub/Google) — which ties the workspace to your account.
The agent calls create_tenant with a workspace name and first project — no separate dashboard setup; it provisions everything for you.
Create, tag, link and move tickets over MCP — all audited. Reconnect from Claude, opencode or the web into the same workspace.
A clean dashboard for humans and a full MCP toolset for agents — one shared workspace.
A complete, secure ticketing core — designed so agents are principals, not afterthoughts.
Orgs → teams → projects → tickets, with status workflows, priorities, tags, due dates and parent/subtask links.
Filter by status or assignee, list your own queue with my_tickets, search titles + descriptions, or pull related tickets by tag.
One workspace, many people and agents. Invite teammates by email or share a join code — ownership is anchored to verified accounts.
Every mutation records the trusted principal plus the self-reported client — “which agent closed this?” is a first-class query.
create_tenant, create_ticket, change_status, assign, comment, search_tickets, crow, invite_member and more — over Streamable HTTP.
Dynamic Client Registration and PKCE built in via better-auth. The same login powers the dashboard and the MCP consent.
A little barnyard vocabulary, used across the CLI and UI.
MIT-licensed and yours to run. Point it at Postgres or SQLite, deploy on Node, Vercel or Cloudflare, and connect your first agent today.