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 the Installed tab with connected cloud storage and custom MCP servers, the Catalog tab, and the Add custom MCP button

​
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 agent 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, or choose from ready-to-connect servers in the Integrations Catalog.
1

Navigate to Integrations

Go to Team Settings > Integrations. Click + Add custom MCP in the top right corner (or explore pre-configured servers in the Catalog tab).
2

Enter Endpoint URL and Authentication

Enter your server’s Endpoint URL (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.As you enter the endpoint, Omnifact automatically tests connectivity, detects the supported authentication method, and preselects it:
  • OAuth: For services that support OAuth (such as HubSpot, GitLab, GitHub, Jira, or Salesforce). If the provider requires an app registered in their developer portal (such as GitHub, Slack, Box, or HubSpot), you can optionally expand Advanced settings, copy the Redirect URI, and enter your app’s Client ID and Client secret.
  • API key: Enter the API key shared across your team.
  • Bearer token: Enter the Bearer token.
  • Custom header: Specify your custom header name and secret value.
  • None: For unauthenticated public or internal test endpoints.
Team-Wide Access vs. Personal Sign-In: For servers using API key, Bearer token, Custom header, or None, authentication credentials are configured centrally by an administrator. Enabled tools are immediately available to all team members in their chat sessions; individual user- or group-level permissions are currently not supported for these authentication types. With OAuth servers, an administrator configures the endpoint for the workspace, but each user must individually link their own account in Account Settings > App Connections before the tools can be used in chat.
3

Validate Connection

Click Validate Connection (or Validate & Connect when using OAuth).For OAuth servers, a popup window opens for you to sign in and grant access. Omnifact connects to the endpoint, tests connectivity, and discovers the available tools and server identity metadata.
4

Review Discovered Identity and Tools

Once validated, Omnifact automatically discovers and prefills the server details:
  • Name: Automatically prefilled with the server’s reported name. You can customize the name if you prefer a different display label.
  • Slug: Automatically generated from the endpoint address or name to serve as a tool prefix in chat (for example, a slug of salesforce prefixes tools as salesforce__lookup).
  • Icon: Displayed automatically if provided by the server, with an option to remove it.
5

Save the Server

Click Add MCP Server to finalize the setup. Discovered tools are enabled by default, and you will be taken to the server details page to configure per-tool access policies.
Add MCP Server dialog with a Privacy Filter warning and endpoint URL field
For an OAuth server, select OAuth and click Validate & Connect. If the provider requires an app registered with the service, you can optionally expand Advanced settings to copy the Redirect URI and enter your credentials.
Add MCP Server dialog with OAuth selected, showing Advanced settings with the Redirect URI, Client ID, and Client secret fields
Best practice: Enabling an MCP server grants access to every tool that server exposes, including tools beyond the use case you have in mind. Enable a tool only when you actually need it, and leave the rest on Disable. Least privilege is safer than turning tools on just in case.

​
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:
DeepWiki MCP server details page listing tools with Disable, Approval, and Always 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 (or Connect & Save for OAuth) 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.

​
OAuth Servers and Account Connections

When an MCP server uses OAuth, the deployment model differs significantly from Bearer token or API key configurations:
  • Central server registration: Administrators add the MCP server endpoint in Team Settings. Omnifact automatically checks whether the server supports direct client registration or if a pre-registered OAuth app (with Client ID and Client secret in optional Advanced settings) is required. Signing in during setup tests the connection and discovers available tools.
  • Availability across the workspace: Once saved, the server is listed for all team members in Account Settings > App Connections (accessible directly at https://chat.omnifact.ai/account/connections) under the MCP Servers section.
  • Personal authentication required: Discovered tools are not automatically enabled for end users. Each team member must click Connect on the server card and authenticate with their individual credentials. Until they do, the card indicates: “Connect your own account to use these tools in chat. Until you do, their tools are not available to you.”
  • In-chat behavior: If a user asks the agent to perform an action using an OAuth tool that they have not yet connected (or if their authorization expired), the agent explicitly prompts them in chat to link their account under App Connections.
  • User permission boundaries: The agent executes tools exclusively within the permissions of the individual’s connected account in the target system (such as HubSpot, GitLab, or Jira). The tool list on the administrator’s server page reflects the administrator’s account permissions; other users see and execute only what their own account allows.
  • Admin connection status: If the administrator’s personal account is disconnected or its token expires later, the server page prompts them to click Connect Account before modifying tool configurations. Existing workspace connections and other team members’ access remain intact.
App Connections page in User Settings showing connected apps and the MCP Servers section with connected services

​
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 input.
  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 input asking to allow a Jira MCP tool, with Deny and Allow buttons
If a user denies the tool run, the agent 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.