Skip to main content
The MCP server exposes over 140 tools across 25+ domains. Every tool listed here is available from any MCP-compatible client.
Ask your AI assistant “What OpenCX tools do you have?” — it will enumerate all available tools live.

Conversations

AI Configuration

Knowledge

Channels

Operations

Use list_team_categories or create_team_category to find a category ID, then set category_id with update_team_settings. Send null to clear it. Categories organize teams without changing their routing. Category reads require teams:read; creation requires teams:write.Use list_office_hours to find a schedule, then set support_office_hours_id; null restores the workspace default. Schedules and categories must belong to the current workspace. Set support_assignment_strategy and auto_assign_interval_seconds to configure assignment. Pacing accepts 0 to turn it off or whole seconds from 15 to 3600.To configure call routing, first use get_team to review the current settings, then call update_team_settings with the team ID and only the settings to change. This requires both teams:read and teams:write. Omitted settings stay unchanged; it does not add members, change their availability, or set organization-wide auto-answer.
Ring timeout accepts 10–120 seconds; maximum wait accepts 30–3,600 seconds. Wrap-up accepts 0–3,600 seconds: 0 disables it and null inherits the organization setting. Distribution accepts longest_available or fewest_answered_today. Enabling Support does not make an unstaffed or unavailable team ready to answer calls. See inbound calls for routing prerequisites.
Custom variables are authored in the OpenCX dashboard (Settings → Macros → Variables); the API and MCP surface them read-only via list_macro_variables. Macro attachments are also authored in the dashboard and returned read-only by list_macros and get_macro. Options can be set with create_macro and update_macro: update_macro takes the full list, so keep an option by passing its id and leave one out to remove it.

Analytics

Compliance and Audit


Prompt Library

Ready-to-use prompts by domain

Workflows

Multi-step scenarios that chain prompts together

Get Started

Connect the MCP server to your AI client

Troubleshooting

Common issues and how to resolve them

Contact segment management

Use create_contact_segment, update_contact_segment, and delete_contact_segment to manage saved contact filters. These tools require segments:write. Companion makes them available to users with contact write permission. Updates change only supplied fields; supplying a definition replaces the complete filter rules. Membership recalculates in the background after creation or filter changes. Deletion removes the segment and its memberships while keeping contacts, and does not rewrite references in other configurations. Use list_contact_segments, get_contact_segment, list_segments_for_contact, and check_contact_in_segment to inspect definitions and membership with segments:read. See contact segments for examples.