{"name":"Casii MCP","transport":"Streamable HTTP","method":"POST","headers":{"Authorization":"Bearer <API_KEY>","Content-Type":"application/json","Accept":"application/json, text/event-stream"},"requests":[{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-11-25","capabilities":{},"clientInfo":{"name":"casii-http","version":"1.0"}}},{"jsonrpc":"2.0","method":"notifications/initialized"},{"jsonrpc":"2.0","id":2,"method":"tools/list"},{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"get_export_tool","arguments":{"export_type":"instagram_profile_followers"}}}],"usage":"POST each request to the supplied MCP URL, including its trailing slash. After initialize, send notifications/initialized without id and use the returned protocolVersion as Mcp-Protocol-Version. Read result.structuredContent; check result.isError.","rules":"Tool descriptions and schemas returned by tools/list are authoritative; do not guess arguments. Creation/resumption spend credits: show the target, quantity and quoted credits and get explicit user confirmation first. If a paid call outcome is uncertain, retry with the same idempotency_key and arguments; a new key is a new paid operation.","installation":"Ask which AI client is used if unclear, then follow its official Streamable HTTP configuration format and name the server casii. Merge with existing servers. By default configure only the MCP URL with no auth header: clients that support MCP authorization (OAuth) open the Casii consent page in the browser on first connect, the user signs in and approves, and the client obtains tokens itself. If no browser opens and requests keep returning 401, tell the user instead of inventing credentials. Only when an API key is supplied, send it in the Authorization header; prefer user-level config or client secrets/environment variables, keep the key out of URLs and version control, and explain unsupported headers instead of writing invalid config. Verify with tools/list, report whether a restart is needed, and create no paid tasks.","authentication":"API keys and connected apps access the owner’s business tools and tasks, not only the current tool. HTTP 401 carries a WWW-Authenticate challenge: OAuth-capable clients follow it to authorize in the browser; with an API key, obtain a valid key. Revoke keys and disconnect apps in API Keys. Send credentials only to the supplied MCP host."}