What the caller may do here
Role, gate state, plan limits and a set of derived booleans — so an agent on a static surface can check before it acts instead of attempting a write and reading the failure.
Descriptive, never authoritative: see the schema.
Authorizations
MCPJam API key (sk_…). Create one at Settings → API keys. Guest sessions cannot use the API, and API keys cannot manage other API keys.
Path Parameters
ID of the hosted project that contains the server.
Response
The caller's capabilities in this project.
What the caller may do in this project, asked BEFORE they try it.
A planning aid, not a gate. Every enforcement point is unchanged: the write path checks roles and the beta flag inside the platform regardless of what this returned a second earlier. A caller that reads a true here and races a flag flip gets the same clean 403 it would have got without asking. Nothing may consult this INSTEAD of its own check.
It exists because every agent surface MCPJam ships is static — one MCP tool catalog built with no organization in hand, a CLI command tree fixed at install — so an agent planning a task otherwise has to attempt the write and read the failure. By then it has usually already told a human what it was about to do.
The caller's ORGANIZATION role: guest, member, admin or owner. This is what the platform's role checks rank; a project grant does not raise it.
admin or editor, when the caller holds a project grant.
Which channel we resolved this request to arrive on. Echoed so an agent can confirm it is labelled the way it expects — a CLI showing up as rest means its user agent is not reaching us.
The booleans to branch on, derived server-side rather than left for each caller to re-derive from role plus flag state.

