Connect your AI to DVT

You'll need:

• a DVT sign-in for the workspace (your AI acts as you, so it can do what you can do there, and no more);
• DVT's server address: https://app.dvtapp.co/api/mcp
• a paid plan with your AI app. Connecting your own tools (“custom connectors”) isn't on most free plans.

When you connect, DVT asks you three things: which workspace, whether the AI can send or only writes drafts for the team to send, and what it may reach (contacts, emails and texts, social, reviews, projects and deals, forms, workflows, and, only if you tick them, calls and ads).

1. In Claude, open Settings → Connectors and choose Add custom connector.
2. Name it DVT and paste https://app.dvtapp.co/api/mcp as its address. Add it.
3. Choose Connect. A DVT page opens: sign in with your email (DVT emails you a link), pick the workspace and what Claude may do, and choose Allow.
4. In a chat, turn DVT on from the tools menu if it isn't already, and ask away.

On a Claude Team or Enterprise plan, an owner of your Claude organization may need to add the connector for the organization first; then each person connects it and signs in as themselves. Once added on claude.ai, DVT also works in the desktop and phone apps.

1. In ChatGPT, open Settings → Apps & Connectors → Advanced settings and turn on Developer mode.
2. Back in Apps & Connectors, choose Create. Name it DVT, paste https://app.dvtapp.co/api/mcp, and pick OAuth for authentication.
3. Sign in to DVT on the page that opens, pick the workspace and what ChatGPT may do, and choose Allow.
4. In a new chat, add DVT from the tools menu, then ask.

ChatGPT asks you to confirm before it changes anything in DVT.

In a terminal:

claude mcp add --transport http dvt https://app.dvtapp.co/api/mcp

Then, inside Claude Code, run /mcp, pick dvt and choose Authenticate. A browser opens for you to sign in to DVT.

Tools that can't sign in use a DVT API key instead.

1. In DVT, go to Settings → AI access → New API key. Name it, pick what it can do, and make it.
2. Copy the key straight away: DVT shows it once. The page also shows the exact setup for Claude Code and Cursor.
3. In n8n, give an AI Agent node an MCP Client Tool with the endpoint https://app.dvtapp.co/api/mcp, transport HTTP Streamable, and Bearer authentication set to the key.

Treat a key like a password. If one gets out, revoke it in Settings → AI access and make another.

• “Who got in touch this week, and who hasn't had a reply yet?”
• “Draft replies to our unanswered Google reviews. Keep them short and friendly.”
• “Email Sarah Jones to say her quote is ready, and add a note that I followed up.”
• “Schedule three Facebook posts for next week about our spring offer.”
• “Make a deal for the Miller roof job at $8,400 and a project with the usual tasks.”
• “Build a workflow that texts new leads from the website form and tags them.”
• “Set up a contact form for our website and give me the code to paste.”

It uses your business's time zone and your workspace's own tags, pipelines and team. If it isn't sure which customer you mean, it looks them up first.

Your AI can also take work from DVT without being asked each time:

• In a workflow, add the Hand to my AI step: your AI writes a text or email to the contact, or does something else with DVT's tools. You choose whether DVT sends what it writes or saves it as a draft for you to check.
• For reviews, add a rule under Automations → AI, such as “Google reviews with 3 stars or fewer: write a reply”.

Then, in Settings → AI access → Let automations use your AI, choose how DVT tells your AI a job is waiting:

• Claude routine. DVT starts a routine on your Claude plan (Pro, Max, Team or Enterprise) as soon as a job comes in, with no API key. The page has the routine's instructions ready to copy. Jobs are usually done within a few minutes, and you set how many runs a day DVT may use.
• Webhook. DVT sends each job to your own agent (n8n, Zapier, Make or your code), which does it in seconds. That agent uses an AI API key, which its provider bills by use.
• Just ask. Jobs wait until you open Claude or ChatGPT and say “do my DVT tasks” (some AI apps also list it as a ready-made prompt). Owners get one email a day while jobs are waiting.

Use Send test job on that page to check it works. Every job and how it went is listed under Automations → AI. Jobs nobody finishes within 3 days are dropped, and the owners are told.

• Your AI acts as you, with your role. Staff can't use it to do what only owners can.
• Drafts only connections never reach a customer: emails, texts, posts and review replies wait for someone on the team to send them. Calls and ads aren't offered to them at all.
• DVT's own rules still apply: texts only to people who agreed to them, never between 9pm and 8am, no email to bounced addresses, and your plan's monthly allowances.
• Calls and ads are off unless you tick them when you connect. Ads spend your ad account's money, so only owners can allow them.
• Settings → AI access lists every connection (owners see everyone's) with what each did lately. Revoke one and it stops at once. Taking someone off the team cuts off their AI too.
• Things your AI sends are marked “by AI” in the inbox, with the connection's name.

What your AI reads from DVT goes to your AI provider, under your own agreement with them. DVT never sends your data to an AI provider by itself.

• “AI access isn't part of the plan”: ask whoever looks after your DVT account.
• The AI says DVT can't do something: the connection may not reach that area (connect again and tick it), your role may not allow it, or your plan may not include that feature.
• It asks you to sign in again: sign-ins last 60 days without use, and stop if the connection is revoked. Connect again from your AI app.
• Jobs stay waiting: open Settings → AI access. It shows the last problem waking your AI (for a routine, usually a token to regenerate or a routine that's paused), and how many runs were used today.
• Still stuck? Email support@dvtteam.com.