Infrastructure

Connect your CI/CD, cloud, and dev infrastructure to give the agent access to external services.

Infrastructure integrations give the agent access to your existing tools and services via MCP (Model Context Protocol). Connect cloud providers, databases, project management, monitoring, and more — so the agent can read issues, query databases, check deployments, and investigate errors as part of its workflow.

Pre-Configured Services

Connect any of these services from the agent settings page. Click Browse MCPs to see the full list.

OAuth

These services authenticate through an OAuth flow. Click Connect, then run the provided CLI command to complete authorization.

Service	What the Agent Can Do
Linear	Read and update issues, create tickets, manage projects
Jira	Manage tickets, read boards, update issue status
Notion	Access documentation, read and search pages
Sentry	Investigate errors, read stack traces, query events
Vercel	Check deployments, read build logs, inspect environment

Credentials

These services connect with API keys or tokens entered directly in the dashboard.

Service	Required Credentials	What the Agent Can Do
Slack	Bot Token, Team ID	Send messages, read channels
Supabase	Access Token, Project Ref	Query databases, manage tables, read schemas
Cloudflare	API Token, Account ID	Manage workers, DNS, and pages
AWS	Access Key, Secret Key, Region	Interact with EC2, S3, RDS, Lambda, and other AWS services
MongoDB	Connection String	Query collections, read and write data

Credentials are encrypted at rest using AES-256-GCM. They are only decrypted when passed to the agent during a session.

Connecting a Service

OAuth Services

Go to the Agent page and click Browse MCPs
Select the service you want to connect

Copy the CLI command shown in the modal:

paragon mcp-auth linear --url https://mcp.linear.app/sse

Run it in your terminal — this opens the OAuth flow in your browser
After authorizing, paste the token back into the dashboard modal
The service appears as Connected with a checkmark

Credential Services

Go to the Agent page and click Browse MCPs
Select the service
Enter the required credentials (API keys, tokens, connection strings)
Click Save

Custom MCP Servers

Connect any MCP-compatible service that isn't in the pre-configured list.

Click Browse MCPs > Custom MCP
Enter a name for the server
Choose a protocol:
- stdio — Local process communication (command + args)
- HTTP — HTTP-based MCP endpoint
- SSE — Server-Sent Events transport
Configure the server URL or command
Add any required environment variables or headers
Click Save

Example: Custom stdio Server

{
  "command": "npx",
  "args": ["-y", "@your-org/mcp-server"],
  "env": {
    "API_KEY": "your-api-key"
  }
}

Managing Connections

Connected services show a checkmark in the Browse MCPs panel. To disconnect a service, click on it and remove the configuration.

Your MCP configuration applies to all your agent sessions and automations. Each team member manages their own connections independently.

Next Steps

Integrations

Configure GitHub mentions, Slack triggers, and browser tools.

Automations

Set up automated workflows that use your connected infrastructure.

Automations Integrations