Proxmox MCP Server

Proxmox MCP Server

Enables natural language interaction with Proxmox VE clusters for managing VMs, containers, storage, and snapshots.

Category
访问服务器

README

<div align="center">

<a href="https://soyrage.es/"> <img src="./assets/soyrage-banner.svg" alt="SoyRage Agency — Full-Stack Developer × Infrastructure Engineer · soyrage.es" width="100%"> </a>

<br/>

🖥️ Proxmox MCP Server

Chat with your Proxmox VE cluster. A Model Context Protocol server that turns any MCP‑capable AI — Claude Desktop, Cursor, Continue, Zed — into a natural‑language operator for Proxmox Virtual Environment: nodes, QEMU VMs, LXC containers, storage, tasks and snapshots.

“List my VMs and which are down.” · “How much RAM is web (VMID 101) using?” · “Snapshot db before I upgrade it.” · “Gracefully shut down container 200.”

<br/>

<img src="./assets/screenshots/tui-dashboard.png" alt="Proxmox MCP Server terminal dashboard by SoyRage Agency — tabs, live gauges, guest OS, snapshots and one-key actions" width="88%">

<sub>💻 The built‑in proxmox-mcp-tui terminal dashboard — tabbed views (Guests · Nodes · Storage · Tasks), live CPU/memory/disk gauges, guest OS, search, snapshots and one‑key actions. <a href="#-the-terminal-ui-tui">More screenshots ↓</a></sub>

<br/><br/>

CI Node TypeScript MCP Proxmox VE License: SRAL Donate

Designed, built & maintained by SoyRage Agency · https://soyrage.es/

⚡ New here? Install in one command → Quick install. · ☕ Support the project

</div>

🐳 Looking for the Docker equivalent? See the sister project docker-mcp-server — same philosophy, for Docker & Compose.

📑 Table of contents

⚡ Quick install (one command)

Never done this before? It's 3 steps and about 3 minutes. You do not need to touch any config file — a friendly wizard asks you a few questions and sets up everything.

✅ Step 1 — Install the two things you need (once)

  • Node.js (click the big green “LTS” button, next‑next‑finish).
  • Git.

✅ Step 2 — Run one command

<table> <tr><td><b>🪟 Windows</b><br/><sub>PowerShell</sub></td><td>

irm https://raw.githubusercontent.com/soyrageagency/proxmox-mcp-server/main/install.ps1 | iex

</td></tr> <tr><td><b>🍎 macOS / 🐧 Linux</b><br/><sub>Terminal</sub></td><td>

curl -fsSL https://raw.githubusercontent.com/soyrageagency/proxmox-mcp-server/main/install.sh | bash

</td></tr> </table>

✅ Step 3 — Copy‑paste your details when the wizard asks

