Features

FelagarMCP for agents

Connect Cursor or Claude with scoped MCP tools, template and onboarding access, and an audit log of what agents did.

In practice

MCP for agents

Connect Cursor, Claude, and other MCP clients with OAuth. Tools respect scopes (tickets, projects, deliverables, time, templates, onboarding), agents act as your agency, and MCP settings show connected clients plus recent actions so “under your permissions” is visible, not just a promise. Staff confirmation still gates welcome emails, retainers, and other client-facing or billing actions.

Agents act under scopes you grant, with an audit trail in settings. They can browse templates and start onboarding, but staff still confirm before anything reaches a client or billing.

Highlights

What stands out when this becomes part of how you run client work.

01
OAuth clients with enforced tool scopes
02
Templates, onboarding, and agent action audit
03
White-label MCP URL for your studio

How it works

MCP lets agents act as your agency with OAuth scopes you control. Settings show who connected and what ran.

01
Open Settings → MCP and connect an OAuth client such as Cursor or Claude with the tool scopes you allow.
02
Agents call scoped tools for tickets, projects, deliverables, templates, onboarding, time, and more, acting as your agency.
03
Review the audit log of recent actions so “under your permissions” is visible, not a vague claim.
04
Use a white-label MCP URL when you want agencies to brand the public endpoint for their studio.

We run the platform. You run the studio.

Create an account, invite your team and clients, and you’re live, with no DevOps side quest. Updates, uptime, and the portal stay on us so you can stay on the work that pays.

Request beta access Self-hostComing soon

MCP for agents

Highlights

How it works

Related features

We run the platform. You run the studio.