MCP
The MCP connector allows you to connect a Power Omni agent to a server compatible with the Model Context Protocol.
In practice, it works as a bridge between the agent and external tools. These tools may be hosted on your own server, in an API prepared for MCP, or in a service maintained by another provider.
When should I 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:
Query data from an external system.
Execute actions in your own API.
Integrate the agent with the company’s internal tools.
This connector is recommended for more technical scenarios, where there is already an MCP server available from a system or tool used by the company, or a team 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, if needed, limit which tools the agent can use.
At the moment, Power Omni allows MCP servers to be connected in two ways:
Without authentication, for public servers.
With API Key, for servers that require an access key.
Microsoft also recommends storing credentials in project connections instead of leaving fixed keys directly in the application code.
Creating an MCP connector
To create an MCP connector, go to:
Settings → Artifacts → Connectors → Create Connector
Then, select the Server MCP type.
Fill in the fields according to the server you want to connect.
Connector fields
Connector Type
Select Server MCP.
Project
Choose the project where the connector will be created.
Name
Give the connector a simple name to identify it in Power Omni.
Description
Explain when and how the agent should use this connector.
Server Label
Enter a unique identifier for this MCP server. Example: my_mcp_server.
Server URL
Enter the MCP endpoint URL. Example: https://example.com/api/mcp.
Authentication
Choose None or API Key, depending on the server.
Allowed Tools
Enter which tools from this server the agent can use. Leave this field empty to allow all tools.
Approval Policy
Define whether calls will run automatically or require approval.
Server Label
The Server Label is the identifier used to recognize that MCP server.
Use a short name, with no spaces, that is easy to understand.
Examples:
my_mcp_server
finance_mcp
crm_mcp
Ideally, the name should indicate which system or purpose that MCP represents.
Server URL
The Server URL must point to the remote MCP endpoint.
Example:
The server must be accessible. If the URL is protected by a private network, firewall, IP blocking, or unsupported authentication, the connector may not work correctly.
Authentication
Power Omni currently supports two authentication types for the MCP connector.
None
Use this option when the MCP server is public and does not require a key, token, or credential.
This mode is useful for tests, internal servers without authentication, or services that already have another protection layer before the endpoint.
API Key
Use this option when the MCP server requires an access key.
When selecting API Key, Power Omni will display the Connection Configuration area.
You can import an existing connection or create a new one.
To create a new connection, fill in:
Field
How to fill it in
Connection Name
Give the credential a name for identification.
Token / API Key
Paste the key or token required by the MCP server.
Allowed Tools
The Allowed Tools field lets you limit which tools from the MCP server the agent can use.
If the MCP server exposes multiple tools, you can allow only the ones required for that specific agent.
Example:
consult_customer list_orders create_ticket
This configuration helps reduce risks and prevents the agent from using tools that are not part of its purpose.
Approval Policy
The Approval Policy defines whether the agent can execute tools automatically or whether some type of approval will be required before the call.
In Power Omni, the Never option, which means automatic execution, allows the agent to execute the tool without requesting manual approval each time.
Use automatic execution only when the tool is safe for the agent’s flow.
We recommend requiring approval for higher-risk operations, especially when the tool writes data or changes resources.
Testing the connector
After saving the connector, associate it with an agent and run simple tests.
You can ask the agent:
What tools are available?
Then, test a specific tool from the MCP server.
Example:
Check João’s customer data using the available tool.
If the agent cannot use the tool, review the following points:
Whether the server URL is correct.
Whether the server is online.
Whether the API Key is correct.
Whether the tool is included in the Allowed Tools list.
Whether the agent is linked to the connector.
Whether the connector description clearly explains when it should be used.
Need help?
If you have any questions about configuring an MCP server, validating authentication, filling in the fields, or understanding which tools should be allowed for the agent, contact Power Omni Support.
Last updated