Omeda MCP Overview

Overview

The Omeda connector lets you work with your Omeda data by talking to an AI assistant such as Claude. You can ask about results and take routine actions in Omeda without leaving the conversation.

The connector works with live data from your Omeda account. The assistant sees only the databases, deployments, and audiences your Omeda user can already access, and every action runs as you.

The connector currently covers email: reporting on deployments, and building and testing new ones. To see what you can ask for and which tools are available, see Omeda MCP - Email.

Supported AI assistants

The Omeda connector is a remote MCP server, so it works with AI assistants that support remote MCP connectors with OAuth sign-in.

Omeda tests the connector with the supported assistants. Assistants differ in some behavior, such as when they ask before running a tool.

Before you start

You need three things:

• An Omeda user login for the databases you want to work with.

• MCP access on your Omeda user. Omeda turns this on per user. If you don't have it, contact Omeda support.

• A supported AI assistant. See Supported AI assistants above. If your organization uses a business plan for its assistant, an admin may need to allow the Omeda connector before you can add it.

The tools the assistant can use depend on the permissions on your Omeda user, so two people at the same company may see different tool lists.

Connect Omeda to your assistant

Claude

1. In Claude, open the connectors directory and search for Omeda.

2. Select Connect.

3. Sign in with your Omeda login when the Omeda sign-in page opens, and approve access.

4. In a conversation, turn on Omeda from the connectors or tools menu.

5. Ask a starter question to confirm it's working, such as "What database am I working in?"

You normally stay connected after signing in, but you may need to sign in again from time to time.

To disconnect, remove the Omeda connector from your Claude connector settings. Disconnecting stops any further access to your Omeda data. It doesn't remove Omeda information already returned in an existing chat.

Your database

Most Omeda logins have access to one database, and the connector works in it automatically. There's nothing to set up.

If your login can access more than one database, the assistant works in your default database or asks you to choose one. To work in another, ask the assistant to switch, for example: "Switch to the Acme database." To check where you are, ask "What database am I working in?" You can only switch to databases your login can already access in Omeda.

Confirmations and safeguards

Two different kinds of checks can happen before the assistant acts.

Tool permissions are set in your assistant. Omeda marks each tool as read-only or as making changes, and the assistant uses that to set default permissions, such as asking for your approval before a tool that changes data. In Claude, you can set each tool to Always allow, Needs approval or Blocked, and your organization may set restrictions you can't change. Depending on your assistant and your organization's settings, your defaults may differ. See Claude's connector documentation for details.

Confirmations in the conversation are separate. Before some actions, the assistant asks you to confirm a choice, such as which database to switch to or which audience query to use, even when the tool itself doesn't need approval.

Each area's article lists which of its tools change data.

Data and privacy

The connector is built and run by Omeda and reads and writes data only through Omeda's own APIs. Your Omeda permissions limit what the connector can access.

Omeda receives the information included in each tool request, such as a deployment ID, a date range or a new subject line. That can include information from your conversation, for example email content you ask the assistant to add. The connector doesn't receive your full conversation, only what the assistant sends in tool requests. What the tools return to the assistant, such as performance figures or clicker breakdowns, is handled under your AI provider's data terms.

Signing in uses OAuth, so the assistant never sees your Omeda password. Disconnecting the connector stops its further access.

Use of the connector is governed by Omeda's End User License Agreement. For how Omeda handles personal data as a company, see the Privacy Policy.

Troubleshooting

Get help

For questions about the connector, your access or a result that looks wrong, contact Omeda support through the Omeda Support Portal. Include the database, any deployment track IDs involved and what you asked the assistant, so support can reproduce it.

For problems with your AI assistant itself, such as signing in to it or its connector settings, use that provider's help center. For Claude, that's support.claude.com.

Table of Contents