VoltAgent MCPConfiguration: connect to the Sume hosted MCP server

In VoltAgent, declare a server in MCPConfiguration with type: "http", url: "https://mcp.sume.com/mcp" and requestInit: { headers: { Authorization: "Bearer ..." } }. VoltAgent's docs say the http type tries Streamable HTTP first and falls back to SSE, which suits Sume, since its docs tell remote clients to use Streamable HTTP.

VoltAgent's side is its MCP docs; Sume's side is OAuth and API keys and MCP tools and gates. Both were read on 2026-10-06. Sume has no official VoltAgent integration.

Which fields matter?

The docs then show the flow: call getTools() on the configuration, pass the result to the agent as tools, and call disconnect() when finished.

What should I do before a paid call?

getTools() returns what the credential sees. An API key sees paid tools, so decide which the agent gets. Sume's docs recommend tools_schema for one tool's contract and dry_run=true or generation_admission_preview before paid creates. idempotency_key is required on paid and write calls; max_spend_usd is optional and enforced only when the call includes it, so tell the agent to send it every time.

Key hygiene

Read the key from an environment variable at startup and never paste it into a prompt. Sume's safe-automation page lists API keys and signed URLs as unsafe to log, and says to log request ids and job ids instead.