That's it — the wizard walks you through it and tests the connection for you:

  This wizard sets everything up in under a minute. You'll need:
    1. Your Proxmox web address (the one you log in to).
    2. An API token (safest) — or your Proxmox username + password.

  Proxmox address (e.g. https://192.168.1.10:8006): https://10.0.0.11:8006
  Do you have an API token? (Y/n): y
  Token ID (user@realm!name, e.g. root@pam!mcp): root@pam!mcp
  Token secret (paste the UUID): ••••••••-••••-••••-••••-••••••••••••
  Verify the TLS certificate? (most Proxmox use self-signed → No) (y/N): n
  Read-only mode? (view only — safest) (y/N): n

  Testing the connection…
  ✓ Connected to Proxmox VE (8.2.4)
  ✓ Saved credentials to .env
  ✓ Added the "proxmox" server in your Claude config.

  All set!  →  restart Claude Desktop and ask "List my Proxmox VMs."

Then restart Claude Desktop and say: “List my Proxmox VMs and containers.” 🎉

<details><summary><b>Don't have an API token yet? (create one in ~20 seconds)</b></summary>

In the Proxmox web UI: Datacenter → Permissions → API Tokens → Add, pick user root@pam, name it mcp, and copy the secret (shown once). Your token ID is root@pam!mcp. Full details in Create a Proxmox API token. Prefer not to now? The wizard also accepts your username + password. </details>

<details><summary><b>Already cloned the repo, or want to re-run setup?</b></summary>

Run npm run setup from the project folder. The installer backs up and merges your existing Claude config, so other MCP servers are preserved. </details>

<details><summary><b>No Proxmox cluster to test with?</b></summary>

Try demo mode — realistic fake data, no host needed. </details>

💙 If this saves you time, please support the project on PayPal and drop a ⭐.

🧭 What is this?

The Model Context Protocol (MCP) is an open standard that lets AI assistants talk to external tools over a well‑defined JSON‑RPC interface. Proxmox MCP Server is an MCP server that speaks that protocol over stdio and exposes your Proxmox VE cluster as a set of safe, richly‑described tools.

Point any MCP‑capable assistant at it and you can operate your virtualization stack in plain language — the model reads each tool's schema, decides which to call against the Proxmox REST API, and reports the results back to you. Built for home‑labbers and sysadmins who'd rather ask than remember qm and pct flags.

🚀 Feature overview

Area Capabilities
🧭 Cluster List nodes with load, node status, cluster quorum/membership, and a consolidated cluster_resources view.
🖥️ Guests List QEMU VMs and LXC containers (filter by kind / running), live status, full config, and guest OS (via the QEMU agent — name, version, IPs).
⚙️ Lifecycle Start · graceful shutdown · hard stop · reboot · suspend/resume — for VMs and containers.
🚚 Management Migrate to another node · clone (from templates) · resize CPU/RAM · delete.
📦 Backups Backup (vzdump) · list archives · restore into a VMID.
🧱 Provisioning List templates/ISOs · create LXC containers and QEMU VMs.
📸 Snapshots List, create (optionally with RAM), rollback and delete snapshots.
💾 Storage List storages per node with type, content and usage.
🧾 Tasks Recent task log per node (backups, migrations, actions…).
⌨️ Terminal UI A creative, lazydocker‑style TUI (proxmox-mcp-tui) with live gauges, guest OS, and one‑key actions.
🛡️ Safety Global read‑only mode · guest allowlist (by VMID or name) · TLS verification control.
🔐 Auth API token (recommended) or username/password ticket auth.
🧩 Modular Every capability is a toggleable plugin — expose exactly the surface you want.
🧱 Engineering 100% TypeScript, strict mode · tiny dependency surface · stderr‑only logging.

🛠️ How it works

                 ┌──────────────────────────────────────────────┐
   You  ◀──────▶ │  AI assistant (Claude / Cursor / Continue …)  │
                 └───────────────────────┬──────────────────────┘
                              stdio · JSON‑RPC (MCP)
                 ┌───────────────────────▼──────────────────────┐
                 │              Proxmox MCP Server               │
                 │   config → auth → tool call → Proxmox API     │
                 └───────────────────────┬──────────────────────┘
                          HTTPS · /api2/json (token or ticket)
                 ┌───────────────────────▼──────────────────────┐
                 │        Proxmox VE node / cluster (:8006)      │
                 └───────────────────────────────────────────────┘

The server calls the Proxmox VE REST API (https://<host>:8006/api2/json). It resolves each guest's node automatically from /cluster/resources, so you address VMs and containers simply by VMID or name — no need to know which node they live on.

✅ Requirements

Requirement Notes
Node.js ≥ 18 ES modules + global fetch. Node 20+ recommended.
A Proxmox VE 7/8 node or cluster Reachable on its API port (8006).
An API token (recommended) Or a user/password. See Create a Proxmox API token.
An MCP client Claude Desktop, Cursor, Continue, Zed, or the MCP Inspector.

📦 Installation

git clone https://github.com/soyrageagency/proxmox-mcp-server.git
cd proxmox-mcp-server
npm install
npm run build

🧪 Try it instantly — demo mode (no Proxmox needed)

Want to evaluate it right now without a cluster? Run in demo mode — the server serves a believable 2‑node lab (VMs, containers, storage, snapshots):

npm run build
PROXMOX_MCP_DEMO=true npm run inspect     # explore every tool in the MCP Inspector

Or point Claude Desktop at it with "PROXMOX_MCP_DEMO": "true" in the env block and ask “List my Proxmox VMs and containers.” You'll get output like:

VMID  KIND  NAME           NODE  STATUS   CPU   MEMORY          UPTIME
100   VM    web            pve   running  3.1%  1.8 GB/4.0 GB   22d 23h
101   VM    db             pve   running  8.7%  6.2 GB/8.0 GB   22d 23h
200   CT    nginx-proxy    pve   running  0.4%  96.0 MB/512 MB  22d 22h
201   CT    grafana        pve   running  1.2%  240 MB/2.0 GB   13d 21h

When you're ready, set PROXMOX_MCP_DEMO=false and add your real host + token.

With a real cluster

npm run inspect     # after setting PROXMOX_HOST + token (see below)

⌨️ The terminal UI (TUI)

Prefer the terminal? Launch proxmox-mcp-tui — a creative, professional, lazydocker‑style dashboard for your cluster that opens with a SoyRage Agency welcome, then drops you into a live, keyboard‑driven view. Hand‑rolled ANSI, zero UI dependencies.

npm run build
npm run tui        # → interactive terminal dashboard
npm run tui:demo   # same, with realistic mock data (no cluster needed)

<div align="center">

A warm welcome

<img src="./assets/screenshots/tui-welcome.png" alt="SoyRage Agency Proxmox terminal welcome" width="80%">

Guests — OS, live gauges & one‑key actions

<img src="./assets/screenshots/tui-dashboard.png" alt="Proxmox MCP terminal UI by SoyRage Agency" width="92%">

Tabbed views — Nodes · Storage · Tasks

<img src="./assets/screenshots/tui-storage.png" alt="Proxmox MCP terminal UI storage view by SoyRage Agency" width="92%">

🤖 Give orders to the AI — in plain language

<img src="./assets/screenshots/tui-ai.png" alt="Proxmox MCP terminal UI AI command bar by SoyRage Agency" width="92%">

<sub>Rendered in <b>demo mode</b> · watermarked © SoyRage Agency · soyrage.es</sub>

</div>

Features

  • Tabbed views — 1 Guests · 2 Nodes · 3 Storage · 4 Tasks (or Tab to cycle), each with column headers and usage bars.
  • 🤖 AI command bar — press a and type an order in plain English: “restart db”, “shutdown 200”, “which VMs are down?”, “how much RAM is web using?”. The AI proposes the action and asks you to confirm before it runs — questions get an instant answer. Powered by any OpenAI‑compatible endpoint (OpenAI, Ollama, LM Studio…); demo mode simulates it.
  • Live — a clock and cluster name in the header, auto‑refreshing every 5 s.
  • Search — press / to filter guests by name or VMID.
  • Help overlay — press ? for a keyboard cheat‑sheet.
  • Safe actions — destructive stop and every AI action ask for a y/n confirmation; read‑only mode hides all action keys.
  • Rich details — the selected guest shows its OS (via the QEMU agent), CPU/memory/disk gauges, cores and uptime; press s for its snapshots.

Keys: 1‑4/Tab views · ↑/↓ (or j/k) navigate · / filter · a ask AI · s snapshots · S start · d shutdown · x stop · b reboot · r refresh · ? help · q quit. VMs are cyan, containers magenta.

💡 Enable the AI with PROXMOX_MCP_AI_ENDPOINT (+ _KEY, _MODEL). Works with Ollama locally for free. Without it, the bar still understands common orders via a built‑in rule engine.

🔑 Create a Proxmox API token

An API token is the safest way to authenticate (no password stored, revocable, scopable).

  1. In the Proxmox web UI go to Datacenter → Permissions → API Tokens → Add.
  2. Pick a User (e.g. root@pam) and a Token ID (e.g. mcp). Copy the generated secret — it's shown only once.
    • Your PROXMOX_TOKEN_ID is then root@pam!mcp.
  3. Give the token permissions. For full control assign the PVEAdmin role at path /; for read‑only use PVEAuditor. (Uncheck Privilege Separation to inherit the user's privileges, or add an ACL for the token.)
  4. Put the values in your MCP client config / .env:
    PROXMOX_HOST=https://192.168.1.10:8006
PROXMOX_TOKEN_ID=root@pam!mcp
PROXMOX_TOKEN_SECRET=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Prefer least privilege: pair a PVEAuditor token with PROXMOX_MCP_READONLY=true for a safe, view‑only assistant.

🔌 Connecting to your AI client

Add the server to your MCP client. Example for Claude Desktop (%APPDATA%\Claude\claude_desktop_config.json on Windows, ~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "proxmox": {
      "command": "node",
      "args": ["/absolute/path/to/proxmox-mcp-server/dist/index.js"],
      "env": {
        "PROXMOX_HOST": "https://192.168.1.10:8006",
        "PROXMOX_TOKEN_ID": "root@pam!mcp",
        "PROXMOX_TOKEN_SECRET": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
        "PROXMOX_VERIFY_TLS": "false",
        "PROXMOX_MCP_READONLY": "false"
      }
    }
  }
}

A ready‑to‑edit copy lives in examples/claude_desktop_config.json. Restart your client and ask: “What Proxmox nodes and VMs do I have?” — the assistant will greet you on behalf of SoyRage Agency and take it from there.

⚙️ Configuration reference

Every setting is an environment variable. A local .env is loaded automatically; a JSON config file (proxmox-mcp.config.json) provides defaults. Precedence (low → high): defaults → config file → .env → environment. See .env.example.

Variable Default Description
PROXMOX_HOST — API base URL, e.g. https://192.168.1.10:8006.
PROXMOX_TOKEN_ID — API token id user@realm!tokenname (recommended).
PROXMOX_TOKEN_SECRET — API token secret (UUID).
PROXMOX_USER — user@realm for ticket auth (used only if no token).
PROXMOX_PASSWORD — Password for ticket auth.
PROXMOX_VERIFY_TLS false Verify the node's TLS certificate.
PROXMOX_MCP_READONLY false Hide all state‑changing tools.
PROXMOX_MCP_DEMO false Serve fabricated demo data (no real host needed).
PROXMOX_MCP_ALLOWLIST — Comma‑separated VMIDs/names the AI may touch (empty = all).
PROXMOX_MCP_PLUGINS — Load only these plugins (empty = all).
PROXMOX_MCP_DISABLED_PLUGINS — Disable these plugins. about is locked.
PROXMOX_MCP_LOG_LEVEL info debug | info | warn | error.
PROXMOX_MCP_AI_ENDPOINT — OpenAI‑compatible base URL for the TUI's AI copilot (empty = rule‑based).
PROXMOX_MCP_AI_KEY — Bearer key for the AI endpoint.
PROXMOX_MCP_AI_MODEL gpt-4o-mini Model name for the AI endpoint.
PROXMOX_MCP_CONFIG proxmox-mcp.config.json Path to the optional JSON config file.

🔒 TLS & self‑signed certificates

Proxmox ships a self‑signed certificate by default, so PROXMOX_VERIFY_TLS=false (the default) is expected for most home‑labs — the connection is still encrypted, just not certificate‑verified. TLS control is per‑request (via undici), so it does not disable verification globally for your process.

Set PROXMOX_VERIFY_TLS=true only when your node presents a certificate your system trusts (e.g. a Let's Encrypt cert, or an internal CA / reverse proxy in front of :8006).

🛡️ Security model & networking

This server can control your infrastructure — treat access like root SSH.

Control What it does
Read‑only mode (PROXMOX_MCP_READONLY=true) Hides every lifecycle/snapshot‑mutating tool. Pair with a PVEAuditor token.
Guest allowlist (PROXMOX_MCP_ALLOWLIST) Restricts all guest tools to matching VMIDs/names; anything else returns a clear error.
Scoped API token Grant the token only the privileges it needs; revoke instantly from the UI.
Least privilege PVEAuditor + read‑only = a safe, view‑only assistant.

Networking: the Proxmox API listens on :8006. Reach a remote node over a VPN (WireGuard / Tailscale) rather than exposing 8006 to the Internet. The MCP server runs locally beside your AI client and connects out to Proxmox — it opens no inbound ports of its own.

Safety recipes

# View-only assistant (great for demos / dashboards)
PROXMOX_MCP_READONLY=true          # + a PVEAuditor token

# Only let the AI manage two specific guests
PROXMOX_MCP_ALLOWLIST=101,web

# Expose only cluster/guest insight, no storage/tasks
PROXMOX_MCP_PLUGINS=nodes,guests,cluster

🧰 Complete tool reference

Tools marked W change state and are hidden when PROXMOX_MCP_READONLY=true. Guests are addressed by VMID or name.

Identity

Tool Description
about Credits, license and the SoyRage Agency welcome banner.
list_plugins The modular plugins and whether each is enabled.

Insight (read‑only)

Tool Parameters Description
list_nodes — Cluster nodes with status, CPU and memory.
node_status node Detailed status of one node.
list_guests kind? (qemu/lxc), runningOnly? All VMs & containers with live stats.
guest_status guest Live status of one VM/container.
guest_config guest Full configuration of one guest.
guest_osinfo guest The guest's operating system (agent name/version + IPs).
list_storage node Storages on a node with usage.
list_tasks node, limit? Recent tasks on a node.
cluster_status — Cluster membership & quorum.
cluster_resources type? Consolidated nodes/guests/storage view.
list_snapshots guest Snapshots of a VM/container.
list_backups node?, storage? vzdump backup archives with VMID, size, age.
list_templates node? Container templates (vztmpl) and install ISOs.

Lifecycle (W)

Tool Parameters Description
start_guest guest Power on a VM/container.
shutdown_guest guest, timeout? Graceful ACPI/OS shutdown (preferred).
stop_guest guest Hard stop (power‑cord). Destructive — confirm first.
reboot_guest guest Graceful reboot.
suspend_guest guest, toDisk? Pause a VM in RAM (or hibernate to disk).
resume_guest guest Resume a suspended VM.

Management (W)

Tool Parameters Description
migrate_guest guest, target, online? Move a guest to another node (live if running).
clone_guest guest, newid, name?, full?, target? Clone a VM/CT (e.g. from a template).
set_guest_resources guest, cores?, memory? Quickly change CPU cores / RAM (MB).
backup_guest guest, storage, mode?, compress? Create a vzdump backup to a storage.
delete_guest guest, confirm, purge? Destroy a guest (guarded: confirm must equal the VMID).

Backups & provisioning (W)

Tool Parameters Description
restore_backup volid, vmid, node?, storage?, force? Restore a vzdump archive into a VMID.
create_container vmid, ostemplate, storage, hostname?, cores?, memory?, diskGb?, … Create an LXC container from a template.
create_vm vmid, storage, name?, diskGb?, cores?, memory?, iso?, ostype?, … Create a QEMU VM (with a disk + optional install ISO).

Snapshots (W)

Tool Parameters Description
create_snapshot guest, name, description?, withRam? Take a snapshot (optionally with VM RAM).
rollback_snapshot guest, name Revert to a snapshot (destructive).
delete_snapshot guest, name Remove a snapshot.

💬 Example conversations

You say… The assistant calls…
“Show me all my VMs and containers.” list_guests
“Which containers are running?” list_guests { kind: "lxc", runningOnly: true }
“Is node pve healthy?” node_status { node: "pve" }
“How is VMID 101 doing?” guest_status { guest: "101" }
“Snapshot db before the upgrade.” create_snapshot { guest: "db", name: "pre-upgrade" }
“Gracefully shut down container 200.” shutdown_guest { guest: "200" }
“How full is storage on pve?” list_storage { node: "pve" }
“What happened on pve recently?” list_tasks { node: "pve" }
“Who built this?” about

🧩 Modular plugin architecture

The server is assembled from independent plugins, each owning one capability group; which load is driven entirely by configuration. The about plugin is locked — it carries the SoyRage Agency identity and cannot be disabled.

Plugin Category Type Tools
about 🔒 identity read about, list_plugins
nodes nodes read list_nodes, node_status
guests guests read list_guests, guest_status, guest_config, guest_osinfo
storage storage read list_storage
tasks tasks read list_tasks
cluster cluster read cluster_status, cluster_resources
snapshots snapshots read/write list_snapshots, create/rollback/delete_snapshot
lifecycle lifecycle write start/shutdown/stop/reboot/suspend/resume_guest
management management write migrate/clone/backup/delete_guest, set_guest_resources
backups backups read/write list_backups, restore_backup
provisioning provisioning read/write list_templates, create_container, create_vm 
PROXMOX_MCP_PLUGINS=                                # (env) empty = load all
PROXMOX_MCP_DISABLED_PLUGINS=lifecycle,snapshots    # insight only

Ask the assistant “list the plugins” any time to see what's enabled.

🗂️ Project structure

proxmox-mcp-server/
├── assets/soyrage-banner.svg  # SoyRage Agency identity banner
├── examples/                  # Claude config + config-file examples
├── install.sh / install.ps1   # One-command bootstrap for beginners
├── scripts/install.mjs        # Cross-platform Claude Desktop configurator
├── src/
│   ├── index.ts               # Entry point: banner, attribution guard, wiring
│   ├── branding.ts            # SoyRage identity, ASCII banner, MCP instructions
│   ├── plugins.ts             # Modular plugin catalogue & loader
│   ├── config.ts              # Layered config (defaults → file → .env → env)
│   ├── logger.ts              # stderr-only structured logger
│   ├── proxmox/
│   │   └── client.ts          # Typed Proxmox VE API client (token/ticket, TLS)
│   ├── tools/                 # One module per plugin's tools
│   │   ├── context.ts · about.ts · nodes.ts · guests.ts · cluster.ts
│   │   ├── storage.ts · tasks.ts · snapshots.ts · lifecycle.ts
│   └── utils/                 # format.ts (tables/units) · result.ts (MCP helpers)
├── .env.example · LICENSE · NOTICE · README.md

🧪 Development

npm run dev        # hot-reload with tsx
npm run typecheck  # strict type check, no emit
npm run build      # compile to dist/
npm run start      # run the built server
npm run inspect    # launch the MCP Inspector
npm run setup      # build + configure Claude Desktop

Design notes: stdout is reserved for the JSON‑RPC stream (logs → stderr); the Proxmox client resolves guest → node automatically; failing tool calls return a clean isError result instead of crashing the connection; TLS control is per‑request via undici.

🩺 Troubleshooting & FAQ

<details><summary><b>“Could not reach the Proxmox API.”</b></summary>

Check PROXMOX_HOST (include https:// and :8006), that the node is reachable (VPN?), and your token/credentials. With a self‑signed cert keep PROXMOX_VERIFY_TLS=false. The server keeps running so tool calls return a friendly error in your chat client. </details>

<details><summary><b>401 / permission denied.</b></summary>

The token/user lacks privileges for that path. Assign an appropriate role (PVEAuditor for read, PVEAdmin/PVEVMAdmin for control) at path / or on the specific VM, and make sure the token isn't limited by Privilege Separation without an ACL. </details>

<details><summary><b>The assistant can't see start/stop tools.</b></summary>

You're in read‑only mode (PROXMOX_MCP_READONLY=true) or the lifecycle plugin is disabled. Adjust and restart your MCP client. </details>

<details><summary><b>Is my data sent anywhere?</b></summary>

No. The server talks only to your Proxmox API and your MCP client over local stdio. It makes no other outbound calls. </details>

🗺️ Roadmap

  • [x] Nodes, guests, lifecycle, snapshots, storage, tasks, cluster
  • [x] Guest OS detection (QEMU agent) · suspend/resume
  • [x] Migrate, clone, resize, backup (vzdump), delete guests
  • [x] Backups: list & restore archives · Provisioning: create VMs/CTs from templates & ISOs
  • [x] Guided setup wizard · API‑token & ticket auth · read‑only & allowlist · modular plugins
  • [x] One‑command installer · demo mode · terminal UI (TUI) · CI
  • [ ] Scheduled backup jobs & backup pruning
  • [ ] Cloud‑init provisioning presets
  • [ ] Published npm package for one‑line npx usage

💙 Support the project

Proxmox MCP Server is built and maintained in the open by SoyRage Agency. If it's useful, please consider supporting continued development — it funds new features and keeps the project free.

<div align="center">

Support on PayPal

paypal.me/soyrageagency · a ⭐ on the repo also helps a lot!

</div>

Other ways to help: share it on r/selfhosted or r/Proxmox, report issues, open PRs, or hire SoyRage Agency for custom DevOps + AI tooling.

🖋️ Credits & License

<div align="center">

Designed, built and maintained by SoyRage Agency — https://soyrage.es/

</div>

Released under the SoyRage Attribution License (see LICENSE and NOTICE). You may use, modify and self‑host it — as long as the credit to SoyRage Agency stays visible: the source headers, the package.json author field, and the runtime identity (ASCII banner, about tool, MCP instructions) must remain intact.

ℹ️ On attribution: software that runs on your machine can always be modified — this is not DRM. The attribution is the default everywhere so removing it is a deliberate act, and the license makes that act a violation. For white‑labelling or a commercial license, reach out via soyrage.es.

<div align="center">

© 2026 SoyRage Agency — https://soyrage.es/ · Made with care in Valencia, Spain.

</div>

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议，是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器，它使大型语言模型能够通过结构化的可访问性快照与网页进行交互，而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具，可以从自然语言描述生成现代化的用户界面组件，并与流行的集成开发环境（IDE）集成，从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互，从而促进营销洞察和受众数据的提取和分析，包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具，连接你所有喜爱的工具：Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外，还可以将任何内容（从 Slack 到 Gmail 再到播客订阅源）导入到 Graphlit 项目中，然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器，集成了 Kagi 搜索功能和 Claude AI，使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议（MCP）服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选