GitHubDashboard
Docs/Integrations

Integrations

Connect providers to MCP Shield with secure OAuth. Each integration grants scoped access to provider capabilities while keeping credentials protected.

Quick Connect

Connect a provider with a single CLI command:

# Connect GitHub
mcp-shield providers connect github

# Connect Vercel
mcp-shield providers connect vercel

# Connect Supabase
mcp-shield providers connect supabase
bash

Or connect via the dashboard for a visual OAuth flow.

How Integrations Work

1

OAuth Connect

Authorize MCP Shield to access the provider with scoped permissions.

2

Secure Storage

Credentials are encrypted at rest and never exposed to AI clients.

3

Governed Access

MCP calls are routed through MCP Shield with policy enforcement.

Credential Security

Provider credentials (OAuth tokens, API keys) are never sent to AI clients. MCP Shield stores them securely and injects them only when forwarding requests to provider servers. AI clients authenticate to MCP Shield with separate tokens.

Available Integrations

GitHub
Available
Repository management, issues, pull requests, and code operations.
15 MCP tools3 scopes
Vercel
Available
Deployments, projects, domains, and environment variables.
12 MCP tools2 scopes
Supabase
Available
Database operations, auth, storage, and edge functions.
18 MCP tools3 scopes
Figma
Available
Design files, components, variables, and export operations.
8 MCP tools2 scopes
Slack
Available
Channels, messages, users, and workspace management.
10 MCP tools2 scopes
Notion
Available
Pages, databases, blocks, and workspace operations.
11 MCP tools2 scopes
Linear
Available
Issues, projects, cycles, and team management.
14 MCP tools3 scopes
AWS
Coming Soon
S3, Lambda, DynamoDB, and other AWS services.

Managing Connections

View and manage your connected integrations:

# List all connections
mcp-shield providers list

# Output:
# ┌──────────┬────────────┬───────────────────┬─────────────┐
# │ Provider │ Status     │ Connected As      │ Last Used   │
# ├──────────┼────────────┼───────────────────┼─────────────┤
# │ github   │ connected  │ your-username     │ 2 hours ago │
# │ vercel   │ connected  │ your@email.com    │ 1 day ago   │
# │ supabase │ expired    │ -                 │ 7 days ago  │
# └──────────┴────────────┴───────────────────┴─────────────┘

# Refresh expired credentials
mcp-shield providers refresh supabase

# Disconnect a provider
mcp-shield providers disconnect github
bash

Scopes and Permissions

Each integration requests only the scopes needed for its MCP tools. You can customize scopes during connection:

# Connect with specific scopes
mcp-shield providers connect github --scopes repo,read:org

# Connect with minimal read-only scopes
mcp-shield providers connect github --scopes read:user,read:org
bash

Principle of Least Privilege

We recommend connecting with the minimum scopes required for your use case. You can always reconnect with additional scopes if needed.

Request an Integration

Need an integration we don't have yet? Let us know:

Open GitHub Issue