Connect your assistant

ChatGPT & Claude · Account setup, permissions and calling · Updated 3 October 2026

Start here

DialAgent connects your assistant to your DialAgent account over remote MCP with OAuth. These instructions cover a custom connection, not an approved public app-directory listing. Connecting an account does not place a call or guarantee that calling is available.

MCP server URL

https://pilot.dialagent.com/mcp

Account: Open your DialAgent account. Use the same account in ChatGPT and Claude to access your own tasks and phone setup.

Choose ChatGPT or Claude, complete account authorization, then check phone setup. Read and approve only the permissions and actions you intend.

Create or sign in to your account

When your assistant opens DialAgent, choose sign up if you are new, or log in to your existing account.

  • Username: 3–64 characters, using only ASCII letters A–Z / a–z, digits 0–9 and underscore (_). A username is not an email address; @, dots, spaces and non-Latin letters are not accepted.
  • Password: 6–128 characters (Unicode code points). Spaces are accepted. Use a strong, unique password.

After sign-up or login, review the authorization screen and select Allow to connect the account. Wait for completion and return to the assistant when prompted. Sign-up, OAuth authorization and phone verification are separate steps. Do not put your password in a chat.

Connect ChatGPT

Set up the custom app in ChatGPT on the web. OpenAI currently documents developer mode for Plus, Pro, Business, Enterprise and Education accounts; workspace policy can restrict access. Menu labels vary between interfaces.

  1. Enable Developer mode. In the newer interface, open Settings → Security and login. In the Apps interface, look under Settings → Apps → Advanced settings. Managed workspaces may require an administrator to enable it.
  2. Open ChatGPT Plugins and use the + button to create a developer-mode app. If your interface uses Apps, choose Settings → Apps → Create instead.
  3. Name it DialAgent, paste https://pilot.dialagent.com/mcp as the MCP server URL and choose OAuth. Use automatic client registration if your dialog offers it; do not enter shared credentials or API keys.
  4. Choose Connect or Scan Tools, as shown. On DialAgent, sign up or log in, select Allow, and complete the return to ChatGPT. Wait for the tool scan, then finish Create if shown.
  5. In a new chat, open the + menu, select Developer mode or the available app picker, and enable DialAgent. Ask: “Use DialAgent to check my phone setup. Do not place a call.”

If you cannot create a custom app, check your plan and workspace permissions. Searching the public directory is not a substitute for this setup. This guide does not promise mobile setup or app-directory approval.

Official references: OpenAI developer mode · Apps and managed-workspace setup.

Connect Claude

Use the hosted remote connector in Claude, not a local extension or a Claude Code command. Claude currently documents custom URL connectors on Free, Pro, Max, Team and Enterprise plans; Free allows one custom connector. Organization controls still apply.

  1. Open Customize → Connectors. In interfaces that use the older navigation, open Settings → Connectors.
  2. Select Add custom connector. Enter DialAgent if a name is requested, and paste https://pilot.dialagent.com/mcp as the server URL. Choose Web if asked for the connector type.
  3. If authentication choices appear, choose Sign in now and Use Claude’s published identity. DialAgent supports this method. No client ID, client secret, API key or request header is needed. In the single-screen dialog, leave optional advanced OAuth credentials empty.
  4. Click Add, then Connect if shown. On DialAgent, sign up or log in, review the permissions, select Allow, and finish returning to Claude.
  5. Enable DialAgent in the chat’s + → Connectors menu. Ask: “Use DialAgent to check my phone setup. Do not place a call.” Review tool permission prompts before approving.

Team / Enterprise: an Owner (or an eligible Enterprise custom role) must first add the connector under Organization settings → Connectors → Add → Custom. Each member then clicks Connect and authorizes their own DialAgent account. Do not share one person’s login.

Official reference: Add a connector that isn’t in the directory, including authentication options and plan restrictions.

Set up your own Caller ID

