Step 01
Define an MCP Server
Enter the URL for a service that supports remote MCP. Choose an authentication type, or let Opal auto-detect it. For OAuth, Opal can detect configuration details automatically.
Connectors
Connect Opal to the systems your organization already uses.
Connectors let your agents, tasks, and flows work directly with external tools and live data. Built on the Model Context Protocol, Opal becomes the coordination layer where your systems come together in one place.
Connectors · remote MCPconnected
mcp server
oauth auto-detected
connection · ana
her access
connection · sam
his access
connection · lee
their access
agents · tasks · flows · spaceslive data
The problem
Most AI tools operate in isolation.
They can answer questions about your business, but they can't reach into your systems, fetch live data, or take action where work actually happens.
The result is a persistent gap between what AI recommends and what people still have to do manually.
01
AI that stops at the answer
Agents that can't access external systems hand work back to people at the exact moment it matters most. The value of automation disappears at the boundary.
02
Integration overhead
Connecting AI tools to existing systems typically requires custom development, brittle middleware, or ongoing maintenance. Most teams don't have the capacity to build and sustain that infrastructure.
03
Shared credentials create risk
When systems are connected with shared credentials, individual accountability disappears and compliance risk increases. Access should follow the person, not the tool.
What is a Connector?
A live link between Opal and your systems.
A Connector is made of two parts: an MCP Server that defines the service, and the individual connections people create from it. Together they give your digital workforce direct, accountable access to the tools your organization already uses.
- 01
MCP Server
Define a connection to any service that supports remote MCP. Provide the server URL and let Opal auto-detect the authentication type, or configure it manually for full control.
- 02
MCP Connections
Each person creates their own connection from an MCP Server, authorizing it with their individual account. Permissions and available functionality reflect exactly what that person can access in the connected system.
- 03
Three authentication methods
Connectors support None, Bearer Token, and OAuth. For OAuth, Opal can auto-detect configuration details — or you can configure manually when you need it done a specific way.
- 04
Flexible attachment
Attach connections to agents, tasks, flows, and Spaces so your digital workforce has direct access to the systems it needs at every stage of work.
- 05
Template-level server definitions
Define an MCP Server on an agent, task, or flow template. When someone creates from that template, they are prompted to select their own connection — letting each person bring their own access without rebuilding the setup from scratch.
- 06
Remote MCP only
Opal is a cloud-based platform. Connected services must support remote MCP. Local MCP servers are not supported.
Flow · connector callauthorized
step 01
Collect request details
step 02
Look up account record
mcp server · crm
calling · returning data
data passed on
step 03
Draft the response with live data
How it works
From server URL to live action.
Step 02
Create a connection
Each team member creates their own MCP Connection from the server, authorizing it with their individual credentials. Their connection reflects their own permissions in that system.
Step 03
Attach to your workforce
Add the connection to an agent, task, flow, or Space so that part of your digital workforce can reach the system directly when it needs to.
Step 04
Work with live data
Agents fetch real information and take action in connected systems as part of their normal operation, without anyone leaving Opal to gather data manually.
Step 05
Reuse across templates
Define a server once on a template. Every new agent, task, or flow created from it is prompted to select the right connection at creation time — consistent setup, individual access.
Key benefits
Live systems access, without the middleware.
One platform for your systems
Bring external tools into Opal so people, agents, and workflows operate against live systems from a single environment. No switching between disconnected tools.
Agents that act, not just answer
Let agents, tasks, and flows fetch real data and call external APIs so work gets completed end to end rather than stopping at a recommendation.
Fast, flexible setup
Auto-detect authentication, including OAuth configuration, to stand up a connection quickly. Manual configuration is available when you need full control.
Access that respects each user
Per-user connections carry each individual's own service permissions. People only reach what they are entitled to reach in the connected system — no shared credentials, no overreach.
Reusable across templates
Define a server once on a template and let each new agent, task, or flow be paired with the right connection at creation time. Scale setup without repeating it.
See it in practice
How teams put connectors to work.
Three real shapes of connected work, from help desk lookups to cross-system reporting.
Case 01
Support
Help desk integration
An operations lead wants a support agent to pull ticket details directly from the company's help desk system. An administrator defines an MCP Server for the help desk, letting Opal auto-detect the OAuth configuration. Each support team member then creates their own MCP Connection from that server and attaches it to the support agent. When a team member asks the agent to look up a ticket, the agent fetches it directly using that person's own permissions, without anyone leaving Opal.
- Auth
- OAuth · auto-detected
- Attached to
- Support agent
- Outcome
- Tickets fetched in Opal
Case 02
Customer Success
CRM-powered renewal preparation
A customer success team uses an agent to prepare renewal summaries. With a Connector in place, the agent retrieves current account data, contract details, and open activities directly from the CRM at run time — without requiring anyone to pull exports, copy-paste records, or manually prepare inputs before the conversation starts.
- Source
- CRM accounts, contracts, activities
- Attached to
- Renewal agent
- Outcome
- No exports or copy-paste
Case 03
Operations
Cross-system reporting
An operations team runs a weekly reporting flow that pulls metrics from multiple systems. Connectors let the flow reach each system directly at run time, using each team member's own access. Reports reflect accurate, current data without manual data gathering or consolidation.
- Scope
- Multiple systems, one flow
- Attached to
- Weekly reporting flow
- Outcome
- Current data, no consolidation
Security and compliance
Access that follows the person, not the tool.
01
Role-Based Access Control
Administrators define and manage MCP Servers. Each user manages their own connections within the access controls their admin has established.
02
Per-User Authorization
Each MCP Connection is authorized by the individual user. Access reflects that person's own permissions in the connected system — not shared credentials.
03
Three Authentication Methods
None, Bearer Token, and OAuth — with auto-detection or manual configuration depending on what your systems require.
04
Audit Log
Agent and workflow actions against connected systems are logged and traceable through Opal's Activity Log.
05
Zero Data Retention
Opal operates on a zero data retention basis with supported models.
06
Certifications
ISO 27001, ISO 42001, and SOC 2 Type II certifications are underway.
Connectors are one part of a connected platform
How Connectors fit the platform.
01AgentsAttach MCP Connections to agents so they can fetch data and take action in external systems as part of their normal work.02TasksGive automated tasks access to external systems for live data retrieval and real action at run time.03FlowsAttach connections to flows so multi-step processes can reach external systems at each stage.04SpacesAttach connections to Spaces to extend external system access within an operational environment.05GovernancePer-user connections enforce individual accountability and support access control requirements.
Connect your digital workforce to the systems that matter.
No middleware. No manual handoffs.
Opal Connectors let your agents, tasks, and flows work with live data from the tools your organization already uses.