IntegrationsMCP Connections

MCP Connections

Understand how the Model Context Protocol powers OptiAgent's tool access, and connect your own custom MCP servers.

The Model Context Protocol (MCP) is the layer that gives OptiAgent the ability to interact with external tools through natural conversation. Every integration that lets OptiAgent read, search, or write data in an external platform is powered by MCP under the hood.

This page explains how MCP works at a system level, how native and custom integrations differ, and how to connect your own MCP servers for tools that Optiverse doesn't natively support.

Choose the Right MCP Page

Optiverse supports two different connection directions:

Where to goWhat it connects
Homepage → MCPsConnect external services to Optiverse so the assistant can use their tools. Open the plug button labelled Manage connectors beside the message input to see MCP Integrations, then choose Custom Server or a supported provider. Older layouts show an MCPs tab.
Settings → MCP (/settings/mcp-server)Connect ChatGPT, Codex, Claude, or Cursor to Optiverse. This page provides the Optiverse MCP server URL and lists authorized AI clients. Setup steps: Optiverse MCP Server.

To add an external MCP server, use the homepage's MCP integration picker. The Custom Server dialog is available there, rather than under Settings → MCP or Settings → Integrations.

How MCP Works

MCP is an open protocol that standardizes how AI assistants communicate with external tools. When an MCP integration is active:

  1. The integration exposes a set of tools (read contacts, search deals, post a message, etc.)
  2. You ask OptiAgent a question or give a command in natural language
  3. OptiAgent selects the right tools to fulfill your request
  4. The tools execute against the external platform and return results
  5. OptiAgent combines the results into a single, coherent response

This means you never need to learn an API or memorize commands. You just ask for what you need and OptiAgent handles the tool orchestration.

Optiverse MCP integrations connecting to HubSpot, Salesforce, Slack, Teams, Notion, Jira, Linear, n8n, and more

Native vs. Custom Integrations

Optiverse provides two ways to connect tools via MCP:

Native IntegrationsCustom MCP Servers
SetupOne-click connect via OAuth or API keyProvide a compatible server URL and a required raw bearer token
Maintained byThe Optiverse teamYou or the tool vendor
ExamplesHubSpot, Salesforce, Pipedrive, Attio, Microsoft TeamsRemote Streamable HTTP MCP servers that accept a single bearer token
Tool curationPre-configured tool set with tested permissionsYou manage which tools are available
UpdatesAutomatic. New tools added as the integration evolvesYou control the server version

Native integrations cover the most common platforms and are optimized for reliability, token management, and permission controls. See the CRM, Communication, and Automation sections for setup guides.

Custom MCP servers fill the gaps when the server's transport and authentication match the supported connection options below. Publishing an MCP server alone does not guarantee compatibility with Optiverse.


Connecting a Custom MCP Server

The Custom Server dialog supports remote Streamable HTTP MCP endpoints that authenticate with a single bearer token. It currently requires an access token. General custom-server OAuth sign-in, additional HTTP headers, local command-based (stdio) servers, and legacy HTTP+SSE endpoints are not supported by this dialog.

Setup Steps

  1. On the Optiverse homepage, open MCPs using the plug button labelled Manage connectors beside the message input (or the MCPs tab in older layouts)
  2. Click Custom Server to open the connection dialog
  3. Fill in the required fields:
