Core concepts / Namespaces and endpoint bundles

Namespaces and endpoint bundles

Namespaces own connections; endpoint bundles publish combinations of them.

Connection namespaces own credentials

A connection namespace is a folder such as Lelapa or Personal. Every connection belongs to one namespace and owns one credential grant. The same provider can appear in many namespaces because method definitions are reusable while credentials are not.

Lelapa / Notion   → lelapa_notion__search
Personal / Notion → personal_notion__search

The current API calls these /api/connection-namespaces.

Endpoint bundles publish shared combinations

An endpoint bundle combines existing shared or service connections behind /mcp/{slug}. Adding a connection does not copy its credential, move its namespace, or rename its tools, and one eligible connection may belong to several bundles. Personal connections are rejected. The current API uses /api/endpoints; /api/namespaces remains a legacy alias for endpoint bundles.

Membership stays live

The URL stays stable while an owner or admin changes bundle membership. Deleting a bundle advances its token epoch, so recreating the same slug does not make previously issued tokens valid again.