Getting started

DylrDev is an MCP gateway for contact center platforms. You connect a platform account once; your AI tools reach it through DylrDev, which checks who’s calling, holds dangerous actions for a person, and logs everything.

Create an account

Create an account with your email and a password, then confirm the email. Confirming signs you in. Your account comes with a Personal org that’s just you, on the Free plan: one dialer connection and 72 hours of audit history. Upgrade it to Business from Billing for more connections. In your account settings (click your name at the bottom of the sidebar) you can turn on two-factor authentication (after your password, signing in asks for a code from an authenticator app) or add passkeys. Once you have a passkey, your password alone no longer signs you in.

Orgs and roles

Everything belongs to an org, and the org is part of each page’s address (/app/personal/… for yours, a team’s own address for a team), so different tabs can show different teams. To work with others, start a team from the org menu in the sidebar and invite people from Team. A team’s Settings has its name, its 2FA requirement, and leaving or (for the owner) deleting it. A personal org can’t invite anyone. A new team is on Business for a 14-day trial, no card needed; after that it’s a seat per member (see pricing), or it becomes read-only until it subscribes. Read-only keeps read tools working and refuses everything else.

  • Owners and admins connect platforms, decide who can use them, arm them, and approve dangerous calls. On Business, they can also require everyone in the team to have two-factor authentication or a passkey (in the team’s Settings, under Team security); anyone with only a password can’t use the team, or its connections from their AI apps, until they add one.
  • Members use the connections they’re given.

Connect a platform

In Connections, choose Connect a platform, pick it, and fill in its credentials. DylrDev makes one read call to check them, then keeps them encrypted; nobody sees them again, including you. See Platforms for what each one needs.

Each connection gets its own MCP URL. To use two accounts, connect both and add both URLs to your AI.

Who can use a connection

By default every member of the org can. Under Who can use it on the connection, choose Only selected and tick the members who should. Owners and admins can always use every connection.

Dangerous tools

Some tools change things that are hard to undo: stopping a campaign, deleting a queue. These never run on the AI’s say-so alone. When the AI tries one, DylrDev refuses and gives it a link for you. On that page an owner or admin can:

  • Approve this call: that exact call, with those arguments, may run once in the next 15 minutes.
  • Approve and arm: the same, and every dangerous tool on the connection runs without asking for 30 minutes.
  • Deny.

Owners and admins can also arm a connection ahead of time from its page, and disarm it early.

Audit

Audit lists every tool call and every change in the org: who made it, through which app, and whether a dangerous call ran because the connection was armed or because it was approved. Arguments are never stored. Events are kept for a week on Business and 72 hours on Free.

Next