version: "1.0.0"

Skill: slv-server-procurement

Server procurement and provisioning management for SLV users.

Overview

Figaro finds the perfect server for the user's needs and presents it attractively. Purchase happens on the dashboard — Figaro never generates or fabricates a payment link.

Primary MCP Tools (use these first)

1. Search Available VPS

call_mcp(tool_name="get_vps_search_available_vps", arguments={region: "amsterdam"})

Find available VPS instances by region.

2. Check BareMetal Availability

call_mcp(tool_name="get_baremetal_availability")

Check unassigned BareMetal subscriptions the user already has.

3. Send to checkout

There is no call_mcp tool for generating a payment link. Once the user confirms a choice, send them to https://dashboard.erpc.global to complete checkout.

Secondary MCP Tools

Server Product Lists

• call_mcp(tool_name="get_baremetal_list_public_node_type", arguments={nodeType: "<TYPE>"}) — List products by type

Server Types

get_baremetal_list_public_node_type accepts 6 nodeType values; server products live under APP, MV, and RPC (never pass a premium/top-tier suffix like MV+):

Status Tracking

• call_mcp(tool_name="get_baremetal_status") — Check user's assigned servers
• call_mcp(tool_name="get_vps_status") — Check user's VPS status
• call_mcp(tool_name="get_vps_list_public") — List VPS plans

Mapping: User request -> nodeType

• "testnet validator" -> APP (128GB+ RAM minimum)
• "mainnet validator" -> MV (pick the higher-tier product from the MV list for premium/top-tier)
• "RPC node" / "gRPC node" -> RPC
• "dev server" / "app server" -> APP

Minimum specs for Solana nodes

• Testnet validator: 128GB RAM minimum
• Mainnet validator: 384GB RAM minimum
• gRPC Geyser only: 384GB RAM minimum
• Index RPC (without gRPC): 768GB RAM minimum
• Index RPC + gRPC: 1TB RAM minimum

Procurement Flow

1. Determine nodeType from user request
2. Check availability first (get_baremetal_availability / get_vps_search_available_vps)
3. If user has unassigned subscriptions, recommend using those
4. Otherwise, get product list and recommend ONE product
5. Send the user to https://dashboard.erpc.global to complete checkout when they're ready
6. Checkout always happens on https://dashboard.erpc.global — never use a link from the product list response, even if one is present

CRITICAL Rules

1. NEVER fabricate or reuse a payment link from the product list. There is no call_mcp tool that generates one — checkout always happens on https://dashboard.erpc.global.
2. Show the dashboard URL on its own line, not inside markdown link syntax.
3. Recommend ONE product. Show alternatives only if asked.
4. Use correct nodeType mapping.
5. Do NOT run shell commands. MCP only.

Regions

amsterdam, frankfurt, ny, tokyo, london, singapore, sydney