Infrastructure Connections
Infrastructure monitors use MCP (Model Context Protocol) to connect to your cloud services. Connect services in Settings → Infrastructure.Available Integrations
Cloud Infrastructure
| Service | Auth Method | What You Need |
|---|---|---|
| AWS | Access Keys | Access Key ID, Secret Access Key, Region |
| GCP | Service Account | Project ID, Service Account JSON key |
| Azure | App Registration | Subscription ID, Tenant ID, Client ID, Client Secret |
| Cloudflare | API Token | API Token, Account ID |
| DigitalOcean | API Token | Personal Access Token |
| Fly.io | API Token | Personal Access Token |
Frontend & App Platforms
| Service | Auth Method | What You Need |
|---|---|---|
| Vercel | OAuth | Click Connect → authorize in browser |
| Netlify | API Token | Personal Access Token |
| Heroku | API Key | API Key from account settings |
Database Providers
| Service | Auth Method | What You Need |
|---|---|---|
| Supabase | Access Token | Access Token, Project Reference |
| MongoDB | Connection String | MongoDB connection string (mongodb+srv://…) |
| Firebase | Project ID | Project ID (requires gcloud CLI auth) |
| Appwrite | API Key | Project ID, API Key, Secret |
| Snowflake | Credentials | Account Identifier, User, Password |
Monitoring & Infrastructure
| Service | Auth Method | What You Need |
|---|---|---|
| DataDog | API Keys | API Key, Application Key, Site |
| Sentry | OAuth | Click Connect → authorize in browser |
| Terraform Cloud | API Token | API Token, Organization name |
Work Collaboration
| Service | Auth Method | What You Need |
|---|---|---|
| Linear | OAuth | Click Connect → authorize in browser |
| Jira | OAuth | Click Connect → authorize in browser |
| Notion | OAuth | Click Connect → authorize in browser |
| Slack | Bot Token | Bot User OAuth Token, Team ID |
Connecting Services
OAuth Services (Vercel, Sentry, Linear, Jira, Notion)
1
Click Connect
Click the Connect button on the service
2
Authorize
Complete the OAuth flow in your browser
3
Done
Service appears as connected
API Key Services (AWS, GCP, Supabase, etc.)
1
Click Connect
Click the Connect button on the service
2
Follow Setup Guide
Each service shows step-by-step instructions with links
3
Enter Credentials
Paste your API keys, tokens, or credentials
4
Save
Click Save to connect the service
Example: Connecting AWS
- Go to AWS IAM Console
- Click “Create access key” under Access keys section
- Select “Application running outside AWS”
- Copy the Access Key ID and Secret Access Key
- Paste into Paragon and set your region (e.g.,
us-east-1)
Example: Connecting Supabase
- Go to Supabase Access Tokens
- Click “Generate new token”
- Copy the token
- Find your Project Ref in your project URL:
supabase.com/dashboard/project/[PROJECT_REF] - Paste both values into Paragon
Custom MCP Servers
Add your own MCP servers for services not in the list:- Click “Add Custom MCP”
- Enter a name
- Select protocol type (stdio, http, or sse)
- Configure command/URL and environment variables
- 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
Disconnecting Services
- Find the connected service
- Click the disconnect/remove button
- Confirm disconnection
Disconnecting a service will cause monitors that depend on it to fail.
Next Steps
Create Monitors
Set up your first infrastructure or uptime monitor