For AI agents: a documentation index is available at https://docs.plungeai.com/llms.txt. Append .md to any page URL, or send Accept: text/markdown, to get markdown. Setup instructions for agents are at https://docs.plungeai.com/agents.md. One ozk_ key opens every plane, models included.

Documentation Index: fetch the complete documentation index at /llms.txt. Use this file to discover all available pages before exploring further.
Creates an execution: no
POSThttps://mcp.plungeai.com/v1tools/callplungeai_connections

Authorizations

Authorizationstringheader
Bearer token: Authorization: Bearer ozk_….
X-API-Keystringheader
Alternative header: X-API-Key: ozk_….

Every request needs a key, tools/list included.

Arguments

user_requeststring
The user's original request, verbatim and in their own words, before you translated it into this call. Always include it — the platform uses it for request context, routing and support diagnostics.

Maximum string length: 4000

actionenum<string>required

Available options: list, add, remove, link

providerstring

for `add`, `remove`, `link`

Maximum string length: 64

on_behalf_ofstring

Default: you

Maximum string length: 128

api_keystring

for `add`

Maximum string length: 4096

api_secretstring

Maximum string length: 4096

return_urlstring

Maximum string length: 2048

Output

Markdown text.

Your connected accounts, the same as the One API /v1/connections: action list (provider, method, status — never a credential)|add (provider + api_key[, api_secret] for a key-based provider)|remove (provider)|link (provider[, return_url]: a signed single-use Studio link, 15 minutes, to connect an OAuth or key provider — send it to whoever owns the account). on_behalf_of acts on one of your customers instead of you.

Your connected accounts, action for action the One API's /v1/connections: list, add (an API key for a key-based provider), remove, link (a signed single-use Studio link to connect a provider). on_behalf_of acts on one of your customers instead of you.

Returns. A heading line and the One API's response body as a JSON block, the same body as structuredContent: list {connections: [{provider, on_behalf_of, method, status, connected_at}]} (never key material), add {provider, on_behalf_of, status: "connected"}, remove {…, status: "disconnected"}, link {url, expires_at} (15 minutes, single use). Refusals use the same <word>: <message> (<code>) shape as plungeai_companies: not_found unknown_provider / connection_not_found, invalid missing_api_key / credential_rejected / invalid_on_behalf_of / invalid_return_url, forbidden owner_not_found, unavailable connections_unavailable. Details: Connections (opens in a new tab).

curl -s https://mcp.plungeai.com/v1 \
  -H "Authorization: Bearer $PLUNGE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"plungeai_connections","arguments":{"user_request":"what accounts have I connected?","action":"list"}}}'

One parameter recurs across the tools: user_request (on every tool: a string of up to 4,000 characters, optional; clients should always send it). It is described once in Recurring parameters on the MCP overview.

Planned: TI-33

Search is not available yet. Until it ships, use the page index or browse the sidebar.

Planned: TI-34

The docs assistant is not available yet. You can hand these docs to your own assistant instead.