Skip to main content

Set up the MessageGears MCP server

This guide walks through connecting an AI assistant to your MessageGears account with the MessageGears MCP server. You configure it once in your MCP client; after that, anyone using that client can work with MessageGears conversationally.

Version notice

The MessageGears MCP server requires Accelerator version 26.3.2 or later.

Availability

The MessageGears MCP server is available now. MessageGears professional services will help enable it for your account; contact your account team to get started.

Prerequisites​

  • An active MessageGears account on Accelerator version 26.3.2 or later.
  • The MCP server enabled for your account. MessageGears professional services handles enablement; contact your account team if you're not sure it's turned on.
  • Your usual MessageGears sign-in (the email and password you use for Accelerator). You do not need to create or paste an API key.
  • An MCP-capable AI client, such as Claude (desktop or IDE) or another MCP-compatible assistant.
  • A browser, for the one-time sign-in step.

Authentication​

The MessageGears MCP server uses OAuth 2.1, the standard sign-in flow for remote MCP servers. There is no API key to generate, copy, or store manually, the OAuth process will automatically handle this process.

Granting access​

The first time your client connects:

  1. Your client registers itself with the server automatically and opens a MessageGears sign-in page in your browser.
  2. You sign in with your normal MessageGears email and password.
  3. The browser hands a token back to your client, which stores it and reuses it from then on.

What this means in practice:

  • You never paste a credential into your client configuration. The only thing you configure is the server URL.
  • The assistant never sees your password or any API credential. Sign-in happens in your browser, not in the conversation, and the server exchanges it for its own internal credential that is never exposed to the assistant.
  • Your permissions are your own. The assistant acts as you, limited to the same roles and brand access your MessageGears user already has. It cannot see or do anything you can't.
  • The flow uses PKCE and short-lived tokens with refresh, so a captured authorization code is not reusable.
Sign-in gives the assistant your access

While your client holds a valid token, anyone using that client can act on your MessageGears account as you. Treat access to the client like access to your MessageGears login, and sign out of the server in your client when you're done with a shared machine.

Revoking access​

If a key needs to be deleted, this can be performed by the individual user by navigating within the UI:

  • By the user: Your name > Profile > API key
  • By a system admin: Admin > System > API key management

Connect your client​

Add the MessageGears MCP server to your client's MCP configuration. The URL is the only setting, and MessageGears provides the one for your account.

{
  "mcpServers": {
    "messagegears": {
      "url": "https://<your-messagegears-mcp-endpoint>"
    }
  }
}

Note there is no headers block and no key: authentication is handled by the sign-in flow described above.

Restart or refresh your client so it picks up the new server. On first use it opens the MessageGears sign-in page in your browser. Some clients add remote MCP servers through a Connectors or Add integration screen instead of a configuration file; if yours does, paste the same URL there.

Confirm the connection​

Ask the assistant something simple:

  • "Test the MessageGears connection."
  • "List my most recent campaigns."

The server includes a connection self-test, so the assistant can tell you directly whether the link is healthy. If the connection fails, check that the endpoint URL is correct and that you completed the browser sign-in. If your session has expired, your client prompts you to sign in again.