BoomTown (OvationCXM) MCP. Manage customer journeys, issues, and teams in chat.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
BoomTown (OvationCXM) MCP Server connects your AI agent directly to your customer journey and support systems. Use it to list all customer journeys, check specific customer profiles, or track support issues across teams.
It lets you orchestrate customer onboarding and support workflows using natural conversation, right from your AI client.
What your AI agents can do
Get customer
Retrieves specific profile data for one customer.
Get issue
Retrieves all details for a specific support case or issue.
Get journey
Retrieves all details about a specific customer journey.
List all customer journeys and retrieve detailed status information for any specific journey ID.
List all support issues or retrieve the full details of a specific case ID.
List all end-users or get a deep profile for a single customer ID.
List all associated organizations or get details for a specific company ID.
List all support teams or get details about a specific team, including members.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
019d7561get customer
Retrieves specific profile data for one customer.
019d7561get issue
Retrieves all details for a specific support case or issue.
019d7561get journey
Retrieves all details about a specific customer journey.
019d7561get organization
Retrieves details for one organization or company.
019d7561get team
Retrieves details for a specific support team.
019d7561list customers
Lists every customer and end-user in the system.
019d7561list issues
Lists all open support issues or support cases.
019d7561list journeys
Lists all active and completed customer journeys.
019d7561list organizations
Lists all organizations linked to your account.
019d7561list teams
Lists all support teams available for assignment.
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 BoomTown (OvationCXM), then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ 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
What you can do with this MCP connector
BoomTown (OvationCXM) MCP Server - Customer Journey Ops connects your AI agent straight to your customer journey and support systems. You'll use it to list all customer journeys, check specific customer profiles, or track support issues across teams. It lets your agent run customer onboarding and support workflows using natural conversation, right from your AI client.
Audit Customer Progress
- You can list all active and completed customer journeys using
list_journeysand then pull detailed status info for any specific journey ID usingget_journey.
Manage Support Cases
- You'll list every open support issue or support case with
list_issues, and you can grab all the full details for a specific case ID usingget_issue.
Inspect Customer Profiles
- You can list every customer and end-user in the system with
list_customers, or you'll get a deep profile for a single customer ID usingget_customer.
View Organizational Structures
- You'll list all associated organizations with
list_organizations, and you can pull details for a specific company ID usingget_organization.
Check Team Assignments
- You can list all support teams available for assignment with
list_teams, and you'll get details about a specific team, including its members, usingget_team.
How BoomTown (OvationCXM) MCP Works
- 1 Subscribe to the server and enter your BoomTown API Token and Secret.
- 2 Your AI client connects and authenticates against the server.
- 3 You prompt the agent using natural language (e.g., 'What is the status of case ABC-123?').
The bottom line is, your AI agent handles the API calls and data retrieval, so you just talk to it.
Who Is BoomTown (OvationCXM) MCP For?
This is for CX Operations teams and support managers who need a single view of the customer lifecycle. If your job involves cross-referencing a customer's history against their current journey status and open issues, this server saves you hours of manual dashboard searching.
Monitors active support cases and checks partner performance across multiple systems without leaving their main workflow tool.
Verifies a customer's progress through a multi-stage journey by checking journey status and associated organizational data.
Needs to quickly check journey statuses and team assignments by querying the data directly from their AI client.
What Changes When You Connect
- Check journey status immediately. Instead of clicking into the manual dashboard, you can ask the agent to run
get_journeyto see the current stage and activities for a customer. - Centralize support visibility. Use
list_issuesorget_issueto get a full case history for a customer, pulling data that usually lives in a separate ticketing system. - Know who's involved. Use
list_teamsorget_teamto verify which team owns a customer or which partner organization is assigned to a specific journey. - Get the full picture. Run
list_customersand thenget_customerto pull detailed end-user profiles and intelligence, skipping the need for manual data stitching. - Audit the entire flow. You can use
list_journeysto see every active journey, then drill down withget_journeyto verify exactly where a customer is in the onboarding process.
Real-World Use Cases
Customer stalls mid-onboarding
A specialist notices a customer is stuck. They prompt the agent: 'What is the status of Enterprise X?' The agent runs get_journey and sees the customer is stuck at the 'Payment Verification' stage. They then run get_customer to find the primary contact's phone number, and immediately flag the issue.
Support ticket requires context
A manager gets a new case ID. Instead of opening the ticketing system, they ask the agent: 'Show details for case ABC-123.' The agent uses get_issue and gets the full history, including which team was assigned and when it was created.
Need to check partner scope
An ops analyst needs to know which departments are involved. They run list_organizations to see all partners, then use get_organization to check if the target company has the necessary permissions before proceeding.
Team assignment is unclear
A support agent is unsure who should handle a complex issue. They ask the agent to list_teams to see all available departments, and then use get_team to check the specific criteria needed for the issue.
The Tradeoffs
Jumping between dashboards
Opening the CRM for customer data, then switching to the ticketing system for issues, and finally checking the dedicated journey dashboard. This takes 10+ clicks and context switching.
→
Use your AI client to ask the agent for a unified view. First, run list_customers to find the ID, then use get_customer and get_issue in sequence to pull all related data in one conversational flow.
Guessing the right data view
Trying to find a customer's journey status by searching the general issue queue, which only shows the case ID, not the stage they are in.
→
Always start by listing or retrieving the journey first. Use list_journeys to get the correct journey ID, then run get_journey to see the accurate stage and activities.
Over-relying on one data source
Finding a customer profile via the CRM, but missing out on open support issues because the CRM doesn't sync that data.
→
Check both ends. Get the customer data with get_customer, and then immediately follow up by running list_issues to ensure no open support cases were missed.
When It Fits, When It Doesn't
Use this server if your job requires synthesizing data from three or more distinct business domains—customer profiles, support tickets, and process workflows—in a single query. You need to know why a customer is stuck (journey status) and who owns the resolution (team/organization data).
Don't use this if you just need a simple list of IDs (use a basic list tool). Don't use it if you only need to read data from one system (use a single-domain tool). This server is for cross-functional data assembly.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by BoomTown (OvationCXM). 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.
Available Capabilities
Getting a complete customer view means jumping between 3-4 separate dashboards.
Today, finding out what's happening with a client means logging into the CRM to check their profile. Then you have to open the separate ticketing system to see if they have open issues. After that, you open the journey map to see if they've hit a roadblock. It's a copy-paste nightmare just to get a basic status report.
With this MCP server, you ask your agent for the status. The agent runs `get_customer` for the profile, then `list_issues` for open tickets, and finally `get_journey` for the status. You get all the data, structured and ready to use, without ever leaving your chat window.
BoomTown (OvationCXM) MCP Server: Access full customer intelligence.
You no longer need to manually cross-reference the team ID from the support system against the organization ID in the billing system. The server handles that linking for you.
You get a single, conversational data pipe. It connects the customer, their journey, their team, and their issues into one unified response. That's the difference.
Common Questions About BoomTown (OvationCXM) MCP
How do I list all customer journeys using the list_journeys tool? +
You simply call list_journeys. This returns a list of every journey ID and name you have active or completed in the system.
Can I find details for a customer using the get_customer tool? +
Yes, get_customer takes a specific customer ID and returns their detailed profile, including end-user data managed in CXMEngine.
What is the difference between list_issues and get_issue? +
list_issues gives you a list of all open support cases. get_issue requires a specific case ID to retrieve all the details for that one issue.
How do I check which team is responsible for an issue? +
You can use list_teams to see all teams, and then use get_issue to inspect the details of a case, which shows the assigned team.
How do I list all organizations using the list_organizations tool? +
The list_organizations tool returns a list of all organizations in your ecosystem. You'll get names and unique IDs for every entity, which lets your agent then fetch specific details using get_organization.
What is the purpose of the get_team tool? +
The get_team tool retrieves specific details about a single support team. This is useful for finding team structures, contact details, or knowing which team handles a specific type of issue.
Can I find out which customers are associated with a specific journey ID using the get_journey tool? +
The get_journey tool provides details about a customer journey itself. If you need to know who is on that journey, you'll use the list_customers tool and filter by the journey ID.
Does the list_customers tool handle filtering by status? +
Yes, the list_customers tool accepts filters for status, allowing you to narrow the results. You can check for 'Active' or 'Suspended' users to get a focused list of end-users.
Can I check the status of a customer's onboarding journey? +
Yes! Use the get_journey tool with the Journey ID. Your agent will fetch the current stage and completed activities for that specific customer journey.
How do I see which team is assigned to a specific support case? +
Simply ask the agent to get_issue and provide the Issue ID. It will retrieve the case details, including the assigned team and its current status in the ecosystem.
Does the integration allow creating new support issues? +
Currently, the toolset is focused on querying and monitoring (Read-Only). You can list and inspect journeys, teams, and issues, but creating new records must be done through the OvationCXM platform for full workflow control.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
ChatBot.com
Manage conversational AI and bot workflows via ChatBot — track stories, interactions, and user data directly from any AI agent.
Wati
Send WhatsApp messages at scale with official API access, chatbot automation, and shared team inbox for business conversations.
Userback
Collect visual feedback from users with annotated screenshots, screen recordings, and bug reports embedded in your product.
You might also like
Zoho Desk
AI-powered helpdesk: manage tickets, contacts, and support workflows via agents.
Channable
Manage marketplace orders and stock via Channable — track sales, update shipments, and monitor returns directly from any AI agent.
TestRail
Browse TestRail suites, parse manual test specs, and monitor active runs seamlessly native within your conversational AI workflow.