Integrations

Modern organizations rely on a broad ecosystem of tools, from document repositories like SharePoint and Google Drive to project management platforms like Jira and Linear, support desks like Zendesk, and internal databases. Omnifact centralizes these connections in one unified administration hub under Team Settings > Integrations. Through the Integrations hub, administrators control external data access and autonomous agent capabilities across two distinct models:

1. Document Access and Connected Sources: Connect enterprise cloud storage services so can index folder structures directly into knowledge bases, and team members can import files into chat conversations.
2. Agent Capabilities and Model Context Protocol (MCP): Connect external business systems, SaaS platforms, and custom APIs so the can search records, summarize information, and execute authorized actions in real time.

​

The Integrations Interface

The Integrations section is organized into two primary tabs:

• Installed: Displays every active integration in your workspace, including connected cloud storage providers and enabled MCP servers. Each entry shows current connection status, active user counts, or enabled tool counts, and provides direct access to configuration and governance settings.
• Catalog: A searchable marketplace of curated, pre-configured integrations ready to install in a few clicks.

In the top right corner, the + Add custom MCP button lets administrators connect any self-hosted or third-party server running over the open Model Context Protocol standard.

​

Exploring the Integrations Catalog

The Catalog tab provides access to more than 35 curated integrations spanning popular enterprise software categories.

​

Categories and Search

You can quickly locate integrations using the search bar or by filtering across nine dedicated categories:

• Files & Documents: SharePoint, OneDrive for Business, Google Drive, OneDrive, Google Docs, Google Sheets, Google Slides, Box, and Egnyte.
• Knowledge & Data: Notion and Airtable.
• Communication: Slack, Zoom, Gmail, and Google Chat.
• Productivity: Google Calendar and Todoist.
• Project Management: Atlassian (Jira and Confluence), Asana, ClickUp, and Linear.
• Sales & Service: HubSpot and Zendesk.
• Finance & Payments: Stripe and PayPal.
• Design: Miro, Canva, Lucid (Lucidchart and Lucidspark), and Webflow.
• Development: GitLab, GitHub, Sentry, PostHog, Supabase, and Neon.

​

Understanding Integration Types and Badges

Each card in the catalog highlights key characteristics of the integration through visual badges:

• MCP: Indicates an agent tool integration that connects over the Model Context Protocol, giving chat agents interactive skills to interact with that platform.
• Document access: Indicates a cloud storage integration used for syncing folder contents into Spaces or attaching files from connected accounts.
• Per-user sign-in: Indicates that after an administrator installs the integration, individual team members must authenticate with their own personal accounts under Account Settings > Connections before using its tools in chat.
• Added: Confirms that the integration is already installed and active in your workspace.

​

Adding an Integration from the Catalog

Installing a curated integration takes only a few steps and requires no manual schema configuration.

​

Connecting Custom MCP Servers

If your organization uses proprietary databases, custom internal APIs, or third-party tools that are not listed in the curated catalog, you can connect them directly as custom MCP servers. Click + Add custom MCP in the top right corner (or select Something else? at the bottom of the catalog) to open the setup modal. You can configure any remote streamable HTTP endpoint using:

• OAuth: With automatic client registration or custom credentials.
• API key: A shared secret passed with every request.
• Bearer token: A static Bearer authorization header.
• Custom header: A custom header name and secret token.
• None: For unauthenticated public or testing endpoints.

​

Managing Installed Integrations

The Installed tab lists all active integrations in your workspace. Clicking any entry opens its dedicated management view. Depending on whether the integration provides document access or MCP agent capabilities, the settings page offers specific controls:

​

Managing Connected Sources (Document Access)

For file storage integrations such as SharePoint, Google Drive, OneDrive, and OneDrive for Business:

• Usage: Displays the number of team members who have connected their personal accounts.
• User Account Connections: Outlines how team members link their personal storage accounts under Account Settings > Connections.
• Admin Consent: For Microsoft services (SharePoint, OneDrive, and OneDrive for Business), organizations often require administrative approval before users can connect. Team administrators can click Grant admin consent directly on the page to grant tenant-wide consent across their Microsoft 365 directory. For step-by-step guidance, see the Microsoft Admin Consent guide.
• Removing an Integration: Click Remove in the top right corner to disable the integration for the entire organization. Removing an integration revokes access for all users and halts document synchronization for any Space folders connected to that provider.

​

Managing MCP Servers and Tool Governance

For MCP servers such as DeepWiki, Atlassian, Slack, or custom endpoints:

• Tool Access Policies: Every discovered tool can be assigned one of three execution policies:
  • Always: Safe, read-only tools run autonomously without prompting the user.
  • Approval: State-changing operations pause execution and prompt the user in chat via an interactive approval banner.
  • Disable: Completely hides the tool schema so AI models cannot see or invoke it.
• Editing Details: Click Edit to update the display name, customize the slug prefix (which prefixes tool names for the AI model), or adjust custom OAuth app credentials.
• Removing a Server: Open the dropdown menu next to Edit and click Remove to delete the MCP server from your workspace.

​

How Your Team Uses Integrations

Once administrators configure integrations in Team Settings, team members can leverage them across Omnifact:

• Connected Sources in Spaces: Space Admins connect cloud storage folders directly to their Spaces. Files are automatically indexed, kept in sync, and searched during conversations. See Connected Sources.
• Attaching Files in Chat: When starting or continuing a conversation, users can attach files directly from connected Google Drive, OneDrive, or SharePoint accounts. See Attaching Documents.
• Invoking MCP Tools in Conversations: For OAuth-backed integrations, team members link their personal accounts in Account Settings > Connections. Once linked, chat agents automatically invoke enabled tools when answering questions or executing tasks, operating strictly within each user’s existing permissions.

​

Privacy and Security Considerations

Omnifact is built privacy-first, but external integrations involve distinct data flow boundaries:

• Cloud Storage Document Filtering: In contrast to MCP tool execution, documents imported from cloud storage into Spaces are processed by the Privacy Filter during indexing and retrieval, ensuring sensitive information is protected before reaching AI models.
• Least Privilege Tool Enablement: By default, newly discovered MCP tools should be set to Disable or Approval until verified by an administrator.
• SSRF Protection: Omnifact validates all custom MCP endpoints to prevent requests to loopback addresses, internal subnets, or cloud metadata services.

​

Related Resources