Use ActionKit by Paragon with Bifrost
Connect to 130+ SaaS integrations (e.g. Slack, Salesforce, Gmail) with Paragon’s ActionKit API.
[ MCP SERVER SUMMARY ]
ActionKit by Paragon MCP server summary
ActionKit by Paragon connects AI agents to 130+ SaaS integrations — Slack, Salesforce, Gmail, and more — through a unified MCP interface. Bifrost adds a governance layer so you control which integrations each team can reach and log every cross-app tool call.
| Property | Details |
|---|---|
| Company | Paragon |
| Connection type | HTTP |
| Authentication | Bearer API key |
| Package or endpoint | Paragon ActionKit MCP endpoint |
| Capabilities | 130+ SaaS integrations, Cross-app actions, Managed authentication |
| Official documentation | ActionKit by Paragon MCP documentation |
Before you start
- A Paragon ActionKit account
- A Paragon API key and MCP endpoint
What you can do with ActionKit by Paragon
- Give sales and support agents governed access to CRM and messaging tools from one MCP endpoint
- Rotate Paragon API credentials in one place instead of every developer laptop
- Enforce spend caps and audit trails when agents orchestrate multi-SaaS workflows
[ HOW TO CONNECT ]
Connect ActionKit by Paragon to Bifrost in three steps
Install Bifrost
Start the gateway locally or deploy in your VPC.
npx -y @maximhq/bifrost
Add ActionKit by Paragon in MCP Gateway
Open MCP Gateway in the Bifrost dashboard, click New MCP Server, and choose HTTP. Or register via the API below.
• Choose HTTP as the connection type and paste your Paragon ActionKit MCP endpoint.
• Set Auth Type to Headers and add your Paragon API key — use env.PARAGON_API_KEY for secret references.
Point clients at Bifrost /mcp
Configure Claude Desktop, Cursor, or Claude Code to use your Bifrost endpoint with a virtual key instead of connecting directly to ActionKit by Paragon.
{
"mcpServers": {
"bifrost": {
"url": "http://localhost:8080/mcp",
"headers": {
"Authorization": "Bearer vk_your_virtual_key"
}
}
}
}[ EXAMPLE CONFIG ]
Register ActionKit by Paragon via API
Add this MCP client with a POST to /api/mcp/client. See Connecting to MCP Servers for full options.
curl -X POST http://localhost:8080/api/mcp/client \
-H "Content-Type: application/json" \
-d '{
"name": "actionkit",
"connection_type": "http",
"connection_string": "https://your-paragon-instance.useparagon.com/mcp",
"auth_type": "headers",
"headers": {
"Authorization": "Bearer env.PARAGON_API_KEY"
},
"tools_to_execute": ["*"]
}'[ WHY BIFROST ]
Run ActionKit by Paragon through one governed gateway
Access control
Virtual keys, RBAC, and tool allowlists per team or agent.
Cost governance
Attribute MCP tool spend alongside LLM usage in one view.
Observability
Log every tool call with latency, server, and virtual key metadata.
Credential isolation
Upstream secrets stay in the gateway — not on every laptop.
[ FAQ ]
Common questions
Why route ActionKit through Bifrost instead of connecting directly?
Direct connections scatter API keys across clients and skip centralized RBAC. Bifrost gives you virtual keys, tool allowlists, audit logs, and cost attribution for every ActionKit invocation.
Which auth mode should I use for ActionKit?
Use header-based authentication with your Paragon API key. Reference secrets with the env. prefix so keys are not stored in plain config files.
Can I limit which SaaS tools agents can call?
Yes. Configure tools_to_execute on the MCP client and attach stricter allowlists to each virtual key so teams only reach approved integrations.
[ RELATED SERVERS ]
More MCP integrations
Composio
Connect AI agents to hundreds of applications and tools through Composio’s managed integration platform.
Slack
Slack’s MCP server gives AI agents secure access to workplace conversations, channels, and collaboration context.
Gmail
Connect AI assistants to Gmail to search messages, draft and send email, and automate inbox workflows through Google Workspace MCP.