BoomTown (OvationCXM) MCP. Manage every customer step, case, and team assignment.
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) manages customer journeys and support operations. Connect this MCP to any AI client and manage everything from onboarding progress and team assignments to open support cases, all through natural conversation.
What your AI agents can do
Get customer
Retrieves detailed information for one specific customer record.
Get issue
Gets the full details and current status of a single support issue or case.
Get journey
Retrieves all data points for one specific customer journey path.
Get a full roster of every end-user or client in the system.
Pull up deep information on one particular customer profile, including their history and status.
See a bulk list of every active or closed support case across the ecosystem.
Get granular details on one specific support ticket, including assignment and status changes.
Check the current stage and activity timeline for a complex onboarding or activation path.
See a roster of every support team, like 'Tier 1' or 'Billing,' within your setup.
View the relationship and details for any company or partner organization listed in your system.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
BoomTown (OvationCXM): 10 Tools
These tools let your agent interact with core CX data: listing all customers, viewing specific journeys, tracking support cases, and mapping organizational structures.
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 BoomTown (OvationCXM) on Vinkius019d7561get customer
Retrieves detailed information for one specific customer record.
019d7561get issue
Gets the full details and current status of a single support issue or case.
019d7561get journey
Retrieves all data points for one specific customer journey path.
019d7561get organization
Gets the details and profile of a single company or organization.
019d7561get team
Retrieves information about one specific internal support team.
019d7561list customers
Lists all available customer accounts, giving you an overview of the user base.
019d7561list issues
Provides a summary list of multiple support issues or cases that need attention.
019d7561list journeys
Lists all defined customer journey templates and their current status across the user base.
019d7561list organizations
Outputs a list of every organization connected to your ecosystem.
019d7561list teams
Lists all support teams that are configured within the platform.
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,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 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.
The Dashboard Overload
Right now, if a customer calls about an issue during their onboarding process, someone has to check three different screens: the journey map dashboard for progress, the support ticketing system for open cases, and the organizational chart to see who owns that client. This means logging into four or five separate tools just to build a single narrative.
With this MCP, you ask your agent one question—like 'What’s wrong with Enterprise Alpha?'—and it pulls together the journey status, checks for open issues, and flags the correct internal team assignment. You get the whole picture instantly.
Reviewing Customer Data with `get_customer`
Previously, to check a client's details, you’d navigate through layers of menus: 'Clients > Search by ID > View Profile.' Every step required manual clicks and confirmation.
Now, your agent handles that whole process. You just ask for the customer profile, and it runs `get_customer` directly, spitting out the structured data you need without any extra friction.
What you can do with this MCP connector
Need a clearer view of your customers' entire lifecycle? This connection lets you talk to your OvationCXM data like it’s already in your agent's memory. You can track complex customer journeys—seeing exactly where they are and what stage they hit last. Need to know if a support case is stalled or who owns the next step? You get that visibility instantly, without opening dozens of dashboards.
It lets you check every member of an organization, see which teams are assigned to specific tasks, or pull up detailed profiles for any end-user. Because customer data moves fast and changes constantly, knowing exactly what happened when is everything. When you run these complex cross-platform queries, the Vinkius platform provides full visibility through its AI Analytics, so your agent always shows you which pieces of information it pulled in and how it used your budget.
You get a single source of truth for every customer interaction, from initial onboarding to final support resolution.
019d7561-3fca-70be-9d6e-4dfc4ea3b134 
How BoomTown (OvationCXM) MCP Works
- 1 Subscribe to this MCP, then enter your BoomTown API Token and Secret.
- 2 Connect it to your preferred AI client (like Cursor or Claude).
- 3 Ask your agent a question like, 'What is the status of customer X's journey?' and get an immediate answer.
The bottom line is you stop clicking dashboards and start asking questions in plain English.
Who Is BoomTown (OvationCXM) MCP For?
CX Operations Managers, Support Team Leads, and Onboarding Specialists. This MCP is for anyone who has to manually cross-reference customer data across a dozen different tabs just to answer one question.
Uses the MCP to verify where a key client stands in a complex, multi-stage onboarding process and report back on any roadblocks.
Uses the MCP to quickly pull lists of open support issues or check which team is assigned to handle an escalated case without logging into the ticketing system.
Uses the MCP to gather a high-level overview of all active organizations and their associated journey stages across multiple business units.
What Changes When You Connect
- Stop jumping between tabs. You can get a full list of all customers using
list_customers, then immediately useget_customerto pull their profile in one conversation. - Track complex onboarding progress instantly. Instead of digging through dashboards, you ask your agent about the journey status and get back the live data from
get_journey. - Support visibility is immediate. If a case needs attention, simply asking for support issues lets you view them via
list_issues, then drill down usingget_issueto see who owns it. - Understand your corporate structure at a glance. You can use
list_organizationsto map out all partners and companies without leaving your workflow tool. - Monitor internal resources easily. Need to know if the billing team is swamped? Use
list_teamsthen confirm their capacity withget_team.
Real-World Use Cases
Diagnosing a stuck onboarding flow
A specialist needs to know why Enterprise X hasn't completed its setup. They ask the agent, which uses list_journeys and then runs get_journey on the specific ID, identifying that the workflow stalled because an organization record was missing.
Triage a burst of support cases
A manager gets alerted to 50 new tickets. Instead of opening 50 separate dashboards, they ask for issues via list_issues, and the agent immediately summarizes which teams need to pick them up.
Mapping corporate dependencies
An account executive needs to know all associated partners for a major client. They ask to list organizations, using list_organizations to build an immediate map of connected entities.
The Tradeoffs
Searching manually by IDs
Copying 10 different customer IDs and running the get_customer tool ten times in a row.
→
First, use list_customers to get a filtered list of relevant clients. Then pass that resulting list to your agent for bulk analysis rather than calling individual getter tools.
Ignoring organizational context
Getting customer data without knowing which parent company or team is responsible.
→
Always start by running list_organizations and using get_organization to establish the context before querying specific user details.
Assuming perfect state
Asking for a journey status when the underlying team has changed ownership.
→
Always cross-reference the current assignment by running list_teams and then using get_team to verify who is currently responsible.
When It Fits, When It Doesn't
Use this MCP if your job involves tracking a customer's status across multiple distinct stages (onboarding, support, account setup) or managing operational data that lives in a dedicated CX platform. Specifically, if you need to list resources like customers or issues before you look up the details of one specific record, these listing tools are essential. Don't use this MCP if your goal is simply to read a static report or pull basic contact information from an email system; those general data connectors handle that better. If your workflow requires complex automation across billing and messaging platforms, remember that the real power comes when you chain multiple MCPs together using Vinkius.
Common Questions About BoomTown (OvationCXM) MCP
How do I list all active journeys using list_journeys? +
You ask your agent to use list_journeys. It gives you a roster of every journey template available in the system, letting you know what paths customers can take.
What is the difference between list_customers and get_customer? +
list_customers shows you a summary table of everyone. get_customer requires a specific ID and gives you all the deep, detailed data for just that one person.
Can I find out which teams are assigned to an organization using list_organizations? +
You use list_organizations first to get the company context. Then, your agent can cross-reference that with list_teams to see who handles accounts like theirs.
If I need current support cases, should I use list_issues or get_issue? +
Use list_issues when you want a broad overview of all open tickets. Use get_issue only if you know the exact case ID and need to see its full history.
What credentials do I need to successfully run a query using get_team? +
You must connect with your BoomTown API Token and Secret. Vinkius handles passing these credentials through zero-trust proxies, so you never have to worry about storing them locally.
When I use list_customers, can the agent filter results by a specific date range? +
Yes, the tool accepts optional parameters for filtering. You can pass start and end dates to limit the customer records returned, making sure you only pull data from the necessary timeframe.
If I use get_journey with an ID that doesn't exist, what should I expect? +
The tool returns a standard 'Not Found' error code. This means the journey ID is wrong or inactive. Always double-check the identifier before running the query.
After listing organizations with list_organizations, how do I pull detailed information for one of those groups using get_organization? +
You pass the specific organization's ID retrieved from the initial list call into the get_organization tool. This ensures the agent pulls the correct, contextual data set.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.