Tools
plungeai_chat
Persistent chat with the PlungeAI assistant (platform tools + web search). action send|new|list_sessions|history. Conversations appear in Studio and the CLI.
Authorizations
Authorization: Bearer ozk_….X-API-Key: ozk_….Every request needs a key, tools/list included.
Arguments
Maximum string length: 4000
Available options: send, list_sessions, history, new
for `send`
Maximum string length: 65536
for `history`
Default: a new conversation (send)
Maximum string length: 256
Output
Markdown text.
Persistent chat with the PlungeAI assistant (platform tools and web search): action send, new, list_sessions or history. Conversations appear in Studio and the CLI.
Returns. send: the assistant's reply and _(conversation: `<id>`)_. new: Created conversation `<id>`. …. list_sessions: # Your conversations (N) (Title, ID, Messages) for the 20 most recent, or No conversations yet.. history: # <title> and every turn. Details: 10.1 (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_chat","arguments":{"user_request":"list my conversations","action":"list_sessions"}}}'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.