Programmatic access
How to manage Meddle from outside the app, and the credentials involved.
Meddle has one supported machine interface: the MCP server. It exposes the same controls as the app and authorises through a browser sign-in flow.
https://app.meddle.sh/api/mcpFor setup instructions, see Connect your assistant.
What authenticates what
| Surface | Credential | Reaches |
|---|---|---|
| MCP server | Bearer token from the sign-in flow | Your full workspace: agents, tools, variables, knowledge, phone numbers, evals, calls, members, billing |
| Website widgets | Publishable key (pk_live_ / pk_test_) | One agent, on the origins that key allows |
| App REST routes | Browser session cookie | What you can reach when signed in |
For direct REST access from your own servers, see the roadmap.
Scopes
| Scope | Grants |
|---|---|
agent:read | List and inspect agents, transcripts, readiness |
agent:write | Edit agents, create drafts, publish |
agent:delete | Destructive operations (delete tools, versions, agents) |
workspace:admin | Members, phone numbers, keys, workspace name |
The consent screen offers all four by default.
Destructive operations
Anything that destroys data requires the agent:delete scope and an
explicit confirm: true on the call. Without it the server asks for
confirmation instead of acting.
Audit trail
Every successful change writes an append-only audit entry. Reads and failures are not recorded. See Access control.
Publishable keys
A publishable key authenticates the website widgets. It is scoped to one agent and carries an origin allowlist. It cannot read or change agent settings.