For AI assistants: this page as plain markdown is at https://docs.voicelogica.ai/raw/integrations/claude-chatgpt.md, and https://docs.voicelogica.ai/llms.txt lists the docs by topic, one file each, small enough to read whole. Read those rather than this HTML page.
Claude and ChatGPT
Ce contenu n’est pas encore disponible dans votre langue.
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
Section titled “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, an Open Claude / Open ChatGPT button and, for ChatGPT, Download plugin.
Server URL:
https://api.voicelogica.ai/api/v1/mcpDirect links, same as the app:
- Claude: Add to Claude - opens Add custom connector.
- ChatGPT: Plugins in ChatGPT - turn on Developer mode first (step 1 below), then click Browse directory, Add at the top right and Add custom MCP server, and paste the server URL.
-
Open Claude from the dialog, or use Add to Claude. Both open Add custom connector with the name and URL already filled.
Doing it by hand: in Claude open Customize - Connectors (also under your name - Settings - Connectors), click + Add, then Add custom connector.
-
Name it Voice Logica, paste the server URL, click Continue. If the boxes are empty, copy the URL from here:
https://api.voicelogica.ai/api/v1/mcp -
Sign in with your Voice Logica account when Claude asks, and allow access.
-
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.
-
In ChatGPT open Settings - Security and login and turn on Developer mode (under Developer mode, near the bottom).
-
Open Plugins in ChatGPT, click Browse directory, then Add at the top right. Pick one:
-
Upload plugin archive - download the Voice Logica plugin (.zip) and drop it in the window, then Add plugin. It brings the server URL and our skills, so ChatGPT already knows how to work with your agents.
-
Add custom MCP server - name it Voice Logica, keep Connection on Server URL and paste the server URL, keep Authentication on OAuth, tick I understand and want to continue, then Create as a plugin. ChatGPT cannot fill the URL in from a link, so copy it from here:
https://api.voicelogica.ai/api/v1/mcp
-
-
Sign in with your Voice Logica account when ChatGPT asks, and allow access. Then open Voice Logica in Plugins and under Permissions choose Allow all tools, so ChatGPT doesn’t stop to ask before every action.
-
Start a new chat and ask: “Which Voice Logica agents do I have?” If it does not use Voice Logica, click + in the message box and turn on Voice Logica.
Developer mode is on every ChatGPT plan, Free included. Workspace (Business, Enterprise) admins may have to allow custom plugins first.
Microsoft 365 Copilot and Teams reach a custom MCP server through an agent you build in Copilot Studio. You need a Microsoft 365 Copilot or Copilot Studio license.
-
Open Copilot Studio (or Integrations - AI Assistants - Microsoft Copilot - Open Copilot Studio in the app). Create an agent or open one you have.
-
Go to Tools - Add a tool - New tool - Model Context Protocol. Name it Voice Logica, add a short description (Copilot reads it to decide when to use the tool), and paste the server URL:
https://api.voicelogica.ai/api/v1/mcp -
Set Authentication to OAuth 2.0 and pick Dynamic discovery, then Create. Sign in with your Voice Logica account when asked, and add the tool to the agent.
-
Publish the agent to Teams and Microsoft 365 Copilot. Open it in Copilot and ask: “Which Voice Logica agents do I have?”
Microsoft Copilot cannot open with a prompt already filled in. Edit with Microsoft Copilot in Voice Logica opens Copilot and copies the prompt, so you paste it.
One click, then sign in with your Voice Logica account when the app asks:
-
Cursor: Add to Cursor (or Integrations - AI Assistants - Cursor - Add to Cursor in the app).
-
VS Code (GitHub Copilot): Install in VS Code. Use it from Copilot Chat in Agent mode (or Integrations - AI Assistants - GitHub Copilot - Add to VS Code in the app). Edit with GitHub Copilot in the app opens Copilot Chat with the prompt filled in.
-
Claude Code: run this, then type
/mcpin Claude Code and pick voice-logica to sign in.Terminal window 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.{ "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, GitHub Copilot, Microsoft Copilot and Perplexity are on the same tab and work the same way.
What you can ask
Section titled “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.”
- “Delete all my DEH campaigns.” - it lists them with their lead counts first and deletes only after you confirm.
- “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.”
- “Send the agent’s emails from our own address.” - connect a mailbox from the chat: Gmail or Outlook return the same consent link as Add mailbox in the app, or add a custom IMAP/SMTP account. Until one is connected, email still goes from no-reply@voicelogica.ai, now with Reply-To set to your own address, and the assistant tells you how to connect a mailbox.
- “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.
Under the tiles, Choose what it uses by default sets the SIP trunk, AI agent and Calendar used when a request does not name one. The SMS sender row shows your company’s default SMS sender; it applies to every SMS, so you change it in Telephony → SMS senders.
What you see in the chat
Section titled “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
Section titled “Go live from the chat”Pick a plan. “We want to go live.” You get the plans; choose one.
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.
Get a line. Companies in Greece can order their free number. Otherwise connect your PBX or your 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
Section titled “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
Section titled “Connect your PBX from Claude”Most office phone systems connect by registering a trunk out to Voice Logica: no port forwarding, no public IP.
Ask. “Connect my Panasonic PBX to my agent.” It creates the connection and gives you the server, port, username and password.
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.
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
Section titled “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 page, driven from the chat.
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.
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.
Device online. Tell it when the installer finished. It checks the device: online, tunnel up, and any PBX it found on the LAN.
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.
How the tools are organised
Section titled “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: <area>_query reads, <area>_execute changes. Called without an action, <area>_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 |
feature_requests_* | Feature requests: list and search, read one, add one (similar ones are shown first), add or remove your vote |
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, delete campaigns with their leads (list first, then confirm) |
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
Section titled “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. An area set to view in your role (for example Agents: view) can be read but not changed: the assistant is not given the tool that changes it. 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. No sign-in needed.
Troubleshooting
Section titled “Troubleshooting”Why does Claude or ChatGPT say it has no Voice Logica tools?
- The connector is added and signed in (Claude: Customize - Connectors shows it connected).
- ChatGPT: Developer mode is on, Voice Logica is listed under Plugins - Installed, and it is turned on in this chat (+ in the message box).
- The tile on Integrations - AI Assistants is not Disabled (use Re-enable).
Why does Claude or ChatGPT show another company's agents?
You are signed in to a different Voice Logica company. Ask Claude or ChatGPT to list your companies and switch, or switch company in the app and reconnect.
Why does Claude or ChatGPT say access denied for telephony or edge devices?
Your Voice Logica role does not include telephony or edge devices. Ask a company admin to do it for you, or to raise your access under Team and access.
Why can Claude or ChatGPT read my agent but not change it (or say a save failed)?
Your role lets you view that area but not change it, so the assistant has no tool to make the change and nothing was saved. Voice Logica tells the assistant this, so it should answer “your role does not allow it”. If it says a save failed instead, the cause is still the same.
Ask a company admin to set that area to edit for you under Team and access - Users (for the prompt, greeting and settings: Agents - edit), then start a new chat or reconnect the assistant so it gets the new tools. Or ask the admin, or your Voice Logica account manager, to make the change.
