stork_install
Set up an MCP server for the user: say what they want connected (Notion, Supabase, Sentry, Postgres, a browser) and their client, and get the config to write, what the user must supply (a sign-in or keys), and who publishes the server. Stork picks the vendor's own server where there is one. Use this when the tool needs the user's own account, which Stork cannot use for them. Show the user who publishes the server before writing the config.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"name": "<name>"
},
"name": "stork_install"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The product or job, for example Notion, Supabase, browser automation. | |
| client | No | The user's MCP client: cursor, claude-desktop, claude-code, vscode, zed. Any other name gets the common mcpServers JSON. |