Setup

Before creating infrastructure monitors, connect the services you want to scan.

​

Infrastructure Connections

Infrastructure monitors use MCP (Model Context Protocol) to connect to your cloud services. Connect services in Settings → Infrastructure.

​

Available Integrations

​

Cloud Infrastructure

​

Frontend & App Platforms

​

Database Providers

​

Monitoring & Infrastructure

​

Work Collaboration

​

Connecting Services

​

OAuth Services (Vercel, Sentry, Linear, Jira, Notion)

​

API Key Services (AWS, GCP, Supabase, etc.)

​

Example: Connecting AWS

1. Go to AWS IAM Console
2. Click “Create access key” under Access keys section
3. Select “Application running outside AWS”
4. Copy the Access Key ID and Secret Access Key
5. Paste into Paragon and set your region (e.g., us-east-1)

​

Example: Connecting Supabase

1. Go to Supabase Access Tokens
2. Click “Generate new token”
3. Copy the token
4. Find your Project Ref in your project URL: supabase.com/dashboard/project/[PROJECT_REF]
5. Paste both values into Paragon

​

Custom MCP Servers

Add your own MCP servers for services not in the list:

1. Click “Add Custom MCP”
2. Enter a name
3. Select protocol type (stdio, http, or sse)
4. Configure command/URL and environment variables
5. Save

​

Repository Connection

Some monitors require a connected GitHub repository:

• Code Quality - analyzes code in a repo
• Dependency Scan - checks package files in a repo
• README Sync - updates README.md in a repo

Ensure the Paragon GitHub App is installed and repositories are added in Settings → Repositories.

​

Disconnecting Services

1. Find the connected service
2. Click the disconnect/remove button
3. Confirm disconnection

​

Next Steps