OpenZiti Network Management

io.github.openziti由 GitHub 账号 openziti 发布v0.11.0更新于 Oct 24, 2026

Manage OpenZiti zero-trust networks — through natural language

概览

AI 生成的概览

一个本地 MCP 服务器,让 AI 助手用自然语言管理 OpenZiti 零信任网络,从查看身份到创建策略。

可以做什么
登录、登出、列出并切换 Ziti 网络配置,并在运行时完成设备授权登录;这些元工具始终可用,即使其他工具被过滤。管理身份、服务、配置与配置类型、认证策略、认证器、证书颁发机构、外部 JWT 签名者、态势检查与注册。管理边缘路由器、路由器、中转路由器、终结器、边缘路由器策略、服务边缘路由器策略与服务策略,包括拨号与绑定关系。查看和修改控制器设置、控制器与系统信息、会话与 API 会话以及身份类型。操作 fabric 层,包括增删改查、电路、链路、集群与数据库快照。
适用场景
当你管理一个或多个 OpenZiti 网络,希望助手回答关于身份、服务、路由器和策略的问题,或执行创建身份、创建绑定策略等日常管理任务时使用。既适合交互式探索,也适合预先配置好配置文件的自动化场景。
运行要求
以本地进程形式在用户机器上运行;提供 macOS、Linux 和 Windows 的预编译二进制,也可用 Go 1.24+ 从源码构建。需要 Claude Desktop 等 MCP 客户端,以及带控制器的 OpenZiti 网络。必须认证:UPDB 用户名和密码、设备授权、OAuth2 客户端凭据,或用于 mTLS 的 Ziti 身份 JSON 文件。凭据保存在用户主目录下的配置文件中。
安装前请注意
该服务器可以创建、修改和删除网络资源,包括身份、策略、路由器和会话;可用只读标志或工具模式限制暴露范围。密码、客户端密钥和证书材料等凭据保存在本地配置文件中,使用完毕后应登出。身份文件中的证书材料会被复制到该配置文件。请审阅认证过程中请求的权限。

安装

在 SourceWeft 中

  1. 打开 控制台中的 OpenZiti Network Management,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

[OpenZiti MCP Server Banner]

🚀 Getting Started • 🕸️ Architecture • 🔐 Authentication • 🛠️ Supported Tools • 🔒 Security • 🩺 Troubleshooting • 📋 Debug Logs • 👨‍💻 Development

The Ziti MCP Server is sponsored by NetFoundry as part of its portfolio of solutions for secure workloads and agentic computing. NetFoundry is the creator of OpenZiti and zrok.

MCP (Model Context Protocol) is an open protocol introduced by Anthropic that standardizes how large language models communicate with external tools, resources or remote services.

The Ziti MCP Server integrates with LLMs and AI agents, allowing you to perform various Ziti network management operations using natural language. For instance, you could simply ask Claude Desktop to perform Ziti management operations:

  • List which identities exist

  • Tell me if there are any exposures in the network

  • Do you see potential misconfigurations?

  • Which identities have access to the Demo1 service?

  • Create a new Ziti identity named "Demo" and get its ID

  • Log into my prod Ziti network using UPDB

  • Switch to the staging network

  • etc.


🚀 Getting Started

Prerequisites:


Install

Download a pre-built binary

Pre-built binaries are available for macOS, Linux, and Windows (amd64 and arm64) on the releases page.

macOS (Apple Silicon)

bash
curl -sL https://github.com/openziti/ziti-mcp-server/releases/latest/download/ziti-mcp-server_darwin_arm64.tar.gz | tar xzsudo mv ziti-mcp-server /usr/local/bin/

macOS (Intel)

bash
curl -sL https://github.com/openziti/ziti-mcp-server/releases/latest/download/ziti-mcp-server_darwin_amd64.tar.gz | tar xzsudo mv ziti-mcp-server /usr/local/bin/

Linux (amd64)