FieldDescription
Server KeyA unique identifier used as the tool name prefix (e.g., my-server)
Display NameA human-readable label shown in the UI (e.g., "My MCP Server")
Server URLThe HTTP endpoint of the MCP server (e.g., https://your-mcp-server.com/mcp)
Access token (required)Paste only the raw token value. Optiverse adds the Authorization: Bearer prefix automatically. Do not enter Bearer, Authorization:, JSON, or a different header name. An API key works here only if the server accepts it as a bearer token.
  1. Click Connect
  2. Reopen the server to discover and review its tools, then enable/disable individual tools as needed

The token field may be labelled Authorization Header in older screenshots. It still accepts only the raw bearer token, not an arbitrary HTTP header.

The Server Key becomes a prefix for all tools from that server. Choose something short and recognizable so you can identify the source when OptiAgent uses the tools.

Technical Requirements

Optiverse connects to custom MCP servers over Streamable HTTP, the standard remote transport for MCP. Your server must:

  • Expose an HTTP endpoint that supports POST and GET requests
  • Implement the MCP protocol (tool listing, tool execution, result responses)
  • Accept Authorization: Bearer <token> without requiring other authentication headers
  • Be reachable from Optiverse's backend, not only from your laptop or a private network

Compatibility depends on both transport and authentication. A working website URL, a REST API endpoint, or an MCP server that requires OAuth or extra headers cannot be connected through the generic bearer-token form alone. Streamable HTTP may use SSE responses; this does not add support for the separate legacy HTTP+SSE transport.

What Can You Connect?

A company-hosted MCP service that exposes documentation search or support-ticket tools over Streamable HTTP with one bearer token is a suitable candidate. Check the vendor's endpoint and authentication requirements before connecting. Prefer the provider's existing Optiverse integration when one is available.


Managing Tools and Permissions

Each MCP integration (native or custom) exposes multiple tools. You have granular control over what OptiAgent can do.

Tool-Level Toggles

After connecting a server, you can enable or disable individual tools. This lets you:

  • Allow read operations but block writes
  • Expose search tools but hide bulk operations
  • Limit access to only the capabilities your team actually needs

MCP integration showing available tools with toggle controls

Safety by Design

MCP integrations include built-in safety measures:

  • Delete operations are blocked by default. OptiAgent cannot delete records from any connected system.
  • Granular tool control. Enable only the specific tools you need, nothing more.
  • Audit visibility. Every tool call is visible in the conversation, so you can see exactly what OptiAgent accessed.
  • Permission customization available. If your team needs specific permission modes (like requiring confirmation before write operations), contact support@optiverse.ai to enable them for your workspace.

Before enabling write-capable tools on any integration, align with your team on which data OptiAgent should be allowed to modify. Start with read-only access and expand once you've validated the workflows.


Verifying a Connection Works

After connecting a custom MCP server, verify that it's working correctly:

  1. Go to the Multi-Meeting Search (homepage) or open any meeting page with OptiAgent
  2. Ask a simple question that would require the connected tool, for example:
    • "What tools do you have access to from [server name]?"
    • "Search [tool] for [something you know exists]"
  3. OptiAgent should respond using the connected tool and show the tool name in the response

If the connection fails:

SymptomLikely CauseFix
"Tool not found"Server saved but tools not discovered or enabledOpen Homepage → MCPs, reopen the server to discover its tools, and enable the required tools
Timeout or no responseServer URL unreachableVerify the URL is publicly accessible and the server is running
Authentication errorMissing/invalid token or unsupported authenticationEnter the raw bearer token without a prefix. The Custom Server form does not support OAuth or additional headers.
Custom Server is missing from Settings → MCPThe settings page connects AI clients to OptiverseOpen Homepage → MCPs using Manage connectors beside the message input
Unexpected resultsServer returns malformed dataTest the server independently to confirm it works

Best Practices

  1. Start with native integrations. If Optiverse has a native integration for your tool, use it. Native integrations are maintained, updated, and optimized for reliability.
  2. Use custom servers for the gaps. Reserve custom connections for tools that aren't natively supported but are critical to your workflow.
  3. Keep Server Keys short and clear. They appear as tool prefixes in conversations. hubspot is better than my-company-hubspot-production-v2.
  4. Test before rolling out. After connecting, ask OptiAgent a few test questions to confirm the tools work as expected.
  5. Review tool permissions. Disable tools you don't need. Fewer enabled tools means faster, more focused AI responses.
  6. Monitor usage. Check conversation logs periodically to see which tools OptiAgent uses most. Disable unused integrations to keep things clean.