Skip to main content
Connecting workplace AI to internal software traditionally required custom API wrappers or closed vendor ecosystems. Omnifact natively supports the Model Context Protocol (MCP), an open industry standard that connects autonomous chat agents directly to your organization’s business systems, databases, and internal tools under complete administrative control. Because MCP is an open standard, your organization avoids vendor lock-in. You can connect off-the-shelf MCP servers provided by software vendors or deploy lightweight internal servers for proprietary databases. Because these integrations connect at the platform level, changing default AI models or adding new reasoning tiers never disrupts your existing connections.
Team Settings Integrations page showing cloud storage cards and the MCP Servers section with connected servers and enabled tool counts

​
How MCP Works in Omnifact

  1. Platform Connection: Administrators configure remote MCP server endpoints in Team Settings > Integrations.
  2. Automatic Tool Discovery: Omnifact connects to the server, queries its available capabilities, and registers the discovered tool schemas for agent use.
  3. Administrative Access Control: Administrators assign an explicit execution policy (Always, Approval, or Disable) to each discovered tool.
  4. Agent Invocation: When users interact with the assistant in chat, agents intelligently invoke enabled tools to look up live records, run calculations, or update systems.
  5. Interactive Confirmation: For sensitive tools configured for approval, the user reviews the exact request payload in chat before the action executes.

​
Adding an MCP Server

Team administrators can configure remote MCP servers over HTTP directly from the administration dashboard.
1

Navigate to Integrations

Go to Team Settings > Integrations. Scroll down to the MCP Servers section and click Add MCP Server.
2

Configure Identity

Enter the server identity details:
  • Name: A descriptive display name shown across the administration interface (for example, “Salesforce CRM” or “Internal Inventory API”).
  • Slug: A unique identifier containing only lowercase letters, digits, and hyphens (up to 24 characters). The slug serves as a model-facing tool prefix (for example, a slug of salesforce prefixes tools as salesforce__lookup).
3

Set Endpoint and Authentication

Enter the connection details:
  • Endpoint URL: A streamable HTTP MCP endpoint (for example, https://mcp.internal.example.com/mcp). Private network addresses, loopback addresses, and internal subnets are blocked by default to prevent unauthorized intranet requests.
  • Authentication: Choose your server’s authentication method:
    • None: For unauthenticated public or internal test endpoints.
    • API key: Sends the key in an API key header.
    • Bearer token: Sends standard Authorization: Bearer <token> authentication.
    • Custom header: Allows specifying a custom header name and secret value.
4

Validate Connection

Click Validate Connection. Omnifact tests connectivity to the endpoint and retrieves all exposed tools. If validation succeeds, you will see the list of discovered tools.
5

Save the Server

Click Add MCP Server to finalize the setup. The server will appear in your MCP Servers list.
Add MCP Server dialog with a Privacy Filter warning, endpoint URL field, and API key authentication

​
Per-Tool Governance and Access Policies

Opening internal systems to AI agents demands clear administrative boundaries. Omnifact gives IT teams complete authority over which tools run and how they execute. Click on any configured server in Team Settings > Integrations to view its tool management page. Every tool exposed by the server operates under one of three policies:
MCP server details page listing discovered tools with Always, Approval, and Disable access policies

Always

Runs safe, read-only lookups (such as documentation searches or customer status checks) autonomously without prompting the user.

Approval

Pauses state-changing operations and sensitive updates (such as updating records or sending emails) until confirmed in chat.

Disable

Keeps the tool off-limits and hides its schema so AI models never see or invoke it.

​
Managing Stale and Updated Tools

When connection settings or remote tools change:
  • Click Edit on the server details page and select Validate & Save to refresh the tool list.
  • Existing tools retain their configured access policies.
  • Newly discovered tools start in the Disable state by default until an administrator enables them.
  • Tools no longer reported by the remote server are grouped under a No longer reported section, where they can be removed individually or with Remove all.

​
Interactive In-Chat Approvals

For tools assigned the Approval policy, Omnifact prevents unauthorized state changes by placing a human in the loop. When an AI agent decides to run an approval-gated tool:
  1. Generation pauses, and an interactive Tool Approval Banner appears directly above the chat composer.
  2. The banner clearly identifies the tool name, target MCP server, and total actions queued (for example, “1 of 2 actions”).
  3. Users can expand the parameter view to inspect the exact argument payload before deciding.
  4. Users click Allow to permit execution or Deny to cancel the call.
Tool approval banner above the chat composer asking to allow a Jira MCP tool, with Deny and Allow buttons
If a user denies the tool run, the assistant receives an explicit denial status and continues the conversation, explaining that the action was cancelled without modifying any data.

​
Privacy Filter and Security Considerations

Omnifact is built privacy-first, but external integrations require special awareness:
Privacy Filter Bypass: Tool calls to external MCP servers communicate directly with your configured endpoints. External MCP tool calls bypass the Privacy Filter in both directions. Arguments sent to external MCP servers go out unfiltered, and returned tool results enter the conversation unfiltered. Only connect endpoints and servers that your organization trusts.
To ensure security across your workspace:
  • Server Authorization: Only administrators with access to Team Settings can add or edit MCP servers.
  • Default Disabling: Newly discovered tools are disabled until an administrator explicitly assigns an active policy.
  • SSRF Defense: Omnifact validates destination endpoints to prevent access to private network resources and metadata services.