bash
curl -sL https://github.com/openziti/ziti-mcp-server/releases/latest/download/ziti-mcp-server_linux_amd64.tar.gz | tar xzsudo mv ziti-mcp-server /usr/local/bin/

Linux (arm64)

bash
curl -sL https://github.com/openziti/ziti-mcp-server/releases/latest/download/ziti-mcp-server_linux_arm64.tar.gz | tar xzsudo mv ziti-mcp-server /usr/local/bin/

Windows

Download the appropriate .zip from the releases page and add the extracted ziti-mcp-server.exe to your PATH.

Build from source
bash
go install github.com/openziti/ziti-mcp-server/cmd/ziti-mcp-server@latest

Register with your AI Client

Use install to register the Ziti MCP Server with your AI client. This only updates the client's configuration file — it does not authenticate. Use the runtime login tools or init for that.

bash
# Register with Claude Desktop (default)ziti-mcp-server install
# Register with a specific clientziti-mcp-server install --client claude-codeziti-mcp-server install --client cursorziti-mcp-server install --client windsurfziti-mcp-server install --client vscodeziti-mcp-server install --client warp
# Register with read-only tools onlyziti-mcp-server install --read-only
# Register with specific tool patternsziti-mcp-server install --tools '*Identit*,list*'

After installing, restart your AI client and use the runtime login tools to authenticate (e.g., ask: "Log into my Ziti network at ctrl.example.com with username admin").

Start and Log In

The server can start with no prior configuration. The AI agent can log into networks at runtime using the built-in login tools:

bash
ziti-mcp-server run

Then in your AI client, simply ask:

Log into my Ziti network at 192.168.1.100:1280 with username admin and password admin

For non-interactive or automated setups, use init to pre-configure credentials before starting:

bash
ziti-mcp-server init \  --auth-mode updb \  --ziti-controller-host <your-controller-host> \  --username <username> \  --password <password> \  --profile prod

See Authentication for all supported modes (UPDB, device auth, client credentials, identity file).

Manual Client Configuration

The install command handles client configuration automatically. If you need to configure an MCP client manually, add this to its configuration and restart:

json
{  "mcpServers": {    "ziti": {      "command": "/path/to/ziti-mcp-server",      "args": ["run"],      "capabilities": ["tools"],      "env": {        "OPENZITI_MCP_DEBUG": "true"      }    }  }}

You can add --tools '<pattern>' and/or --read-only to the args array to control which tools are available. See Restricting Tool Access.

Verify your integration

Restart your MCP Client (Claude Desktop, Windsurf, Cursor, Warp, etc.) and ask it to help you manage your Ziti network.

🕸️ Architecture

The Ziti MCP Server implements the Model Context Protocol, allowing clients (like Claude) to:

  1. Request a list of available Ziti tools
  2. Call specific tools with parameters
  3. Receive structured responses from the Ziti Management API

The server handles authentication, request validation, and secure communication with the Ziti Management API.

[!NOTE] The server operates as a local process that connects to Claude Desktop, enabling secure communication without exposing your Ziti credentials.

🔐 Authentication

The Ziti MCP Server uses the Ziti Management API and requires authentication to access your Ziti network.

Authentication Modes

The server supports four authentication modes:

UPDB Mode (Username/Password)

Use this mode for direct username/password authentication against the Ziti controller:

bash
ziti-mcp-server init \  --auth-mode updb \  --ziti-controller-host <your-controller-host> \  --username <username> \  --password <password>

Or at runtime via the AI agent using the loginUpdb tool.

Device Auth Mode (Interactive Login)

Use this mode for interactive browser-based login. Recommended for development and user-facing scenarios:

bash
ziti-mcp-server init \  --auth-mode device-auth \  --ziti-controller-host <your-controller-host> \  --idp-domain <your-idp-domain> \  --idp-client-id <your-client-id> \  --idp-audience <your-audience>

Or at runtime via the loginDeviceAuth tool (returns a verification URL for the user, then completeLogin to finish).

Client Credentials Mode (Service Account)

Use this mode for service accounts and automation. Recommended for production environments:

