Integrations
Connect the agent with GitHub, Slack, and MCP services.
The Paragon Agent integrates with GitHub and Slack for triggering sessions, receiving notifications, and creating pull requests. It also supports MCP (Model Context Protocol) integrations that give the agent access to external tools and services.
GitHub
Triggering the Agent
Mention the agent in a GitHub comment to trigger a session:
- Issue comments —
@paragon-run fix this bug - PR comments —
@paragon-run add tests for these changes - Review comments —
@paragon-run address this feedback
The agent creates a session, works on the task, and replies with results in the same thread.
Pull Requests
When the agent makes code changes, it:
- Commits via the Paragon GitHub App (or your personal token as fallback)
- Creates a pull request with the changes
- Updates the PR status in the session (open, merged, closed)
Automation Triggers
GitHub events can trigger automations:
- PR created, PR merged, push, comment created, review submitted
- Branch pattern and label filters for selective triggering
- See Automations for configuration
Slack
Triggering the Agent
Mention the Paragon bot in Slack to trigger an automation:
@paragon-bot fix the login bug in the dashboard repo
The agent matches the message to a configured automation and creates a session.
Notifications
Automations can send Slack reports when runs complete:
- Channel — Choose which channel receives notifications
- Output — Optionally include the full agent output
- Threading — Replies are threaded to keep channels clean
Plan Approval via Slack
When a Grind mode session is awaiting plan approval, the agent can notify you in Slack. Approve or request revisions directly from the notification.
Setup
- Go to Settings in the dashboard
- Click Connect Slack
- Authorize the Paragon app in your Slack workspace
- Configure Slack triggers and reporting in your automations
MCP Integrations
MCP (Model Context Protocol) gives the agent access to external tools and services during a session.
Pre-Configured Services
Connect any of these services from the agent settings:
| Service | Auth | What the Agent Can Do |
|---|---|---|
| Linear | OAuth | Read and update issues, create tickets |
| Slack | Credentials | Send messages, read channels |
| Jira | OAuth | Manage tickets, read boards |
| Notion | OAuth | Access documentation, read pages |
| Sentry | OAuth | Investigate errors, read stack traces |
| Vercel | OAuth | Check deployments, read logs |
| Supabase | Credentials | Query databases, manage tables |
| Cloudflare | Credentials | Manage workers, DNS, and pages |
| AWS | Credentials | Interact with AWS services |
| MongoDB | Credentials | Query collections, read data |
Custom MCP Servers
Connect any MCP-compatible service:
- Go to agent settings
- Click Browse MCPs > Custom
- Choose a protocol:
- stdio — Local process communication
- HTTP — HTTP-based MCP server
- SSE — Server-Sent Events transport
- Configure the server URL or command
- Save
Configuration Levels
MCP servers can be configured at multiple levels:
- User-level — Available in all your sessions
- Team-level — Shared across all team members
- Automation-level — Specific to an automation
Browser Tools
The agent can use a real browser in the sandbox environment to interact with web applications:
| Tool | Description |
|---|---|
| Navigate | Go to a URL |
| Click | Click an element |
| Type | Type text into a field |
| Fill | Fill a form input |
| Scroll | Scroll the viewport |
| Get State | Read the current page state |
| Close | Close the browser |
Enable browser support with the --browser flag in CLI or by selecting a Grind session in the dashboard.