Placetel MCP. Audit Calls, Users, and Devices in One Flow
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Placetel MCP Server connects your AI client to your Placetel PBX data. It lets agents programmatically list users, retrieve SIP endpoints, check active calls, and pull detailed call logs (CDRs) instantly.
Use it to automate tasks like auditing user groups or finding specific phone numbers without touching a dashboard.
What your AI agents can do
Get group
Gets the specific details for a defined Placetel user group.
Get sip user
Retrieves all technical information about a specified SIP endpoint.
Get user
Gets the account details for any single Placetel user.
Retrieve specific information about a user account by identifier.
List all available Placetel groups or get details for a single specified group.
Retrieve technical details for a specific SIP user account.
List all active or recent calls, or pull full Call Detail Records (CDRs) for billing/logging purposes.
Get a complete list of connected devices or all assigned phone numbers within the account.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
Placetel MCP Server: 10 Tools for Telephony Management
Use these dedicated tools to query Placetel data, from checking individual user accounts to listing massive call detail records.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Placetel on Vinkius019dd13cget group
Gets the specific details for a defined Placetel user group.
019dd13cget sip user
Retrieves all technical information about a specified SIP endpoint.
019dd13cget user
Gets the account details for any single Placetel user.
019dd13clist call detail records
Pulls comprehensive logs of every call made or received, including duration and parties involved.
019dd13clist calls
Shows a list of calls that are currently active or recently terminated.
019dd13clist devices
Lists every physical and soft device registered with the Placetel system.
019dd13clist groups
Returns a list of all existing user groups within your account.
019dd13clist numbers
Provides an inventory of every assigned phone number in the system.
019dd13clist sip users
Lists all registered SIP user accounts available on the PBX.
019dd13clist users
Retrieves a list of every active Placetel account user.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Placetel, then connect any of our 4,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Placetel. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Auditing call logs shouldn't take a spreadsheet export and several cross-references.
Right now, if you need to audit calls from last Tuesday, the process is a nightmare. You have to log into the dashboard, set the date range, hit 'Export,' wait for the file to generate, download it, and then open up potentially dozens of tabs just to cross-reference user IDs, group memberships, and device names against the call log.
With this MCP server, you skip all that. You ask your agent, 'Show me all failed calls from Group X last week.' The agent runs `list_call_detail_records` and gets a clean, structured payload back instantly. It's pure data, ready for analysis.
Placetel MCP Server: Get the full picture of users and endpoints.
Manually checking if an employee has been assigned a number or if their device is active requires jumping between multiple views. You check `list_users`, then you run to another tab, check `list_devices`, and finally try to locate the correct group in `get_group`—it's a time sink.
Now, your AI client handles that coordination. It can pull user data via `get_user` and immediately cross-reference it with device status from `list_devices`. You get one cohesive answer instead of three different screens.
What you can do with this MCP connector
The Placetel MCP Server plugs your AI client right into your PBX data. You never gotta log into some dashboard just to check basic info; you'll connect your agent and it instantly gets access to all core telephony functions. This lets your team automate tasks—like auditing who belongs in which group, or pulling a specific number's technical details—without touching a single portal button.
User Account Management:
You can get a rundown of every active Placetel user account using list_users, and if you know the ID, you'll pull all the specific account info with get_user. For group structures, it’s simple: use list_groups to see every existing user group name, then run get_group if you need the deep details on one specific membership.
System Inventory:
Need to know what numbers your company uses? You get a full inventory of all assigned phone numbers with list_numbers. To track hardware and software, list_devices gives you a rundown of every physical or soft device registered in the system. On the technical side, it’s no different: list_sip_users shows every SIP account available on the PBX, and if you're checking credentials for one specific user, get_sip_user pulls all that required technical information.
Group & User Details:
The server handles both general accounts and defined groups. You can use list_groups to see what group names are available across your account, and then you’ll pull the full details on a specific membership using get_group. For individual user records, finding an account's basic info is done with get_user, while checking out all active accounts starts by running list_users.
Call Auditing & Records:
When it comes to call data, you’ve got two main tools. First, if you just need a quick status check, list_calls shows you every phone call that's currently ringing or recently ended. For serious logging—like billing or compliance audits—you use list_call_detail_records. This tool pulls the full Call Detail Records (CDRs), giving you comprehensive logs of who called whom, how long it lasted, and which parties were involved.
You can also get a list of every registered SIP user account using list_sip_users.
Putting It Together:
This whole setup means your agent doesn't just check one thing; you're building an audit pipeline. For example, you can pull all the assigned numbers with list_numbers, then use that list to cross-reference against which users are active via list_users. You can get a full list of every device using list_devices and pair that up with checking the technical credentials for specific accounts through get_sip_user.
If you're tracking usage, your agent can first check live status with list_calls, then immediately jump back in time to review historical data by grabbing all the CDRs via list_call_detail_records. You never have to switch contexts or open a different tab; everything runs through this one connection. It’s built for deep, programmatic dives into your PBX infrastructure.
019dd13c-c726-720d-bd14-e6d9d9120e8b 
How Placetel MCP Works
- 1 You connect your AI client using an API Token and point it to the Placetel MCP endpoint.
- 2 The agent calls a specific tool function (e.g.,
list_call_detail_records) by telling it exactly what data you need. - 3 The server executes the call against Placetel's backend, processes the request, and sends back structured JSON data to your AI client.
The bottom line is that your agent gets a structured view of all Placetel data without requiring manual logins or complex API scripting.
Who Is Placetel MCP For?
Network Operations Engineers and Telecom Administrators. You're the one staring at 15 different dashboards, trying to figure out if that outage was a user error or a trunking issue. This tool lets your agent run all those cross-system checks in one prompt.
Uses list_call_detail_records and list_devices to quickly audit call failures or check the status of endpoints during an outage.
Manages user accounts by running get_user or list_users to verify permissions, change numbers, or confirm group memberships.
Runs list_call_detail_records and list_numbers periodically to generate verifiable logs for compliance checks.
What Changes When You Connect
- Instantly audit call history. Instead of downloading massive CSVs from a dashboard, run
list_call_detail_recordsto pull structured data directly into your agent for analysis. - Verify endpoints quickly. Need to know if John's desk phone is registered? Call
list_devicesand get the status immediately, eliminating manual portal checks. - Manage users by role. Use
get_grouporlist_groupsto check which users belong to specific call routing groups without guesswork. - See real-time activity. The
list_callstool gives an immediate snapshot of active calls—perfect for troubleshooting during a live outage. - Full inventory access. Run
list_numbersto audit your entire number pool, ensuring no numbers are missed when planning new extensions.
Real-World Use Cases
Troubleshooting an Outage
A call failed and the user only has a reference ID. Instead of manually cross-referencing that ID across the dashboard, the agent runs list_call_detail_records using the ID. The result immediately shows if the failure was due to a device issue or an incorrect number assignment.
Onboarding New Teams
The ops engineer needs to verify every user has the correct permissions. They run list_users to get all accounts, then call get_group for each department group to confirm proper role assignment before activation.
Billing Audit
Compliance requires proof of all calls made last quarter. The agent runs list_call_detail_records over the specified date range, automatically filtering and summarizing call duration and destination parties for the finance team.
Inventory Cleanup
The IT admin needs to decommission an old branch office's equipment. They run list_devices to get a definitive list of all associated endpoints, ensuring nothing is missed before powering down the physical gear.
The Tradeoffs
Relying on UI Search
Manually going into the Placetel portal, selecting 'Users,' then using the filter dropdown to narrow down results. This process takes several clicks and is prone to forgetting a necessary filter.
→
The agent calls list_users first; if you need specific data, use get_user with the ID. If you only want a list of available numbers, run list_numbers. Keep it in the chat.
Using General Dashboards
Opening the main dashboard to check if a number is active. The dashboard usually shows recent activity but not the current status or full details.
→
To check a specific phone number's status, run list_numbers. For detailed user setup data, use the targeted tool: get_user.
Assuming Data Correlation
Thinking that just listing all users (list_users) automatically shows which groups they belong to. That information is usually in a separate tab or dropdown.
→
To check group membership, you must explicitly call list_groups first, then use get_group if the user belongs to multiple departments.
When It Fits, When It Doesn't
Use this server if your core requirement is reading and structuring data about your telephony infrastructure (users, calls, devices, numbers). You need a programmatic way to answer questions like 'Who called X at Y time?' or 'Is endpoint Z active?'.
Don't use this if you need to change complex routing logic outside of basic API actions. For instance, updating the core billing structure or changing SIP trunking credentials typically requires access to the main Placetel backend configuration panel, not just a read-only MCP connection.
If your goal is simply to track general usage metrics (e.g., total calls this month), an external BI tool connected via standard API keys might be better than running list_call_detail_records every time.
Common Questions About Placetel MCP
How do I find out which devices are registered using list_devices? +
You simply call the list_devices tool. It returns a complete inventory, including device names and their current connection status (e.g., online/offline).
What is the best way to audit calls using list_call_detail_records? +
To get comprehensive logs, run list_call_detail_records. You can then filter this data by date range or specific user ID within your agent prompt for focused results.
Do I need to call list_users before getting details with get_user? +
No. While list_users gives you an overview, you can directly use get_user by providing the specific user ID or username to retrieve all their detailed account information.
How do I check if a group exists using list_groups? +
Call list_groups. This tool returns a comprehensive list of every defined group name. You can then use that name in the get_group function for full details.
How do I use list_numbers to check all available phone numbers? +
It lists every number tied to your Placetel account. The output gives you the number ID and its status, letting your agent quickly verify if a number is active or assigned.
What credentials does get_sip_user require for a specific SIP user? +
It requires the unique identifier of the SIP user. Your agent uses this ID to fetch detailed information, including associated devices and account status.
Are there performance limits when calling list_calls repeatedly? +
The Placetel API handles a large volume of call data. If your agent makes too many calls in rapid succession, you might hit rate limits; waiting about one minute usually resolves it.
What happens if I get an error using get_group? +
The tool returns a precise error code and message. This tells your agent exactly why the group lookup failed—whether it's due to an invalid ID or a permissions issue.
Where do I find my API Token? +
Your API Token can be found in your Placetel web portal under Integrations > Web API.
What access does this MCP need? +
It requires the REST API Token, giving access to users, calls, numbers, and devices.
Can I initiate phone calls using this server? +
Currently, this integration supports retrieving Placetel data like CDRs and configurations. Call initiation via CTI will be added in a future update.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.