[!NOTE] Keep the token lifetime as minimal as possible to reduce security risks. See more

bash
ziti-mcp-server init \  --auth-mode client-credentials \  --ziti-controller-host <your-controller-host> \  --idp-domain <your-idp-domain> \  --idp-client-id <your-client-id> \  --idp-client-secret <your-client-secret>
Identity File Mode (mTLS Certificate)

Use this mode for certificate-based authentication with a Ziti identity JSON file. No IdP configuration is needed:

bash
ziti-mcp-server init \  --auth-mode identity \  --identity-file <path-to-identity.json>

The identity file is a standard Ziti identity JSON file containing ztAPI, id.cert, id.key, and id.ca fields. The certificate material is extracted and stored in the config file. The identity file may be deleted after a successful init (for additional security, if desired).

[!IMPORTANT]

When using CLI init, it needs to be run whenever:

  • You're setting up the MCP Server for the first time
  • You've logged out from a previous session
  • You want to switch to a different Ziti network
  • Your token has expired

Alternatively, use the runtime login tools (loginUpdb, etc.) to authenticate without restarting the server.

Multi-Profile Support

The server supports multiple named network profiles, allowing you to manage several Ziti networks simultaneously:

bash
# Pre-configure two profilesziti-mcp-server init --auth-mode updb --profile prod ...ziti-mcp-server init --auth-mode updb --profile staging ...
# Start with a specific profile activeziti-mcp-server run --profile prod

At runtime, the AI agent can:

  • Log into additional networks using loginUpdb, loginIdentity, etc.
  • List all networks using listNetworks
  • Switch between networks using selectNetwork
  • Log out from a network using logout

Credentials are stored in ~/.config/ziti-mcp-server/config.json with 0600 permissions.

Session Management

To see information about your current authentication session:

bash
ziti-mcp-server sessionziti-mcp-server session --profile prod

Logging Out

bash
ziti-mcp-server logoutziti-mcp-server logout --profile prod

Or at runtime via the AI agent using the logout tool.

🛠️ Supported MCP Tools

The Ziti MCP Server provides 201 Ziti API tools plus 8 meta-tools for managing your Ziti network through natural language. Tools are organized by resource type.

Tip: Use --read-only or --tools patterns to expose only the tools you need. See Restricting Tool Access.

Meta-Tools (Network Management)

These tools are always available regardless of --tools or --read-only filtering.

ToolDescription
loginUpdbConnect using username/password authentication
loginIdentityConnect using a Ziti identity JSON (mTLS certificate)
loginClientCredentialsConnect using OAuth2 client credentials
loginDeviceAuthStart OAuth2 device auth flow (returns verification URL)
completeLoginComplete a pending device-auth login after browser approval
logoutDisconnect from a Ziti network (clear profile credentials)
listNetworksList all configured network profiles with connection status
selectNetworkSwitch the active network profile

Tool Categories

CategoryToolsDescription
Identities22CRUD, relationships, lifecycle, posture, tracing
Services12CRUD and relationship queries
Edge Routers11CRUD, relationships, re-enrollment
Edge Router Policies7CRUD and relationship queries
Service Edge Router Policies7CRUD and relationship queries
Service Policies8CRUD and relationships (Dial/Bind)
Configs6CRUD and service relationships
Config Types6CRUD and config queries
Auth Policies5CRUD (primary/secondary auth settings)
Authenticators5CRUD (updb/cert)
Certificate Authorities7CRUD, JWT retrieval, verification
External JWT Signers5CRUD for external JWT signers
Posture Checks8CRUD, types, and role attributes
Routers5CRUD for fabric routers
Transit Routers5CRUD for transit routers
Terminators5CRUD for terminators
Enrollments5CRUD and refresh
Controller Settings6CRUD and effective value queries
Controllers & System Info4Version, capabilities, summary
Sessions & API Sessions6List, detail, delete
Identity Types2List and detail
Fabric (Routers, Services, …)34Fabric-layer CRUD, circuits, links, cluster, DB snapshots

