Skip to main content
Connect Splash through Conversion’s hosted MCP wrapper to give AI chats and agents tools for events, guests, contacts, and registration forms.
To sync event details, RSVPs, and check-ins into a Conversion field event, use the separate Splash field event integration. The MCP server is its own connection and does not use that integration’s saved sign-in.

Set up Splash

Before you begin

  • A Conversion Administrator account to add the server.
  • A Splash Client ID and Client secret. Splash issues them through your Customer Success Manager. See Get your Splash API credentials. You can reuse the pair the field event integration uses.
  • The username and password of the Splash user the tools act as. The tools can see and change only what that user can, so a dedicated integration user works well.
  • Optional: a Splash CRM API key. Splash issues it separately from the Client ID and Client secret. Only event creation needs it.

Step 1: Write the client secret value

The server takes every Splash credential except the Client ID as one JSON value on a single line.
  1. Copy this template.
  2. Replace each placeholder with your own value.
  3. If you have no CRM API key, delete ,"crmApiKey":"YOUR_SPLASH_CRM_API_KEY". An empty value is rejected.
If a value contains a double quote or a backslash, put a backslash in front of it.
Conversion stores this value encrypted, password included, and sends it to the wrapper each time a member connects. The wrapper uses the username and password once to sign in to Splash and does not keep them. The field event integration works differently: it does not store the password.

Step 2: Add the server in Conversion

In Conversion, go to Settings → AI → Connections. Under MCP servers, click Add MCP server (or Add server below an existing list). Fill in the fields below. Keep credentials out of the server URL. The URL is the same for every Splash organization.

Step 3: Authorize the connection

  1. Click Add server.
  2. Click Connect on the Splash server.
  3. Confirm the server shows Authorized.
No Splash sign-in page appears. The wrapper checks the saved credentials with Splash. Each member must connect individually. Every connection acts as the Splash user in the JSON value, so all members get the same Splash access.

Tools

The server exposes 27 tools, one for each operation in Splash’s published API. On the server’s Tools tab, set each tool’s mode. See tool approval settings. Set the tools you don’t need to Disabled, starting with the ones that delete events, delete or anonymize contacts, and manage team users. Anonymizing a contact cannot be undone. A few tools behave in ways their names don’t show:
  • splash_create_event needs the CRM API key and the ID of an existing theme. Ask splash_all_events to include themes to find one.
  • splash_create_single_group_contact updates a guest whose status is added or invited. For a guest with any other status it creates a duplicate with the same email address, so look the guest up first.
  • splash_batch_cancel_rsvps cancels one guest’s RSVP by setting them to not attending. It does not delete the contact.
  • No tool designs an event page, edits a Splash email template, or changes a registration form. Splash’s API does not offer those.

Test the connection

  1. Open the server’s Tools tab and confirm Splash tools are listed.
  2. Start a Conversion AI chat and ask it to list up to three upcoming Splash events, without creating or changing anything.
  3. Approve the read-only tool call if prompted.
  4. Compare the returned titles with Splash. A successful empty result is valid for an organization with no upcoming events.

Limits

Splash allows two API requests per second per Client ID, shared by everything that uses those credentials. That includes the field event integration when both use the same Client ID. The wrapper does not pace or retry calls. A call over the limit returns Splash’s rate limit error. If a create call fails without a clear answer, check Splash before trying again, because the event or guest may already exist.

Troubleshooting

  • Not Found or Unreachable: check that the server URL is https://map.mcp.conversion.ai/splash/mcp and the transport is Streamable HTTP.
  • Connect fails: check that OAuth client secret is valid JSON on one line with only the fields from Step 1 and no empty values. If it is, Splash rejected the Client ID, Client secret, username, or password. Try signing in to Splash directly with the same username and password.
  • Event creation fails: add crmApiKey to the JSON value with Edit on the server page. Changing OAuth client secret removes every member’s connection, so each member clicks Connect again.
  • A tool reports that the access token expired or was revoked: choose Disconnect from the server’s options menu, then click Connect. If the Splash user’s password changed, update the JSON value first.
  • A tool fails after connecting: check what the Splash user can access and the error returned by Splash.
After correcting the settings, reconnect if needed and use Refresh tools on the server page. A tools list confirms discovery; a successful read-only call confirms access to Splash.