Paragon

Executive Summary

Paragon is an embedded integration platform (iPaaS) for B2B SaaS companies — managed authentication, data sync, and workflow infrastructure that lets a product ship native integrations to its customers without building OAuth flows and API plumbing per provider. ^[1] In 2025 it rebuilt the platform around AI: ActionKit exposes 1,000+ prebuilt integration actions across 130+ SaaS applications to a product's AI agents through a single API or an MCP server, with the same per-tenant managed auth that powers its traditional integrations. ^{[2] [3]}

The company was founded in 2019, is Y Combinator-backed, and raised a $13M Series A led by Inspired Capital with FundersClub, Garuda Ventures, and Jude Gomila participating, bringing total funding to over $16M alongside investors including Global Founders Capital and Village Global. ^[4] Over 100 engineering teams use the platform, which is SOC 2 Type II certified and offers on-premise deployment for enterprises. ^[2] Its ActionKit MCP server is a publicly listed third-party server on the Anthropic MCP registry. ^[5]

---

Product Overview

Paragon's classic product is embedded iPaaS: a B2B SaaS company drops Paragon's Connect Portal into its app so end customers can authorize integrations (OAuth 2.0 or API keys), then builds syncs and workflows against those connections — Paragon claims 70% less engineering effort and 7x faster time-to-market for new integrations. ^{[6] [1]}

ActionKit extends that same infrastructure to agents. A single GET actions call returns JSON schemas — tool names, descriptions, and parameters — for thousands of actions across providers like Google Drive, Google Calendar, Slack, Salesforce, and Jira, ready to pass to an LLM as function definitions; the agent then executes reads, writes, and updates on the end user's behalf using that user's stored credentials. ^[5] The same actions are available over MCP, where the server issues magic links that route end users through the Connect Portal to authorize any integration the agent needs. ^{[5] [3]}

Key Capabilities

Product Surfaces

^{[2] [5] [6]}

---

Technical Architecture

Paragon is a hosted cloud platform with an on-premise deployment option for enterprises. ^[2] Agents consume ActionKit either as REST (tool schemas passed directly into frameworks like Vercel's AI SDK, LangChain, and OpenAI) or through the MCP server. ^{[5] [2]}

The MCP server is open source (TypeScript, MIT license) and uses SSE transport designed for multi-tenant MCP clients: each session is authorized with a Paragon User Token — an RS256-signed JWT encoding the end user's ID — so every tool call executes against that specific user's connections, and unauthorized integrations trigger magic-link auth flows through the Connect Portal. ^[3] Provider credentials live in Paragon's platform, not the agent runtime.

Key Technical Details

---

Strengths

• Per-tenant auth is the core product, not a feature — the Connect Portal, token refresh, and JWT-scoped MCP sessions were built for embedded multi-tenant integrations, exactly what a B2B SaaS product's agents need ^{[3] [2]}
• One platform for integrations and agent actions — the same connections power native integrations (sync, workflows) and agent tool calls, avoiding parallel stacks ^[6]
• LLM-ready tool schemas — a single GET actions call returns function definitions consumable by Vercel AI SDK, LangChain, and OpenAI without adapter code ^[5]
• Registry presence — the ActionKit MCP server is publicly listed on the Anthropic MCP registry, with multi-tenant SSE support uncommon among first-wave MCP servers ^{[5] [3]}
• Enterprise posture — SOC 2 Type II, on-premise deployment, and a six-year operating history with 100+ engineering teams ^[2]

---

Cautions

• Smaller catalog than agent-native rivals — 130+ integrations versus 1000+ toolkits at Composio and 800+ APIs at Nango; the "1,000+" figure counts actions, not providers ^{[3] [2]}
• Opaque pricing — no public prices; Platform, Pro, and Enterprise are all quote-based, metered on Connected Users, making costs hard to estimate before sales contact ^[6]
• Closed platform — only the thin MCP server is open source (modest traction at under 100 GitHub stars as of June 2026); there is no self-hostable open core as an exit hatch ^[3]
• Funding vintage — the $13M Series A dates to the pre-AI era of the business; no AI-era round has been announced, and current financial details are not publicly disclosed ^[4]
• B2B-SaaS-shaped — designed for products embedding integrations for their customers; developers building standalone or internal agents will find leaner catalog-first options

---

Pricing & Licensing

All tiers include unlimited integrations, custom connectors, fully managed authentication, and embedded/headless SDK options; usage scales with Connected Users (customer orgs using integrations). ^[6]

Licensing model: Proprietary hosted platform; the ActionKit MCP server is open source under MIT. ^[3]

Hidden costs: Quote-based pricing metered on Connected Users means costs grow with customer adoption of integrations — favorable for low-penetration products, expensive at scale.

---

Competitive Positioning

Paragon represents a distinct segment of MCP integration platforms: embedded iPaaS vendors pivoting to agents, serving B2B SaaS companies that ship agents inside their own product — versus developer-facing tool catalogs aimed at anyone building an agent.

Direct Competitors

When to Choose Paragon Over Alternatives

• Choose Paragon when: you are a B2B SaaS company shipping agents inside your product and need end customers to authorize integrations through an embedded, white-label auth flow
• Choose Paragon when: you already need embedded iPaaS (sync, workflows) and want agent actions from the same connections
• Choose Composio when: you are agent-first and want the largest plug-and-play tool catalog
• Choose Nango when: self-hosting or open source is a procurement requirement

---

Ideal Customer Profile

Best fit:

• B2B SaaS companies embedding AI agents in their product that must act on each customer's third-party apps (CRM, ticketing, messaging) with that customer's credentials
• Teams that want integrations and agent actions from one vendor instead of stitching an auth provider to a tool catalog
• Enterprises needing SOC 2 Type II and on-premise deployment ^[2]

Poor fit:

• Individual developers or startups building standalone agents who want transparent, self-serve pricing
• Teams requiring an open source, self-hostable core platform
• Products needing long-tail providers beyond the 130+ catalog without building custom connectors

---

Viability Assessment

Paragon enters the MCP platform race the way Nango did — from an existing integrations business — but with a closed platform and an older funding base. Its bet is that B2B SaaS companies shipping in-product agents will buy the full embedded stack (auth UX, sync, workflows, actions) rather than assemble it from catalog-first vendors.

---

Bottom Line

Paragon is the embedded-iPaaS entry in the MCP integration platform category: ActionKit turns six years of per-tenant integration infrastructure into 1,000+ agent-callable actions across 130+ apps, delivered through one API or an Anthropic-registry-listed MCP server with managed OAuth handled by its Connect Portal. ^{[2] [5] [3]}

Recommended for: B2B SaaS companies shipping agents inside their product that need embedded, per-customer authorized integration actions plus traditional sync and workflows.

Not recommended for: Agent-first developers wanting the biggest open catalog or self-serve pricing (see Composio) or teams requiring a self-hostable open core (see Nango).

Outlook: A defensible niche — in-product agents with embedded auth — but Paragon must out-execute larger-cataloged, better-funded agent-native rivals without disclosed AI-era funding.

---

Research by Ry Walker Research • methodology