Proxmox LangChain Agent

Created By
johnstettera year ago
langchain-based client for proxmox mcp server - co-pilot experiment
Overview

what is Proxmox LangChain Agent?

Proxmox LangChain Agent is a lightweight FastAPI service that provides a chat endpoint backed by LangChain and Redis-based message history, designed to interact with a Proxmox MCP (Model Context Protocol) server for conversational access to Proxmox cluster and VM information.

how to use Proxmox LangChain Agent?

To use the agent, you need to set up a Proxmox MCP server and a Redis instance. After building the Docker image, run the container and send a POST request to the /chat endpoint with your query in JSON format.

key features of Proxmox LangChain Agent?

  • FastAPI-based chat service for Proxmox management.
  • Integration with LangChain for advanced conversational capabilities.
  • Redis for persistent message history.
  • Custom tools for retrieving VM and cluster information.

use cases of Proxmox LangChain Agent?

  1. Managing Proxmox VMs through conversational queries.
  2. Retrieving cluster status and VM lists via chat.
  3. Automating Proxmox management tasks using natural language.

FAQ from Proxmox LangChain Agent?

  • What is required to run the Proxmox LangChain Agent?

You need Docker, a Redis instance, and access to a Proxmox MCP server.

  • How do I send a query to the agent?

Send a POST request to /chat with a JSON body containing your message.

  • Can I extend the agent with new tools?

Yes! You can define new functions and add them to the tools list in the app.py file.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
johnstetter
Star
0
Language
Python
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago