MCP | Power Omni Docs

The MCP connector allows you to connect a Power Omni agent to a server compatible with the Model Context Protocol.

In practice, it acts as a bridge between the agent and external tools. These tools can be hosted on your own server, exposed through an MCP-compatible API, or provided by a third-party service.

When should you use the MCP connector?

Use the MCP connector when you already have an MCP server available and want to allow the agent to execute the tools published by that server.

Some examples of use cases:

retrieving data from an external system;
performing actions through your own API;
integrating the agent with internal company tools.

This connector is intended for more technical scenarios where an MCP server already exists for a system used by the company, or where a team is responsible for creating and maintaining that server.

How it works in Power Omni

When creating the connector, you provide the MCP server URL, define a name for the server, choose the authentication type, and configure which tools can be used.

You can also forward the authenticated user's email address from Power Omni to the MCP server. This can be useful when the server needs to identify which user initiated a specific request.

Creating an MCP connector

To create an MCP connector, go to:

Settings → Artifacts → Connectors → Create Connector

Then select:

MCP Server

Fill in the fields according to the server you want to connect.

Connector fields

Field	How to fill it in
Connector Type	Select `MCP Server`.
Project	Select the project where the connector will be created.
Name	Enter a simple name to identify the connector in Power Omni.
Description	Explain when and how the agent should use this connector.
Server Label	Enter a unique identifier for the MCP server. Example: `my_mcp_server`.
Server URL	Enter the MCP endpoint URL. Example: `https://example.com/api/mcp`.
Authentication	Select `None` or `API Key`, depending on the server.
Send logged-in user's email	Enable this option when the authenticated user's email needs to be sent to the MCP server.
Email header name	Enter the HTTP header name used by the server to receive the email address.
Allowed Tools	Define whether the connector can use all tools, only selected tools, or no tools from the server.
Approval Policy	Define how MCP tool calls must be approved before execution.

Server Label

The Server Label is the identifier used to recognize that MCP server.

Use a short name, without spaces, that is easy to understand.

Examples:

github_mcpfinance_mcpcrm_mcpmy_mcp_server

Ideally, the name should indicate which system or purpose the MCP server represents.

Server URL

The Server URL must point to the remote MCP endpoint.

Example:

https://example.com/api/mcp

The endpoint must be accessible from Power Omni.

If the URL is protected by a private network, firewall, IP restriction, or an authentication method that is not supported by the connector, communication with the server may fail.

Authentication

Power Omni allows you to configure the MCP connector without authentication or by using an API Key.

None

Use this option when the MCP server does not require a key, token, or other credential.

This mode can be used, for example, with public servers or environments where endpoint protection is handled by another layer.

API Key

Use this option when the MCP server requires an access key.

When you select API Key, Power Omni will display the connection configuration section.

You can import an existing connection or create a new one.

To create a connection, provide:

Connection Name

Enter a name to identify the credential.

Token / API Key

Enter the key or token required by the MCP server.

Send logged-in user's email

Enable Send logged-in user's email when the MCP server needs to identify which Power Omni user made the request.

When this option is enabled, the authenticated user's email address is sent to the MCP server with every tool call.

This feature can be used in scenarios such as:

identifying the user in the target system;
applying permissions or access rules;
filtering information based on the user;
recording audit information for executed operations.

The user does not need to manually provide their email address during execution. Power Omni retrieves this information from the authenticated user and automatically fills in the value.

Email header name

When email forwarding is enabled, the Email header name field becomes available.

This field defines which HTTP header the MCP server will use to receive the user's email address.

By default, you can use:

PowerOMNI-User-Email

In this scenario, a request may reach the MCP server with a header similar to:

PowerOMNI-User-Email: user@company.com

Only the header name is configured on this screen.

The value is automatically filled in by Power Omni with the authenticated user's email address and cannot be manually defined by the user.

If your MCP server expects a different header name, change the field to match the name used by your application.

For example:

X-User-Email

In this case, Power Omni will send:

X-User-Email: user@company.com

The MCP server must be prepared to receive and interpret the configured header.

Allowed Tools

The Allowed Tools setting controls which tools provided by the MCP server can be used by the agent.

Power Omni provides three options.

All tools

Allows the agent to use all tools provided by the MCP server.

This option is useful when the agent can use the entire set of tools available on that server.

Selected tools only

Allows you to individually select which MCP server tools can be used.

This option is useful when the server provides several tools but the agent should only have access to some of them.

For example, a server may provide:

get_customerlist_orderscancel_orderupdate_customer

If the agent only needs to retrieve information, you can allow:

get_customerlist_orders

The remaining tools will not be available to the agent.

No tools

Prevents the agent from using any tools provided by that MCP server.

This option can be used when the connector needs to remain configured but its tools should not be available for execution at that time.

Approval Policy

The Approval Policy defines whether a call to an MCP tool can be executed automatically or must go through an approval step.

When the option is configured as:

Never (automatic execution)

tools can be executed without requesting approval before each call.

The approval policy should be selected based on what each tool is allowed to do.

Testing the connector

After saving the connector, associate it with an agent and run a few simple tests.

You can start by asking:

Which tools are available?

Check whether the tools shown match the configuration defined under Allowed Tools.

Then test a specific tool.

Example:

Retrieve customer João's information using the available tool.

If you enabled Send logged-in user's email, also check the MCP server to confirm that the configured header is being received correctly.

For example:

PowerOMNI-User-Email: user@company.com

Need help?

If you have questions about configuring an MCP server, validating authentication, defining allowed tools, configuring user email forwarding, or choosing an approval policy, contact Power Omni support.