Install Mcp
Fill a card’s template and add the result to the user’s library.
Installing is a user-level act with no workspace involved — putting
the MCP into a session’s workspace is separate and explicit. The
record keeps (hub_id, card_id) so the library can later answer
“where did this come from” and “is there a newer version”.
Note that the config is not connection-tested here, so a mistyped API key surfaces on first use rather than now. Testing it would mean connecting from the app process, and a stdio MCP would then spawn its command here instead of in the workspace sandbox.
Headers
Caller's user ID. Temporary header-based identity; will be replaced by JWT auth.
Body
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.