Edgevana Compute Agent

Edgevana compute, in your AI agent

Hourly GPU instances for AI agents, over MCP and A2A. Agents search offers, launch, monitor and destroy instances, and every launch shows a preview: nothing is charged until you approve it.

~/.cursor/mcp.json

{
  "mcpServers": {
    "edgevana": {
      "url": "https://mcp.edgevana.com/mcp",
      "headers": {
        "X-API-Key": "<your-edgv_...-key>"
      }
    }
  }
}
  • Tools13
  • ProtocolsMCP + A2A
  • GPU billingHourly
  • Before every launchA preview
01Protocols

One server. Two ways in

MCP for IDEs and agent apps, A2A for agents that read an Agent Card. Both use the same Edgevana API.

MCP

Model Context Protocol

A standard way for AI apps to use outside tools: like USB for agents. Add the server URL and your API key, and the tools appear.

  • Cursor
  • Claude
  • VS Code
  • ChatGPT
  • 20+ apps

A2A

Agent-to-Agent Protocol

Agents discover Edgevana from its Agent Card and send it task messages. Send your API key with each request.

  • LangChain
  • CrewAI
  • AutoGen
  • Any A2A v0.3 client
02Get started

Add Edgevana to your AI app

Five steps, about as many minutes. Pick one to see what goes where.

nodes.edgevana.com → Profile → API Keys

# Your key starts with edgv_
export EDGEVANA_API_KEY=edgv_…
03Reference

URLs, auth and all 13 tools

Seven tools for discovery and pricing, six for instances. MCP clients call them directly; A2A agents send task messages for the same actions.

  • Agent Cardhttps://edgevana.com/.well-known/agent-card.json
  • MCPhttps://mcp.edgevana.com/mcp
  • A2A JSON-RPChttps://mcp.edgevana.com/a2a/jsonrpc
  • A2A RESThttps://mcp.edgevana.com/a2a/rest
Auth
X-API-Key: edgv_… or Authorization: Bearer edgv_…
Transport
Streamable HTTP
Versions
MCP 2025-03-26 to 2025-11-25, A2A v0.3

Deposit. Hourly GPU takes a non-refundable deposit when an instance is created. The amount depends on the hourly price, and the launch preview shows it (deposit.due_today). Credit on the account counts towards it, and it comes back as credit against usage. Bare-metal and CPU servers can be searched and priced, not launched.

Discovery and pricing 7

Instance lifecycle 6

These are the MCP names. A2A supports the same actions except request_reserved_instance; there, compare_to_cloud is compare_cloud and get_platform_info is platform_info.

04Lifecycle

From search to a running server

Nothing is created or charged until you approve the preview and the agent confirms.

  1. Search

    search_servers

    Pick an offer with launch_status "available" and note its offer_id and one of its hourly_sites.

  2. Preview the launch

    launch_instance

    launch_instance without confirm returns the hourly price and an approval object, with the deposit due today when it can be quoted. Nothing is created.

    You approve
  3. Confirm the launch

    launch_instance · confirm: true

    If the preview offered a replacement, show substituted.note first. Once you approve: the same call (with substituted.offer_id and substituted.site if present) plus confirm: true, the approval unchanged and a unique idempotency_key. Nothing launches above the approved price or deposit; if the offer was taken, an equivalent one at the same site may launch within them.

  4. Monitor

    get_instance

    get_instance reports connection.status, and the mapped ports once ready.

    • ready
    • provisioning
    • failed
    • destroying
    • destroyed
  5. Destroy

    terminate_instance

    terminate_instance previews first, then runs with confirm: true. Hourly GPU instances go immediately.

05Connect

Configs to copy

Pick your app, copy its config and replace the placeholder with your key.

Run in your terminal, then claude mcp list to confirm.

claude mcp add --transport http edgevana https://mcp.edgevana.com/mcp --header "X-API-Key: YOUR_EDGV_KEY"
Get your API key

Talk to us

Building on Edgevana compute?

Connecting over *

We use these details only to answer you. See our Privacy Policy.