Nango scopes MCP agents by tenant, and its catalog record is a product behind

Nango scopes MCP agents by tenant, and its catalog record is a product behind

Nango’s guide on how to add access control to any MCP server answers a question most MCP tutorials skip: an MCP server knows which account it authenticated, but it does not know which of your customers an agent is supposed to be working for. Nango’s answer is Agent Sessions. Your backend verifies the user’s tenant membership, then creates a session that selects that tenant’s connections by tag, allowlists named tools, and expires on a fixed clock. The walkthrough gives CustomerA’s agent exactly two Notion tools, notion-search and notion-fetch, for one hour, with no change to the upstream server. The sharpest line is a warning about its own product: keep nango_proxy disabled, because it “bypasses named-tool allowlists, including direct calls to upstream MCP tools.”

The figures in the post are Nango’s: “10,000+ prebuilt tools across 1,000+ APIs.” Treat them as vendor counts. What survives without them is the design, and it is a good one. The tenant decision is made by your backend before the agent starts, the agent “cannot change the scope of its session,” and Nango is honest about the limit: if one connected Notion account can see both customers’ pages, tenant tags will not separate them. Connection selection is not resource permission. The post also names a hard requirement for bringing your own MCP server: it must support OAuth with Dynamic Client Registration or Client ID Metadata Documents.

In the catalog, Nango is six API pages, and the story walks four of them. Tenant-tagged connections are the Nango Connections API; the Notion MCP setup lives in the Nango Integrations API; the prebuilt tools exposed through a session are the Nango Actions API; and the raw passthrough the post tells you to switch off is the Nango Proxy API. What the catalog does not have is the session endpoint itself. The agentic access profile counts 21 operations, 14 of them acting, and the catalog description still says “over 400 APIs with 600+ pre-built integrations.” The product in this post is newer than the record that describes it.

Nango scores 52.6 on the Kin Score, developing, carried by access clarity at 71.1 and discoverability at 66.7, with contract governance at 13.6. Agent Readiness is 31.6, and the lit dimensions match the post: an MCP server, auth clarity, protected resource metadata. The unlit ones are the instructive part. Dynamic client registration is dark on the company whose generic MCP path requires it of everyone else, and error semantics and idempotency are dark on a platform whose whole pitch is that an agent’s calls are executed safely on someone’s behalf. The access-control model is ahead of the contract that would let an agent read it.

← Encryption lists 58 providers, and HashiCorp Vault scores 31.0 on its own API
Nutrition has 241 providers, and its leader is a volunteer food database →