Update Mcp
Rename, enable/disable, or re-key an installed MCP.
Changing a secret is a re-render, not a field edit: an API key can sit anywhere in the config — inside a URL, a header, an env var — so the card’s template plus the merged answers is the only thing that knows where to put it.
Headers
Caller's user ID. Temporary header-based identity; will be replaced by JWT auth.
Path Parameters
Body
The body of a library edit. Omitted fields are left alone.
A new name. Must match [a-zA-Z0-9_-]+ and stay unique for this user.
New answers to the card's inputs_schema, merged over the stored ones — send only the keys that changed. The config is re-rendered from the card, so this needs the originating hub to still be registered and reachable.
Whether the MCP is turned on.
Response
Successful Response
One installed MCP, as shown in the user's library.
The rendered mcp_config is deliberately left out: it carries the
inputs the user filled in at install time, API keys included, and
nothing on this screen needs them.
The installed-MCP record id.
The MCP name, unique for this user.
Whether it needs a session.
Whether the user has it turned on.
The card's user-facing name at install time.
The card's description at install time.
The card's tags at install time.
Who published the MCP, at install time.
The card's icon at install time.
The MCP's page on the hub's website.
The hub it came from, or null when added by hand.
The card's id on that hub.
The card version installed.