Ask DialAgent to check your setup first. If registration or phone setup is required, provide your name and a phone number you own, including its country code. This does not start your requested call.

  1. Explicitly ask to verify your own number, and review the assistant’s tool confirmation. Verification can place an incoming validation call; charges may apply.
  2. DialAgent displays a dedicated validation code. Enter that code on the incoming verification call’s keypad. This is not SMS login. Never give the assistant an account password or an unrelated one-time / two-factor code.
  3. Ask the assistant to check setup again. Only a confirmed verified status establishes readiness; a code request or your saying “done” does not.

If your number is already verified, reuse it. Do not repeat verification just because a tool lacks permission or a call fails. If verification is pending or uncertain, check status instead of automatically requesting another call.

Request one call explicitly

State the destination and a concrete goal: what the assistant should convey, ask or accomplish. Add any constraints and what it may share. For example: “Use DialAgent to call the restaurant at the number I provide, ask whether a table for two is available tonight at 7, and do not book it.”

The assistant checks setup, prepares a draft and uses your verified Caller ID. A draft is not a call. Review any native tool confirmation and any additional DialAgent permission request. Only approve a call you actually want. Connecting, opening history or checking status never authorizes a new call.

Current calls are limited to 600 seconds connected time and 25 seconds ringing, with no automatic redial. Account access, permissions, destination rules and service readiness can still prevent a call. A successful connection is not a guarantee of calling access.

Current MCP tools

The assistant discovers the current tool definitions from DialAgent. These names describe the workflow; ordinary users do not need to assemble tool arguments.

  • onboarding_status — check phone setup without sending a code or placing a call.
  • begin_phone_verification — request validation of your own number, only with your explicit permission.
  • list_caller_ids — list your available verified Caller IDs.
  • draft_task — prepare a task with your destination, goal and duration limit; no call is placed.
  • start_call — request one explicitly authorized call using that draft and your selected Caller ID.
  • task_status and list_tasks — read your own task status and history.
  • cancel_task — cancel an eligible unreserved draft. It is not a tool for hanging up a live call.

This user guide does not offer a public REST API, API-key setup, parallel-call tool or SDK.

No user-configurable webhook integration is documented for the current service. Do not use old place_call or get_call examples.

Status, history and text results

Ask the assistant to check the task, or open your DialAgent account for your own history. Task status, call status and conversation-result availability are different things. “Registered”, “draft” or “queued” does not prove the recipient answered or the goal was achieved.

Available text records are persistent and scoped to the account that owns the task; another user’s connection does not grant access to them. When enabled for your account, received conversation text may be available, but it is not guaranteed to cover every spoken word. A missing transcript is not proof that no call occurred.

No audio-file recording is provided. Do not expect a recording download or an expiring audio link. See the privacy policy for data handling and contact options.

Limits and safe use

Use only your own verified Caller ID, and request only calls you are entitled to make. Do not use DialAgent for emergencies, impersonation, harassment, bulk outreach or collecting passwords and security codes. See Safety and Terms.

There is no promise of unlimited access, universal destination coverage or a production-scale service. The current connector and account determine what is available. The 600-second call limit includes connected hold time.

Troubleshooting

  • Username rejected: use 3–64 ASCII letters, digits or underscores, not an email address. If it is already taken, log in to your existing account or choose another username.
  • Expired form / CSRF error: reopen the current login or sign-up form from the active connection flow, then submit that fresh form. Do not resubmit an old tab repeatedly. Check whether you already created the account before signing up again.
  • “registration_required”: follow the setup instructions. This is not evidence that a call started.
  • Permission or authorization required: review the requested access in the host / DialAgent authorization screen. If a completion screen is waiting, finish it and return to the assistant. A prompt cannot grant missing permissions. If access still fails, stop and contact support; do not repeatedly verify your phone or assume the call was placed.
  • Connected, but no tools: ensure DialAgent is enabled in that conversation and allowed by your workspace. Refresh the app’s tool list if the host offers it. Reconnect only if the connection is actually expired, revoked or the host asks you to authorize again.
  • Call failed, pending or outcome unknown: check its existing status before requesting anything else. Do not automatically retry or create a replacement call; an uncertain result may still represent a real attempt.

For help, email hello@dialagent.com with the host, the step and the visible error. Never send passwords, OAuth tokens or validation codes. For abuse or opt-out requests, see contact options.