Skip to content
XcellAgency
Start a project

Developers

The whole platform, available to agents.

A complete MCP server and REST API — 14 tools covering the catalog, briefs, orders, deliverables, invoices and support.

Free on every tier. Not an add-on, not an enterprise upgrade.

MCP server

Connect Claude, or anything else that speaks MCP

Point an MCP client at the endpoint with an organization-scoped key. The key decides which organization the tools operate on — no tool takes an organization id.

Endpoint

https://api.xcellagency.com/mcp

Keys are issued per organization from Settings → API keys in your portal. A key carries the permissions of the role it was issued under.

Tools

14 tools, two safety classes

Reads run straight through. Anything that moves money, changes scope or is visible to your client needs an explicit confirmation first — an agent cannot do those silently on your behalf.

Reads(9)

Auto-approved. Subject to the same permissions as the UI.

list_services
List the service catalog. Returns name, summary, price, turnaround and revision count for each SKU.
get_service
Get one service by slug, including what is included and its FAQ.
create_brief
Submit a brief in any shape — free text, a Loom URL, a Figma link. Returns a completeness score and the next question to answer.
Requires order:create
answer_brief_question
Answer the outstanding interrogation question on a brief.
Requires order:create
get_order
Get one order: status, line items, SLA clock, deliverables, invoice.
Requires order:read
list_orders
List this organization orders, newest first. Filter by status or SLA health to find work that is at risk or awaiting the client.
Requires order:read
get_invoice
Get an invoice, grouped by service line, with hours by service.
Requires invoice:read
create_ticket
Raise a support ticket against the SLA.
Requires assistant:use
search_knowledge
Search this organization knowledge: orders, deliverables, invoices, tickets, contracts. Returns cited excerpts.
Requires assistant:use

Requires confirmation(5)

A human confirms before the call runs. Permission is checked first, so a caller who is not allowed is told that rather than asked to confirm.

create_order
Create an order from a brief or explicit line items. Requires confirmation: this commits spend.
Requires order:create
approve_deliverable
Approve a deliverable. Requires confirmation: this is client-visible and final.
Requires deliverable:approve
request_changes
Request changes on a deliverable. Requires confirmation: this consumes a revision, and beyond the limit it raises a billable change order.
Requires deliverable:review
pay_invoice
Pay an invoice, in full or in part. Requires confirmation: this moves money.
Requires invoice:pay
pause_subscription
Pause a subscription, banking the unused days. Requires confirmation: this changes billing.
Requires subscription:modify

Guarantees

What the API will not do

  • No tool takes an organization id

    Scope comes from the API key. A tool that accepted an organization id could be argued into passing someone else’s, which turns prompt injection straight into a cross-tenant read.

  • Same permissions as the UI

    A member who cannot pay an invoice in the portal cannot pay one through an agent. The API is not a way around the permission model.

  • Unknown tools are denied

    Authorisation is deny-by-default. A tool added next year is safe without anyone remembering to classify it.

Build against it.On any plan.

Create an account, issue a key, and point your agent at the endpoint.