ActionKit by Paragon

ActionKit by Paragon

Connect to 130+ SaaS integrations (e.g. Slack, Salesforce, Gmail) with Paragon’s ActionKit API.

42
Stars
11
Forks
0
Releases

Overview

Paragon MCP Server is a server implementation for Model Context Protocol (MCP) that integrates with ActionKit, Paragon's API for access to prebuilt actions across 130+ integrations to your users' SaaS applications. It enables you to expose user-facing integrations from your Paragon account as capabilities for your agent, with examples such as Google Calendar (create or update events, get availability), Salesforce (query and manage CRM records), and Slack (send notifications). The server automatically prompts users to authorize these integrations via the Connect Portal, a prebuilt component for secure OAuth 2.0 and API Key intake flows. You can optionally extend the MCP with Custom Actions or direct API access as available tools. For Custom Actions, enable via ENABLE_CUSTOM_OPENAPI_ACTIONS and place OpenAPI specs in an openapi/ folder at the repository root, naming files after the integration (e.g., openapi/googleCalendar.json). The MCP will automatically match OpenAPI specs with Active integrations in your Paragon project to augment the list of available tools. An experimental Proxy API tool can be enabled with ENABLE_PROXY_API_TOOL, allowing the agent to write its own API requests to the integration API with caution. The MCP exposes endpoints /sse, /messages, and /setup for communication and setup. In development mode (NODE_ENV=development), /sse may accept any user via the ?user= parameter to test as a specific user.

Details

Owner
useparagon
Language
TypeScript
License
Updated
2025-12-07

Features

User-facing integrations as MCP capabilities

Expose Paragon account integrations as available capabilities to your agent (examples: Google Calendar, Salesforce, Slack) enabling actions like calendar management, CRM queries, and notifications.

Automatic integration authorization via Connect Portal

Automatically prompt users to authorize integrations using the prebuilt Connect Portal for secure OAuth 2.0 and API Key intake flows.

OpenAPI-based Custom Actions

Add custom action definitions by placing OpenAPI specs in the openapi/ folder (named after the integration) and enable via ENABLE_CUSTOM_OPENAPI_ACTIONS.

OpenAPI auto-matching with active integrations

The MCP automatically matches OpenAPI specs with active Paragon integrations to augment the list of available tools.

Experimental Proxy API tool

Enable the agent to write its own requests to the integration API with ENABLE_PROXY_API_TOOL, with caution to review requests before execution.

SSE-based MCP endpoints

The MCP exposes real-time communication endpoints under /sse, /messages, and /setup for MCP messaging and setup.

Development-mode testing convenience

In development mode, the /sse endpoint can accept any user via the ?user= parameter to test as a specific user.

Audience

DevelopersBuild agents that leverage Paragon ActionKit to access 130+ SaaS integrations.
Cursor usersConfigure Cursor to connect to the MCP server and drive actions.
Claude usersConfigure Claude to use the MCP server endpoints for action retrieval.

Tags

MCPParagon ActionKitSaaS integrationsOAuth 2.0Connect PortalOpenAPICustom ActionsProxy APISSECursorClaudeEnvironment variables