MCP Servers

A collection of MCP (Model Context Protocol) servers, distributed via npm.

Servers

Server	Package	Description
aishell-mcp	@huaweidevtools/aishell-mcp	HuaweiCloud IaC — plan, apply, destroy, estimate cost, troubleshoot cloud deployments

Usage

aishell-mcp

Run directly without installing:

npx @huaweidevtools/aishell-mcp

Or install globally:

npm install -g @huaweidevtools/aishell-mcp
aishell-mcp

Transports

stdio (default) — for IDE / agent runtimes that spawn the server as a subprocess:

aishell-mcp

HTTP — for remote clients:

# Local only (default)
aishell-mcp --port 8080

# Expose to the network (use behind a firewall or tunnel)
aishell-mcp --port 8080 --host 0.0.0.0

Configuration

aishell-mcp reads configuration from environment variables:

Variable	Required	Description
HW_ACCESS_KEY	yes	HuaweiCloud AK (use a temporary AK with HW_SECURITY_TOKEN)
HW_SECRET_KEY	yes	HuaweiCloud SK (use a temporary SK with HW_SECURITY_TOKEN)
HW_REGION	recommended	HuaweiCloud region
HW_SECURITY_TOKEN	no	Temporary STS token; required when using temporary AK/SK

Example:

export HW_ACCESS_KEY=...
export HW_SECRET_KEY=...
export HW_REGION=cn-east-3
aishell-mcp --port 8080

Connect from an MCP client

stdio (e.g. in a client config):

{
  "mcpServers": {
    "aishell": {
      "command": "npx",
      "args": ["-y", "@huaweidevtools/aishell-mcp"],
      "env": {
        "HW_ACCESS_KEY": "...",
        "HW_SECRET_KEY": "...",
        "HW_REGION": "cn-east-3"
      }
    }
  }
}

Releases

Each version publishes a Release with platform binaries and a checksums.txt for manual (non-npm) download. The primary distribution channel is npm: npm install @huaweidevtools/aishell-mcp pulls the matching platform subpackage automatically.

Repository structure

mcp/
├── servers/
│   └── aishell-mcp/              # npm package (launcher + manifest)
│       ├── dist/cli.js           # launcher: resolves and spawns the binary
│       ├── platforms/            # per-platform binaries (one per os/arch)
│       │   ├── linux-x64/
│       │   ├── linux-arm64/
│       │   ├── darwin-x64/
│       │   ├── darwin-arm64/
│       │   ├── win32-x64/
│       │   └── win32-arm64/
│       └── package.json
└── package.json                  # workspace root

Local development

The launcher runs straight from source. Stage the platform binaries first (from dist-build/<version>/ into platforms/*/bin/), then run:

bash servers/aishell-mcp/scripts/stage-platform-bins.sh
node servers/aishell-mcp/dist/cli.js --port 8080

Or link it globally so aishell-mcp resolves to your working copy:

cd servers/aishell-mcp
npm link
aishell-mcp --port 8080

Both paths resolve the binary from the local platforms/ tree. To point an MCP client at your local checkout instead of the npm package, replace the npx command with the node invocation above.

License

MIT