MCP Integration
Connect Fabric AI to external tools using the Model Context Protocol (MCP).
The Model Context Protocol (MCP) enables Fabric AI agents to interact with external tools and services. Connect to GitHub, Jira, Slack, Notion, and dozens of other tools to automate your workflows.
Want to use Fabric from Claude Desktop, Cursor, or VS Code? See Fabric MCP Gateway — it lets you access all your Fabric projects, documents, workspaces, and connected tools from any MCP client through a single URL.
Security First: Fabric implements multiple security layers for MCP servers including encrypted credentials, runtime authority with human approval, and destructive tool blocking. See MCP Authority & Security for details.
What is MCP?
MCP (Model Context Protocol) is an open standard that allows AI models to interact with external tools and data sources in a standardized way.
Benefits
For Users
- Natural language commands to control external tools
- No need to switch between applications
- Automated workflows across multiple services
For Agents
- Standardized tool discovery
- Consistent authentication
- Error handling built-in
Available MCP Servers
Fabric includes a registry of tested, pre-configured MCP servers:
Development & Collaboration
| Server | Capabilities |
|---|---|
| GitHub | Issues, PRs, repositories, code search |
| GitLab (Official) | Issues, merge requests, projects — via GitLab's official MCP server (Premium/Ultimate) |
| Atlassian (Jira & Confluence) | Jira tickets, sprints, and boards; Confluence pages and spaces |
| Azure DevOps | Work items, boards, repositories, pipelines |
| Fizzy | Cards and project boards |
The Atlassian (Jira & Confluence) server uses Atlassian's official Rovo MCP server. One OAuth connection unlocks both Jira tickets and Confluence pages.
Communication
| Server | Capabilities |
|---|---|
| Slack | Messages, channels, threads |
Knowledge & Docs
| Server | Capabilities |
|---|---|
| Notion | Pages, databases, blocks |
| Google Drive | Files, folders, documents |
Diagramming
| Server | Capabilities |
|---|---|
| Excalidraw | Create and edit diagrams |
Fabric
| Server | Capabilities |
|---|---|
| Fabric | Access your own Fabric projects, documents, and workspaces from any agent or MCP client |
Don't see the service you need? You can also add your own custom MCP servers — see Creating Custom MCP Servers below.
Setting Up MCP Servers
Navigate to Settings
Go to Settings → MCP Servers.
Browse Registry
Click Add Server to see available servers in the registry.
Select a Server
Choose the server you want to connect (e.g., GitHub).
Authenticate
Depending on the server, you'll authenticate via:
OAuth (Recommended)
- Click "Connect with OAuth"
- Authorize in popup window
- Tokens stored automatically
API Key
- Get API key from the service
- Paste into Fabric
- Click "Save"
Test Connection
Click Test Connection to verify it works.
Enable Server
Toggle the server to Enabled. It's now available for agents.
Authentication Methods
OAuth 2.0 (Recommended)
For servers that support OAuth:
- Discovery — Fabric finds OAuth endpoints automatically
- DCR — Dynamic Client Registration if supported
- Authorization — User authorizes in popup
- Token Storage — Tokens encrypted and stored securely
- Auto-refresh — Tokens refresh automatically
API Key
For servers that use API keys:
- Get key from service dashboard
- Paste into Fabric settings
- Key is encrypted before storage
- Key is decrypted only when needed
No Authentication
Some servers work without authentication:
- Public search APIs
- Open data sources
- Local development servers
Using MCP Tools
In Conversations
Simply ask the agent to use a connected tool:
"Create a GitHub issue for the login bug we discussed"
"Post a summary of this PRD to the #engineering Slack channel"
"Create Jira stories from the user requirements above"With the Orchestrator
The Orchestrator automatically discovers and uses MCP tools:
Tool Discovery
Agents discover tools automatically:
Multi-Tenant Security
MCP connections are scoped per user/organization:
Personal Connections
- Connect your personal GitHub account
- Only you can use these connections
- Isolated from organization connections
Organization Connections
- Connect organization accounts (e.g., company Jira)
- All organization members can use
- Managed by organization admins
Isolation
Transport Types
MCP servers communicate via different transports:
SSE (Server-Sent Events)
- Real-time streaming
- Best for long-running operations
- Used by most cloud servers
HTTP
- Standard request/response
- Simple and reliable
- Good for simple operations
STDIO
- Local process communication
- Used for development
- Self-hosted servers
Health Monitoring
Fabric monitors MCP server health:
Automatic Recovery
- Rate limits — Automatic backoff and retry
- Token expiry — Auto-refresh OAuth tokens
- Server down — Queue requests, retry later
- Failover — Use alternative servers if configured
Creating Custom MCP Servers
For custom integrations, create your own MCP server:
Server Requirements
- Implement MCP protocol
- Expose tool definitions
- Handle authentication
- Return structured responses
Registration
- Go to Settings → MCP Servers → Add Custom
- Enter server URL
- Configure authentication
- Test and enable
Next Steps
Fabric MCP Gateway
Use Fabric as an MCP server from Claude Desktop, Cursor, or any MCP client
MCP Authority & Security
Complete security guide: credentials, authority, stake levels, and audit
Runtime Authority
How agents get human-approved, time-limited access to connected tools
Agents Overview
Learn how agents use MCP tools
Orchestrator
See MCP tools in multi-step workflows
Fabric MCP Gateway
Use Fabric as a unified MCP server from Claude Desktop, Cursor, VS Code, and any MCP-compatible client. Access all your projects, documents, workspaces, workflows, and connected tools through a single endpoint.
Connecting & Verifying Integrations
A practical checklist for connecting an integration and confirming it actually works, plus disconnect, reconnect, and token-expiry guidance.