# Claude and ChatGPT
Connect Claude or ChatGPT to Voice Logica once, and you can run the platform from the chat: build and test an agent, change its prompt or knowledge, read calls, start a campaign, set up telephony - including an on-premise PBX.
This is the reverse of an integration. Voice Logica does not call Claude; **Claude calls Voice Logica** through our MCP server, signed in as you.
## Connect your assistant
Sidebar - **Integrations - AI Assistants**. Pick **Claude** or **ChatGPT** and click **Connect**. The dialog shows three steps, the server URL with **Copy URL**, and an **Open Claude** / **Open ChatGPT** button.
Server URL:
```text
https://api.voicelogica.ai/api/v1/mcp
```
1. **Open Claude** from the dialog. It lands on **Customize - Connectors** with the name and URL already filled.
Doing it by hand: in Claude open **Customize - Connectors** (not Settings), click **Add**, then **Add custom connector**.
2. Name it **Voice Logica**, paste the server URL, click **Continue**.
3. Sign in with your Voice Logica account when Claude asks, and allow access.
4. Start a new chat and ask: *"Which Voice Logica agents do I have?"*
Works in Claude on the web, desktop and mobile once the connector is added to your account.
1. In ChatGPT (Plus, Pro or Team) open **Settings - Security and login** and turn on **Developer mode**.
2. **Settings - Apps - Create**. Name it **Voice Logica**, paste the server URL, set **Authentication** to **OAuth**.
3. Sign in with your Voice Logica account and allow access.
4. In a new chat, open **+ - Developer mode** and enable **Voice Logica**. Ask: *"Which Voice Logica agents do I have?"*
One click, then sign in with your Voice Logica account when the app asks:
- **Cursor:** [Add to Cursor](cursor://anysphere.cursor-deeplink/mcp/install?name=Voice%20Logica&config=eyJ1cmwiOiJodHRwczovL2FwaS52b2ljZWxvZ2ljYS5haS9hcGkvdjEvbWNwIn0=) (or **Integrations - AI Assistants - Cursor - Add to Cursor** in the app).
- **VS Code:** [Install in VS Code](https://vscode.dev/redirect/mcp/install?name=voice-logica&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fapi.voicelogica.ai%2Fapi%2Fv1%2Fmcp%22%7D). Use it from Copilot Chat in **Agent** mode.
- **Claude Code:** run this, then type `/mcp` in Claude Code and pick **voice-logica** to sign in.
```bash
claude mcp add --transport http voice-logica https://api.voicelogica.ai/api/v1/mcp
```
- **Windsurf:** add this to `~/.codeium/windsurf/mcp_config.json`, then refresh the MCP list.
```json
{ "mcpServers": { "voice-logica": { "serverUrl": "https://api.voicelogica.ai/api/v1/mcp" } } }
```
Any other app that supports remote MCP servers with OAuth connects with the server URL above.
**No Voice Logica account yet?** Connecting creates it. In the window that opens, choose **Continue with email** (or Google / Microsoft), enter the 6-digit code from your inbox, then your business name and website, and click **Create account & connect**. The window closes, you are back in the chat already connected, and your first agent is being built from your website. Ask *"show me my agent"*: it answers "building" for about a minute, then gives you ways to hear it.
Back in Voice Logica the tile turns **Connected**. Cursor and Perplexity are on the same tab and work the same way.
## What you can ask
Plain requests work. A few that do real work:
- *"Build an agent that answers for my dental clinic, in Greek, and books appointments."*
- *"Call me so I can hear it"* - it rings your phone with the agent. Or *"let me test it in the browser"* for a link.
- *"Make the greeting shorter and stop it from giving prices."*
- *"Add our website to its knowledge."*
- *"Show me yesterday's calls that ended in a transfer, with the reason."*
- *"Start a campaign calling this list tomorrow from 10:00 to 14:00."*
- *"Connect my Panasonic PBX."* / *"Add +30 210 123 4560 to 4569 to our trunk and send them to the agent."*
- *"During calls, text the caller our booking link."*
- *"Set up a phone for maria@acme.gr and email her the instructions."*
- *"We want to go live: which plan fits us?"*
- *"How do I connect my carrier?"* - it answers with the step-by-step guide and offers to do each step for you.
The assistant asks before it does anything that changes live behaviour or costs money, and tells you what changed.
Not sure what to ask? In Claude, click **+** and open **Voice Logica** for ready-made starters, or ask *"What can you do?"*. The full list, by area: [What you can ask](https://docs.voicelogica.ai/integrations/what-you-can-ask/).
Under the tiles, **Choose what it uses by default** sets the **SIP trunk**, **AI agent**, **SMS sender** and **Calendar** used when a request does not name one.
## What you see in the chat
In Claude and ChatGPT some answers come as a small card instead of text:
- **Your agent** - its name, language and greeting, with buttons to talk to it in the browser, have it call your phone, or improve it.
- **Test call** - the call's status updates by itself while it rings and runs, then shows the summary and the transcript, with a link to the recording.
- **Plans** - one card per plan with the price and what is included. **Choose** asks for that plan in the chat; you add your card on a secure Stripe page, never in the chat.
Apps that do not show cards (for example Cursor) get the same information as text.
## Go live from the chat
1. **Pick a plan.** *"We want to go live."* You get the plans; choose one.
2. **Add a card.** If there is no card on file you get a secure Stripe link. Add the card there and say *"done"*; the plan is bought.
3. **Get a line.** Companies in Greece can order their [free number](https://docs.voicelogica.ai/telephony/voice-logica-numbers/). Otherwise connect your [PBX](https://docs.voicelogica.ai/telephony/connect-your-pbx/) or your [carrier](https://docs.voicelogica.ai/telephony/your-own-carrier/).
The free number is only ordered after you confirm: the assistant first tells you whether it is available and which agent will answer it.
## Numbers, routes and team phones
- **Numbers:** add numbers to a trunk (a list or a range), move a number to another route, stop using one.
- **Inbound routes:** which agent, person or group answers each number, with different destinations after hours and on holidays.
- **Outbound routes:** which trunk and caller ID carry calls to which numbers.
- **Team phones:** invite a person, turn on the softphone, Windows app or iOS app for them (buying a seat if none is free), and email or text them the setup steps.
Changes only touch what you name. Deleting a route or number is always confirmed first.
## Connect your PBX from Claude
Most office phone systems connect by registering a trunk out to Voice Logica: no port forwarding, no public IP.
1. **Ask.** *"Connect my Panasonic PBX to my agent."* It creates the connection and gives you the server, port, username and password.
2. **Enter the values.** It walks you through the steps in your PBX's own menus, one at a time. The full list per make is on [Connect your PBX](https://docs.voicelogica.ai/telephony/connect-your-pbx/).
3. **Check.** Say *"done"*. It checks whether the PBX registered, and if not, tells you why (wrong password, nothing arrived yet) and what to check.
### A PBX that cannot register a trunk
For a phone system on the office network that can only be reached as an extension. The same flow as the [Edge device](https://docs.voicelogica.ai/telephony/edge-device/) page, driven from the chat.
1. **Ask.** *"Connect my PBX. It's on the office network, the IT PC runs Windows."* Say Linux if the machine next to the PBX is Linux or a Raspberry Pi.
2. **Run the installer.** You get a download link for a Windows installer made for your company (valid 4 hours), or a one-line Linux command with the token inside. Run it on an always-on machine on the same network as the PBX. The assistant also lists the firewall needs: outbound TCP 443 and UDP 51820. Using the virtual machine instead? Start it and read the assistant the **Claim code** from its console screen.
3. **Device online.** Tell it when the installer finished. It checks the device: online, tunnel up, and any PBX it found on the LAN.
4. **Give the PBX details.** The PBX IP (for example `192.168.1.10`), its SIP port (5060 unless your PBX uses another, such as 5059 on Alcatel OXO) and the extension username and password the PBX created for Voice Logica.
Because the address is private, the assistant creates the trunk **through your edge device** automatically. With several devices it picks the one whose network contains the PBX, and asks you if that is not clear. The trunk registers, and the assistant confirms.
Last step: *"Send calls on that line to my agent"* - then dial it from a real phone and ask it to show you the call.
> **If it stops at the device:** The assistant will not create a trunk the device cannot carry. If it says the tunnel is down, open outbound **UDP 51820** on the site firewall and ask it to retry. The other causes are on [Edge device - Troubleshooting](https://docs.voicelogica.ai/telephony/edge-device/#troubleshooting).
## How the tools are organised
This part is for IT teams and developers; you never need tool names to use the assistant.
The everyday work has its own tools: agents and their prompt and settings, test calls, calls and statistics, knowledge, workflows, campaigns, trunks and `connect_pbx`, plans, support tickets and tasks. The rest of each area sits behind two tools: `_query` reads, `_execute` changes. Called without an action, `_query` lists every action with its input, so the assistant looks it up when it needs it.
| Area | What is in it |
|---|---|
| `telephony_*` | Phone numbers, inbound and outbound routes, sending a team member their device setup |
| `pbx_*` | Whether a PBX registered, SIP logs of a call or a trunk, edge devices and their installer |
| `team_*` | Members, invitations, phone seats per device, buying seats |
| `query_user_action`, `execute_user_action` | A member's status and access: change name, phone or access, disable or re-enable, remove, password reset |
| `messages_*` | SMS, Viber and email, mailboxes, SMS sender IDs |
| `calendar_*` | Calendars and events |
| `billing_*` | Subscription, add-ons, card on file, cancel or resume, VAT number |
| `tickets_*` | Your support tickets: list, read, reply |
| `knowledge_*` | Knowledge housekeeping and the questions callers asked that the agent could not answer |
| `leads_*`, `campaigns_*` | Campaign leads (including .xlsx/.csv import), scheduled calls, one campaign's details, pause, resume, test call |
| `scenarios_*`, `versions_*` | Test scenarios and suites, saved and published versions of agents and workflows |
| `eshop_*` | The e-shop product catalogue the agent answers from |
Each action runs with the same permission check as the tool it replaced, and a chat opened before a change still works with the tool names it already has.
## Security
- **Your company only.** Every action runs on the company you are signed in to. If you belong to several, ask it to switch - it cannot mix them.
- **Your permissions.** The assistant can do what your user role can do in the app, nothing more. Telephony and edge-device setup need an admin on the company.
- **You sign in, not a key.** Access is an OAuth sign-in to your account. No API key is pasted into the chat.
- **Secrets stay out of the chat.** Passwords, API keys and tokens saved in your settings (a workflow's Authorization header, a webhook token, a PBX password) show as `[hidden]`. When the assistant edits that setting, the stored value is kept.
- **Turn it off.** On **Integrations - AI Assistants**, **Disconnect** on the tile (then **Disable**) blocks that assistant at once; **Re-enable** restores it. Removing the connector in Claude or ChatGPT also ends it.
Passwords you give it (a SIP extension, for example) are stored on the trunk like any trunk you create in the app.
Before connecting, you or your IT team can read every tool the assistant gets, with what each one does and whether it only reads or also changes data, at [api.voicelogica.ai/.well-known/mcp/server-card.json](https://api.voicelogica.ai/.well-known/mcp/server-card.json). No sign-in needed.
## Troubleshooting
**The assistant says it has no Voice Logica tools**
1. The connector is added **and** signed in (Claude: **Customize - Connectors** shows it connected).
2. ChatGPT: **Developer mode** is on and **Voice Logica** is enabled in *this* chat (**+ - Developer mode**).
3. The tile on **Integrations - AI Assistants** is not **Disabled** (use **Re-enable**).
**It shows another company's agents**
You are signed in to a different company. Ask it to list your companies and switch, or switch company in the app and reconnect.
**It says access denied for telephony or edge devices**
Your role does not include that. Ask a company admin to do it, or to raise your access under **Team and access**.
**Claude Settings says connectors moved**
Connectors live under **Customize - Connectors**, not Settings. Use **Open Claude** in the connect dialog to land there directly.
## Next Steps
[Edge device](https://docs.voicelogica.ai/telephony/edge-device/) - the same PBX setup, from the app.
[Your own carrier](https://docs.voicelogica.ai/telephony/your-own-carrier/) - carriers and public PBXs.
[AI Assistants](https://docs.voicelogica.ai/integrations/mcp-settings/) - the other direction: your agent calling an MCP server during a call.