Composition axis
Gateway MCP servers
Reaches many systems at once. One connection that fans out to hundreds of apps, trading depth for breadth.
Example · Zapier
A Gateway server trades depth for breadth. One connection, and the agent can reach hundreds of applications behind it.
For a small practice that runs on ten tools and has nobody to maintain integrations, that trade is often correct. Connecting a gateway once is less work than connecting nine separate servers, and it covers applications that will never publish an MCP server of their own.
The cost is credential custody. A Gateway holds tokens for every system it fans out to, which means one vendor now sits between your agent and your client data, and a breach there is a breach everywhere at once. That is not a reason to avoid gateways. It is a reason to know which of your systems the gateway can reach, and to scope it to the ones you actually need rather than accepting the default grant.
Depth is the other trade. A Gateway usually exposes a generic shape across every app it touches, so you get a common denominator rather than the specific, well-modeled tools a native System server publishes for its own product.
Gateway servers in the directory
4 servers in this directory play this role
Blend (Autopilot MCP)
VendorBlend Labs · Banking & Account Aggregation
Gives lender-built AI agents a single interface into Blend's origination stack, credit and underwriting through compliance and closing, with agentic workflow execution, institution-specific configuration against a lender's own guidelines, access controls and audit trails. Caveats: mortgage and consumer lending origination, adjacent to, not part of, wealth management. Live in beta at announcement. Blend platform lenders only. Access controls and audit trail are vendor-described. Connection details are not publicly published; start with read-only scopes.
Auth: EnterpriseRemoteUpdated 2026-09-10BriteCore
VendorBriteCore · Insurance & Annuities
Open MCP Service layer across the BriteCore P&C platform, acting as a governed orchestration surface over policy, billing, claims, document and workflow APIs so carriers and partners can build their own AI agents on the same infrastructure as BriteCore's native copilots. Vendor describes enforcement of authentication, fine-grained access control, rate limiting, auditability, compliance controls, human-in-the-loop governance and observability. All vendor-described, not independently verified. Caveats: available to BriteCore platform carriers, not a public endpoint. Shipped alongside eight embedded copilots as the first phase of a broader roadmap, multi-agent orchestration across renewals, premium-to-cash and other processes was still future work at announcement. Connection details are arranged with the vendor; start with read-only scopes.
Auth: EnterpriseRemoteUpdated 2026-09-10Duck Creek
VendorDuck Creek Technologies · Insurance & Annuities
MCP support within Duck Creek's insurance-native Agentic AI Platform. Its AI Gateway layer provides a marketplace, registry and standardised protocols (MCP and A2A) so Duck Creek, partner and carrier-built agents can reach core policy, claims, billing and risk data, alongside new agentic underwriting and FNOL applications. Caveats: MCP here is one protocol inside a broader agentic platform, not a standalone published MCP server, treat this listing as protocol support rather than a discrete server. Duck Creek core customers only. The FNOL application was built with Google Cloud on Gemini models. Connection details are not publicly published.
Auth: EnterpriseRemoteUpdated 2026-09-10Zapier MCP
OfficialZapier · Productivity & Collaboration
Hosted MCP gateway that turns 8,000+ connected apps into agent tools, including advisory fee-billing, invoicing and back-office systems that ship no MCP server of their own. You choose which actions to expose on your own private endpoint using your existing Zapier connections.
Auth: OAuthRemoteUpdated 2026-07-31