Skip to main content
Korve’s streamable HTTP MCP endpoint is https://mcp.korve.dev/mcp. Legacy API-key setup:
Use an organization-scoped key with the least role the agent needs. MCP clients that implement protected-resource and authorization-server discovery, dynamic public-client registration, authorization code with S256 PKCE, and rotating refresh tokens can instead request a grant bound to audience mcp and exact operation scopes; see Agent OAuth. Never reuse a CLI-audience token. The MCP transport authenticates before initialization, so every client connection needs an MCP-audience credential. Once connected, search only reads the bundled public contract and makes no API request; execute additionally enforces the credential’s exact operation scopes.

​
Search the contract

search accepts a text query, a resource name, or no arguments for the compact public index. A match includes operation id, method, path, auth, minimum role, risk, approval requirement, parameters, and body schema.

​
Execute bounded JavaScript

After searching, call execute with JavaScript. The sandbox exposes only korve.request({ method, path, query?, body? }), console logging, and ordinary language features.
The result is { result, logs, requests }; requests records method/path operations and response status for the run. The sandbox cannot use direct network access, filesystem or environment access, provider SDKs, or internal/runtime-only routes. A request must match a public operation from the spec before authenticated dispatch. Search results label safe, write, dangerous, and destructive operations. The MCP host should require approval for risky tool execution, and the platform agent separately persists mutations as pending actions. See Safe automation.