# Paragon (ActionKit MCP): MCP server status, API access gate and what it does > An embedded integration platform for SaaS products, whose ActionKit product exposes a stated 1,000-plus... Official MCP, Enterprise leaning. Checked 2026-09-07. *Markdown twin of the HTML page at the same path. Same content, no navigation, no styling, no scripts. Links below point at other twins. Site map for machines: [llms.txt](../llms.txt). The whole dataset: [directory.json](../data/directory.json).* *Maintained by Andrew McGuire (https://andrewcmcguire.com), who also publishes https://gtmsignals.co and https://justsaid.ai.* --- [Directory](../index.md) / [MCP Layer](../categories/mcp-infrastructure.md) / Paragon (ActionKit MCP) # Paragon (ActionKit MCP) [Official MCP](../mcp/official.md) [Enterprise leaning](../gates/enterprise-leaning.md) [MCP Layer](../categories/mcp-infrastructure.md) RESEARCHED Checked 2026-09-07 CLI: whiskers > **RESEARCHED** Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 1. Vendor: [useparagon.com](https://useparagon.com) · entry id 07-paragon · source 07-mcp-infrastructure.md line 338 **What it does** An embedded integration platform for SaaS products, whose ActionKit product exposes a stated 1,000-plus actions across 130-plus third-party applications through one API and one MCP server, with Paragon handling the OAuth prompts inside the customer's own product. **AI features, separated from automation with an AI label on it** None of its own. The differentiator relevant to agents is a Dynamic Proxy Actions feature, in beta, that lets an agent write and execute raw HTTP requests against a third-party API using the model's own knowledge of that API rather than a pre-built connector, which is a genuinely different design from a fixed tool list. **RevOps role** Integration infrastructure for a team that is shipping an agent inside its own product rather than wiring up its own stack, which makes it the odd one out among the gateways in this file and closer to Merge than to Composio. **MCP server** - **Status bucket**: Official MCP - **Auth**: Paragon user token plus Connect Portal OAuth. The distinguishing feature is that the authorisation prompt is embedded in the calling product's own chat surface, so an end user authorises a third-party application at query time without leaving the app. - **Parsed URLs**: 2 found in the mcp_url field - **Endpoint probe**: not probed yet The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established on 2026-09-07 and the MCP URL has not been probed live yet. mcp_status, verbatim from the file: official (open-source adapter you host) mcp_url, verbatim from the file: https://github.com/useparagon/paragon-mcp (product page: https://www.useparagon.com/mcp) - [https://github.com/useparagon/paragon-mcp](https://github.com/useparagon/paragon-mcp) - [https://www.useparagon.com/mcp](https://www.useparagon.com/mcp) **What this server exposes** Not harvested yet. Unmeasured, not empty: nobody has read this server's tool list, so this page says nothing about what it exposes. 141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. The full roll up is on the [tools index](../tools-index.md). **Command line** - **Binary**: whiskers - **Status**: official CLI, first party - **Strongest evidence**: npm - **Harvested**: 2026-09-27 Install, as the source shows it: ``` npm install -g @useparagon/whiskers-cli ``` quoted from [https://www.npmjs.com/package/@useparagon/whiskers-cli](https://www.npmjs.com/package/@useparagon/whiskers-cli) on 2026-09-27, via npm ``` npm install -g @useparagon/cli ``` quoted from [https://www.npmjs.com/package/@useparagon/cli](https://www.npmjs.com/package/@useparagon/cli) on 2026-09-27, via npm Packages seen, with the version on 2026-09-27: - [npm: @useparagon/whiskers-cli 2026.5.12](https://www.npmjs.com/package/@useparagon/whiskers-cli) - [npm: @useparagon/cli 1.1.16](https://www.npmjs.com/package/@useparagon/cli) - [npm: @polarityinc/paragon 0.1.4, third party](https://www.npmjs.com/package/@polarityinc/paragon) - [pypi: paragon 1.0.0, third party](https://pypi.org/project/paragon/) A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it. Harvest date 2026-09-27. **Access gate** - **Gate bucket**: Enterprise leaning - **Can a solo operator reach it**: Not without a contract api_gate, verbatim from the file: enterprise-leaning - Paragon publishes no prices. Its pricing page prices by "Connected Users", stating "Usage costs scale based on the number of tenants (customer orgs) you have using integrations", offers a "Start free trial" on each of the three products (Managed Sync, ActionKit, Workflows), and routes SSO, priority support and professional services to "Talk to sales". A solo operator can start without a call but cannot learn the price without one. **API documentation** No documentation URL recorded. 727 of 1252 entries are in the same position. Blank is legal and it is published as blank. **GitHub health** Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build. The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale. A github.com URL already appears somewhere in this entry, which is a seed for that rail and not a measurement of repo health: - [https://github.com/useparagon/paragon-mcp](https://github.com/useparagon/paragon-mcp) **On GitHub** [github.com/useparagon](https://github.com/useparagon) tied to the vendor by rule 1, the directory already classed this repo first-party and its owner is an Organization, confidence strong - **Public repositories**: 18, forks excluded, as read on 2026-09-08 - **Mention MCP**: 2 of them - **Look like CLIs**: 0 of them - **Latest push**: 2026-09-07 The five most recently pushed, on 2026-09-08: | Repository | Kind | Description | Stars | Pushed | Latest release | |---|---|---|---|---|---| | [paragon-ai-skills](https://github.com/useparagon/paragon-ai-skills) | other | Agent Skills for setting up Paragon integrations - from project setup, to installation, and all the way to connecting... | 0 | 2026-09-07 | | | [enterprise-installer](https://github.com/useparagon/enterprise-installer) | infrastructure | Paragon Enterprise deployment assets | 10 | 2026-09-07 | 2026.0826.0910-46ada2b5 | | [managed-sync-s3-uploader](https://github.com/useparagon/managed-sync-s3-uploader) | other | A Node.js service to forward files synced by Paragon Managed Sync pipelines to an S3 bucket | 1 | 2026-08-25 | | | [connect-headless-example](https://github.com/useparagon/connect-headless-example) | docs or examples | | 1 | 2026-08-20 | | | [paragon-mcp](https://github.com/useparagon/paragon-mcp) | MCP server | | 48 | 2026-07-22 | | Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08. **Jobs it can do** No job tag on this entry. 981 of 1,252 entries are untagged. An empty list here means nobody has tagged this, not that the tool does nothing. The vocabulary is closed, so a tool whose job is genuinely not in it stays blank rather than being forced into the nearest tag. **Sources** - [https://www.useparagon.com/mcp](https://www.useparagon.com/mcp) - [https://www.useparagon.com/pricing](https://www.useparagon.com/pricing) - [https://github.com/useparagon/paragon-mcp](https://github.com/useparagon/paragon-mcp) 3 source URLs. Raw sources field, verbatim: https://www.useparagon.com/mcp, https://www.useparagon.com/pricing, https://github.com/useparagon/paragon-mcp **Notes, verbatim from the file** Verified 2026-09-07 from the vendor's own MCP page. NOT A HOSTED ENDPOINT: unlike every other entry in this group, Paragon ships an open-source adapter the customer runs, so there is nothing to probe and none is claimed; the vendor's page offers "Book a demo" and "View GitHub repo" and no server URL. GTM connectors named on the page include Salesforce, HubSpot, Pipedrive, Gong, Salesloft, Apollo, Outreach, Marketo, Mailchimp and Microsoft Dynamics, which is the densest GTM coverage of the six unified-API layers reviewed in this pass. The multi-tenant framing is the practical divider between this and a Composio or a Zapier MCP: Paragon assumes the buyer has end users of their own who each need to authorise their own accounts, so a single operator wiring up one stack is not the target customer and will find the pricing model an awkward fit. **Provenance** - **Entry id**: 07-paragon - **Source file**: 07-mcp-infrastructure.md - **Source line**: 338 - **Tier**: RESEARCHED - **last_checked**: 2026-09-07 - **Data baked**: 2026-09-27 Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the [methodology page](../methodology.md).