Jewei Mcp Nacos

Created By
jeweis5 months ago
Nacos MCP Server - 让 AI 助手能够查询和管理 Nacos 配置。 支持 Nacos 1.x/2.x/3.x 版本。
Overview

what is Jewei Mcp Nacos?

Jewei Mcp Nacos is a server that allows AI assistants to query and manage Nacos configurations, supporting Nacos versions 1.x, 2.x, and 3.x.

how to use Jewei Mcp Nacos?

To use Jewei Mcp Nacos, you need to configure it in your project settings by adding specific JSON configurations to your .mcp.json, ~/.claude.json, or other relevant configuration files.

key features of Jewei Mcp Nacos?

  • Supports multiple Nacos versions (1.x, 2.x, 3.x)
  • Allows querying and managing configurations through AI assistants
  • Provides a simple setup process with environment variable configurations

use cases of Jewei Mcp Nacos?

  1. Querying configuration data from Nacos using natural language commands.
  2. Publishing and updating configurations in Nacos through AI interactions.
  3. Managing Nacos configurations in a read-only mode for production environments.

FAQ from Jewei Mcp Nacos?

  • What versions of Nacos does Jewei Mcp Nacos support?

It supports Nacos versions 1.x, 2.x, and 3.x.

  • Can I use Jewei Mcp Nacos in a production environment?

Yes, it can be configured to run in a read-only mode suitable for production use.

  • How do I set up the environment variables?

You can set up environment variables like NACOS_HOST, NACOS_API_PORT, and others in your configuration files.

Server Config

{
  "mcpServers": {
    "nacos": {
      "command": "uvx",
      "args": [
        "jewei-mcp-nacos"
      ],
      "env": {
        "NACOS_HOST": "localhost",
        "NACOS_API_PORT": "8848",
        "NACOS_CONSOLE_PORT": "8080",
        "NACOS_USERNAME": "nacos",
        "NACOS_PASSWORD": "your-password",
        "NACOS_NAMESPACE": "dev",
        "NACOS_VERSION": "3",
        "NACOS_READ_ONLY": "false"
      }
    }
  }
}
Project Info
Created At
5 months ago
Updated At
4 months ago
Author Name
jeweis
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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.

36 minutes ago