Connect an MCP client

Every connection has its own MCP URL, shown on its page in the app:

https://dylr.dev/mcp/<connection>

Whoever uses it acts as themselves: the connection’s access rules, approvals, and audit log all apply to them.

Claude, ChatGPT, Cursor

Apps with a sign-in screen use OAuth.

  1. Add a custom connector (Claude), an MCP app (ChatGPT), or an MCP server (Cursor) with the connection’s URL.
  2. Your browser opens DylrDev. Sign in if you need to.
  3. DylrDev asks whether to let the app use that connection as you. Choose Allow.

Claude Code, scripts, and other tools

Tools without a sign-in screen use an API key. On the connection’s page, under API keys, create one. It’s shown once, works on that connection only, and acts as you.

claude mcp add --transport http dylr-twilio https://dylr.dev/mcp/<connection> --header "x-api-key: dylr_…"

Other clients can send it as x-api-key: <key> or Authorization: Bearer <key>.

When a call needs approval

When the AI calls a dangerous tool on a connection that isn’t armed, nothing happens on the platform. The AI gets a refusal with a link to the approval and an approval_id. Once an owner or admin approves it, the AI calls the same tool again, with the same arguments and that approval_id, and it runs once.

Revoking access

  • An OAuth app: Settings → AI apps → Revoke. Its access ends at once.
  • An API key: on the connection’s page, Revoke next to the key.
  • Everything on a connection: owners and admins can revoke the connection itself. Its credentials, keys, and pending approvals are deleted; the audit log stays.