Ziti MCP Server

MCP安全风控

提供方 openziti

安全风控 未标注 无需鉴权 社区 / 第三方

Manage OpenZiti zero-trust networks — through natural language

一句话选型结论

按资料字段整理

Ziti MCP Server 属于安全风控类 MCP 服务器,传输方式未标注,无需鉴权,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类安全风控 传输方式未标注 鉴权无需鉴权 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

安全风控
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

安装与配置

未标注 无需鉴权
上游未给出传输方式
  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
资产与漏洞排查

盘点资产、扫漏洞、看暴露面。

日志与审计

汇总日志、查异常行为。

合规检查

按规则检查配置与权限是否合规。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在安全风控场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Ziti MCP Server当前 未标注 未标注 本地部署 无 2026-05-17
Cyber Strike AI 75 未标注 未标注 无 2026-05-17
mcp-for-beginners 未标注 stdio · 本地进程 本地部署 有 2026-04-13
casdoor 未标注 stdio · 本地进程 本地部署 有 2026-04-12
kubeshark 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Modelcontextprotocol C22988b0 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

安全风控
字段来自项目仓库与公开索引,中文说明由本站标注
提供方openziti上游标注的维护方 openziti
分类安全风控本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

16.7 KB
来自项目仓库与上游目录的原文,未做删改

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:

  • Claude Desktop or any other MCP Client
  • OpenZiti network
  • Go 1.24+ (only if building from source)

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 xz
sudo 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 xz
sudo 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 xz
sudo 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 xz
sudo 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 client
ziti-mcp-server install --client claude-code
ziti-mcp-server install --client cursor
ziti-mcp-server install --client windsurf
ziti-mcp-server install --client vscode
ziti-mcp-server install --client warp

# Register with read-only tools only
ziti-mcp-server install --read-only

# Register with specific tool patterns
ziti-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 ''` 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:

&gt; [!NOTE]
&gt; 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 &lt;your-controller-host&gt; \
  --idp-domain &lt;your-idp-domain&gt; \
  --idp-client-id &lt;your-client-id&gt; \
  --idp-client-secret &lt;your-client-secret&gt;

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).

&gt; [!IMPORTANT]
&gt;
&gt; When using CLI `init`, it needs to be run whenever:
&gt;
&gt; - You&#x27;re setting up the MCP Server for the first time
&gt; - You&#x27;ve logged out from a previous session
&gt; - You want to switch to a different Ziti network
&gt; - Your token has expired
&gt;
&gt; 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 profiles
ziti-mcp-server init --auth-mode updb --profile prod ...
ziti-mcp-server init --auth-mode updb --profile staging ...

# Start with a specific profile active
ziti-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 session
ziti-mcp-server session --profile prod


### Logging Out```bash
ziti-mcp-server logout
ziti-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.

Tool Description
loginUpdb Connect using username/password authentication
loginIdentity Connect using a Ziti identity JSON (mTLS certificate)
loginClientCredentials Connect using OAuth2 client credentials
loginDeviceAuth Start OAuth2 device auth flow (returns verification URL)
completeLogin Complete a pending device-auth login after browser approval
logout Disconnect from a Ziti network (clear profile credentials)
listNetworks List all configured network profiles with connection status
selectNetwork Switch the active network profile

Tool Categories

Category Tools Description
Identities 22 CRUD, relationships, lifecycle, posture, tracing
Services 12 CRUD and relationship queries
Edge Routers 11 CRUD, relationships, re-enrollment
Edge Router Policies 7 CRUD and relationship queries
Service Edge Router Policies 7 CRUD and relationship queries
Service Policies 8 CRUD and relationships (Dial/Bind)
Configs 6 CRUD and service relationships
Config Types 6 CRUD and config queries
Auth Policies 5 CRUD (primary/secondary auth settings)
Authenticators 5 CRUD (updb/cert)
Certificate Authorities 7 CRUD, JWT retrieval, verification
External JWT Signers 5 CRUD for external JWT signers
Posture Checks 8 CRUD, types, and role attributes
Routers 5 CRUD for fabric routers
Transit Routers 5 CRUD for transit routers
Terminators 5 CRUD for terminators
Enrollments 5 CRUD and refresh
Controller Settings 6 CRUD and effective value queries
Controllers & System Info 4 Version, capabilities, summary
Sessions & API Sessions 6 List, detail, delete
Identity Types 2 List and detail
Fabric (Routers, Services, …) 34 Fabric-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 &#x27;demo-admin&#x27; 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 &#x27;my-api&#x27; service

🔒 Security

Restricting Tool Access

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

Enable only read-only operations

ziti-mcp-server run --read-only

Alternative way to enable only read-only operations

ziti-mcp-server run --tools 'list,get'

Limit to just identity-related tools

ziti-mcp-server run --tools 'Identit'

Limit to read-only identity-related tools

ziti-mcp-server run --tools 'Identit' --read-only

Run the server with all tools enabled

ziti-mcp-server run --tools '*'


&gt; [!IMPORTANT]
&gt; 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

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

&gt; [!CAUTION]
&gt; 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 ...
    - 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-time
tail -n 20 -F ~/Library/Logs/Claude/mcp*.log

👨‍💻 Development

Building from Source```bash

Clone the repository

git clone https://github.com/openziti/ziti-mcp-server.git
cd ziti-mcp-server-go

Build

go 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

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Ziti MCP Server 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Ziti MCP Server 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Ziti MCP Server 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Ziti MCP Server 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Ziti MCP Server 能提供哪些能力?

资料显示能力标签包括 安全、开发工具、数据分析。具体工具清单以官方文档为准。

Ziti MCP Server 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

Ziti MCP Server 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。