Official description3 sourcesMCP servers3d ago
useparagon/paragon-mcp
Access 130+ SaaS integrations via ActionKit
- Source
- collected from the abordage/awesome-mcp list · type: MCP server
- Harvest history
- first seen 2026-10-14 · last seen 2026-10-16 · seen 4× · listed by 3 sources
- Score
- score 303 · 3 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-10-14;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
Third-party quality signals



The embedded integration platform for developers.
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
---
Paragon MCP Server
A server implementation for Model Context Protocol (MCP) that integrates with ActionKit, an API by Paragon that provides access to prebuilt actions for 130+ integrations to your users' SaaS applications.
Features
| Example Chat | Setup Link |
|:-------------:|:----------:|
| | |
- Add user-facing integrations from your Paragon account as available capabilities to your agent, for example:
- **Google Calendar**: Create or update events and get calendar availability on your user's behalf.
- **Salesforce**: Query and manage records from your user's CRM.
- **Slack**: Send notifications to your user's Slack workspace.
- Automatically prompt users to authorize integrations with the Connect Portal, a prebuilt component for secure OAuth 2.0 and API Key intake flows.
- Optionally: add Custom Actions or direct API access as available tools in the MCP.
Prerequisites
To start using the Paragon MCP Server, you will need to sign up and register for a Paragon account.
- Node.js @ 22.14.0
- npm package manager
Installation
1. Clone the repository
2. Install dependencies:
Environment Variables
Create a .env file in the root directory by running:
Set up the environment variables as described below:
- **Required:**
- PROJECT_ID: Your Paragon project ID)
- SIGNING_KEY: Your JWT signing key (requiredif SIGNING_KEY_PATH is not set)
- SIGNING_KEY_PATH: Path to your JWT signing key file (required if SIGNING_KEY is not set)
- Optional:
- LIMIT_TO_INTEGRATIONS: Comma-separated list of integration names to limit the types of available tools.
- LIMIT_TO_TOOLS: Comma-separated list of tool names to additionaly limit available tools if needed.
- PORT: Server port (default: 3001)
- MCP_SERVER_URL: The URL of your hosted MCP Server. This will be used to generate Setup Links when your users are prompted to install integrations. (default: http://localhost:3001)
- CONNECT_SDK_CDN_URL: Paragon Connect SDK CDN URL (default: https://cdn.useparagon.com/latest/sdk/index.js)
- ACTIONKIT_BASE_URL: Paragon ActionKit base URL (default: https://actionkit.useparagon.com)
- ZEUS_BASE_URL: Paragon API base URL (default: https://zeus.useparagon.com)
- PROXY_BASE_URL: Paragon Proxy API base URL (default: https://proxy.useparagon.com)
- NODE_ENV: Node environment (default: development)
**Note**: When NODE_ENV is set to development, the /mcp and /sse endpoints accept any user ID in the ?user= query parameter to automatically authorize as a specific user while testing locally.
- ENABLE_LEGACY_SSE: Set to false to remove the deprecated /sse and /messages endpoints (default: true)
- MCP_ALLOWED_HOSTS: Additional comma-separated Host header values accepted by /mcp. The host from MCP_SERVER_URL is allowed automatically.
- MCP_ALLOWED_ORIGINS: Additional comma-separated Origin header values accepted by /mcp. The origin from MCP_SERVER_URL is allowed automatically.
- MCP_SESSION_IDLE_TIMEOUT_MS: Time in milliseconds before an inactive Streamable HTTP session is closed (default: 1800000)
- MCP_MAX_SESSIONS: Maximum number of concurrent Streamable HTTP sessions per server instance (default: 1000)
Running the Server
Start the server using:
The server will start on http://localhost:3001 by default.
Client Configuration
> **Note:** Cursor's MCP implementation is a very new protocol and is still in active development. You might encounter unexpected issues. When making changes to the MCP server URL, a full client restart is recommended. For more information about current limitations, see the Cursor MCP documentation.
- Source
- awesome
· https://github.com/useparagon/paragon-mcp
- Browse by field
- MCP servers
- added
- yesterday
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.
Browse all fields →
← Back to index