OpenDSS MCP 服务器

Created By
XJTU-RLa year ago
mcp server for LMC
Overview

what is LMC-mcp-server?

LMC-mcp-server is an OpenDSS server built using the Model Context Protocol (MCP) framework, enabling interaction between power system simulation tools and large language models (LLMs).

how to use LMC-mcp-server?

To use LMC-mcp-server, install it via pip or uv, and then start the server in development mode or install it for desktop use. You can interact with the server using Python to compile DSS files and execute commands.

key features of LMC-mcp-server?

  • Supports core functionalities of OpenDSS power system simulation.
  • Exposes OpenDSS functionalities and data through the MCP protocol.
  • Provides user-friendly resources, tools, and prompt templates for common power system analysis tasks.

use cases of LMC-mcp-server?

  1. Compiling and executing OpenDSS commands for power system analysis.
  2. Analyzing circuit information and power flow results.
  3. Integrating with LLMs for enhanced simulation capabilities.

FAQ from LMC-mcp-server?

  • What are the prerequisites for using LMC-mcp-server?

You need Python 3.10 or higher and an installation of OpenDSS.

  • How can I install LMC-mcp-server?

You can install it using uv install or pip install commands provided in the documentation.

  • Can I contribute to the project?

Yes! Contributions are welcome, and you can submit issues or code following the project's coding standards.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
XJTU-RL
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