Hosted Model Context Protocol

Your company knowledge,
one MCP URL away.

OrgMCP turns GitHub, Drive, Jira, Postgres, Sentry and your internal APIs into a single hosted MCP server. Drop the URL into Cursor, Claude or ChatGPT and your whole team queries permission-aware company context — no agent framework, no glue code.

No credit card. EU data residency. Bring-your-own connectors.

cursor — Settings → MCP servers
URL https://orgmcp.acme.io/t/acme/mcp
How does our SSO callback handle stale state?

Found 3 sources in acme/auth-service:

  • ghsrc/sso/sessionRefresh.tsL142
  • 🇳Notion · "SSO Stale-State RFC"
  • 💬Slack #eng-platform · 3 days ago

The callback drops the stale state cookie and re-issues a fresh nonce on every WorkOS round-trip — see L142-L168.

Built for teams, not demos.

Multi-tenant by design, with the boring-but-essential primitives — RLS, audit log, audience filters — wired up before day one.

Sources your AI vendor does not ship

Jira, Confluence, Postgres, MySQL, Sentry, Axiom, John Deere and any internal HTTP API — next to GitHub, Drive and Slack, in one workspace.

One connection, every client

Connect each source once. Cursor, Claude, ChatGPT and any Streamable-HTTP MCP client share the same URL, the same permissions and the same audit log.

Audience-scoped retrieval (Business+)

Group ACL filters every search server-side. Engineering can't see HR documents, even by accident.

Simple, per-seat pricing.

Start free. Upgrade when your team needs it. A seat is a person whose agent calls OrgMCP — not your whole headcount.

Free

Try OrgMCP on a side project. No credit card.

$0/ €0
forever
  • 3 seats / 3 connectors / 3 sources
  • 3k tool-calls / month
  • 1 GB ingest / month
  • GitHub, GitLab, Google Drive, Slack, Linear, Postgres & MySQL

Team

For teams whose agents already have Cursor, Claude or ChatGPT.

$35/ €29
per seat / month · min 2 seats
  • 2–25 seats · 500k tool-calls / mo
  • All 17 catalog sources · 20 GB ingest / mo
  • Annual: $29 / €24 per seat / month
  • Models not included — bring your own AI client

BusinessRecommended

SAML IdP, group ACL, custom domain, audit export.

$71/ €59
per seat / month · min 5 seats
  • 5–100 seats · 5M tool-calls / mo
  • WorkOS SAML / OIDC (Google/Microsoft login is on every plan)
  • Group ACL · custom domain · audit export
  • Annual: $59 / €49 · 14-day trial, no card upfront

Enterprise

Regulated sectors — SCIM, silo, SLA, custom MSA.

Custom
contract
  • Unlimited seats / sources
  • WorkOS SCIM Directory Sync
  • Audit-log Kinesis stream
  • Silo deployment · 99.9% SLA

All prices excl. VAT. EU customers: VAT calculated at checkout. EU B2B with valid VAT-ID: reverse-charge applies. US: most states have no sales tax on B2B SaaS.
Full pricing & tax details.

Frequently asked questions

Does OrgMCP store my source data?

Indexed embeddings live in your tenant partition of OpenSearch Serverless. Raw files stream from the source system on every read; we only persist what we have to.

How is access controlled?

Every search and tool call carries a server-side audience filter (tenant + groups + user). The OpenSearch query-time filter is mandatory and applied in middleware, not the client.

Where is data stored?

AWS Frankfurt (eu-central-1). EU GDPR-compliant by default. Custom regions available on the Enterprise plan.

Which MCP clients are supported?

Anything that speaks the Streamable HTTP MCP transport — Cursor, Claude (web, Desktop, Code), ChatGPT, VS Code, and most OSS MCP clients. One URL works in all of them at once.

ChatGPT and Claude already connect to Drive, Slack and GitHub. Why OrgMCP?

Those built-in connectors are great if your team uses one AI client and your context lives in Drive, Slack and GitHub. OrgMCP is for the rest: Jira and Confluence, Postgres and MySQL, Sentry and Axiom, industry systems like John Deere, and any internal HTTP API — plus one connection shared by Cursor, Claude and ChatGPT with a single audit log, hosted in the EU. Keep the vendor connectors you like; add OrgMCP for what they don't reach.