See docs/tools.md for the full tool reference with detailed tables and example prompts.

Example Prompts

  • Show me all Ziti identities
  • Which identities have access to the Demo1 service?
  • Create a new identity called 'demo-admin' and make it an admin
  • List all edge routers and their status
  • Show me all Dial service policies
  • What version is the Ziti controller running?
  • Give me a summary of the network — how many identities, services, and routers exist?
  • Create a Bind policy for the 'my-api' service

🔒 Security

Restricting Tool Access

When configuring the Ziti MCP Server, limit tool access based on your specific needs:

bash
# Enable only read-only operationsziti-mcp-server run --read-only
# Alternative way to enable only read-only operationsziti-mcp-server run --tools 'list*,get*'
# Limit to just identity-related toolsziti-mcp-server run --tools '*Identit*'
# Limit to read-only identity-related toolsziti-mcp-server run --tools '*Identit*' --read-only
# Run the server with all tools enabledziti-mcp-server run --tools '*'

[!IMPORTANT] When both --read-only and --tools flags are used together, the --read-only flag takes priority for security. Meta-tools (login, logout, listNetworks, selectNetwork) are always available regardless of filtering.

This approach offers several important benefits:

  1. Enhanced Security: Limiting available tools reduces the potential attack surface.
  2. Better Performance: Fewer tools means less context window usage for tool reasoning.
  3. Resource-Based Access Control: Configure different instances with different tool sets.
  4. Simplified Auditing: Easier to track which operations were performed.

Credential Storage

  • Credentials are stored in ~/.config/ziti-mcp-server/config.json with 0600 permissions
  • The config file is never world-readable
  • Authentication supports OAuth 2.0 device authorization, client credentials, mTLS certificates, and UPDB
  • Easy credential removal via logout command or tool

[!IMPORTANT] For security best practices, always log out when you're done with a session or switching between networks.

[!CAUTION] Always review the permissions requested during the authentication process to ensure they align with your security requirements.

Security Scanning

We recommend regularly scanning this server with community tools built to surface protocol-level risks:

  • mcpscan.ai — Web-based scanner for MCP endpoints
  • mcp-scan — CLI tool for evaluating server behavior

Reporting Issues

To provide feedback or report a bug, please raise an issue on our issue tracker.

🩺 Troubleshooting

Start troubleshooting by exploring all available commands and options:

bash
ziti-mcp-server help

🚨 Common Issues

  1. Authentication Failures

    • Ensure you have the correct permissions in your Ziti network
    • Try re-initializing with ziti-mcp-server init --auth-mode <mode> ...
    • Or use the runtime login tools to re-authenticate
  2. TLS Certificate Errors

    • The server auto-fetches the controller's CA on login via the EST /cacerts endpoint
    • If the CA fetch fails, add the controller CA to your system trust store
    • Or re-login to trigger a fresh CA fetch
  3. Client Can't Connect to the Server

    • Restart your MCP client after configuration changes
    • Check that the binary path in the client config is correct
  4. Invalid Configuration Error

    • This typically happens when no profile is active or credentials are missing
    • Use listNetworks to check profile status
    • Use a login tool or ziti-mcp-server init to authenticate

[!TIP] Most connection issues can be resolved by restarting both the server and your MCP client.

📋 Debug logs

Enable debug mode to view detailed logs:

sh
export OPENZITI_MCP_DEBUG=true

Get detailed MCP Client logs from Claude Desktop:

sh
# Follow logs in real-timetail -n 20 -F ~/Library/Logs/Claude/mcp*.log

👨‍💻 Development

Building from Source

bash
# Clone the repositorygit clone https://github.com/openziti/ziti-mcp-server.gitcd ziti-mcp-server-go
# Buildgo build ./cmd/ziti-mcp-server
# Run./ziti-mcp-server run

Regenerating API Clients

The Ziti API clients in internal/gen/ are generated from OpenAPI specs using go-swagger:

bash
make generate

来源:README.md,提交 9867ecd

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.11.0最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分