ZCF - Nbility AI 网关

ZCF is an enhancement tool for Claude Code and Codex. Its goal is to consolidate initial API setup, workflow templates, and MCP service integration into one command as much as possible.

If you do not have an active Nbility account and token yet, complete the Beginner's Guide first, then continue with this configuration.

What ZCF Can Do

Common uses include:

Quickly writing API provider configuration
Installing common development workflows
Connecting MCP services
Unifying language, templates, and output style

For users who want less manual configuration, this approach is more convenient.

Common Initialization Options

API Options

Option	Purpose
`-p custom`	Use a custom provider, commonly used for Nbility
`-t api_key`	Equivalent to the above method; use API Key auth
`-k "sk-xxx"`	Pass your token
`-u "https://api.nbility.dev/"`	Set the Nbility base URL
`-M "claude-sonnet-4-5-20250929"`	Set the main model
`-H "claude-haiku-4-5-20251001"`	Set the fast model

Example:

npx zcf i -s -t api_key -k "sk-xxx" -u "https://api.nbility.dev/" \
  -M "claude-sonnet-4-5-20250929" \
  -H "claude-haiku-4-5-20251001"

Workflow Options

Option	Purpose
`-w all`	Install all workflows
`-w sixStepsWorkflow,gitWorkflow`	Install only selected workflows
`-w skip`	Do not install workflows

Typical options include commonTools, sixStepsWorkflow, featPlanUx, gitWorkflow, and bmadWorkflow.

MCP Service Options

Option	Purpose
`-m all`	Install all MCP services
`-m context7,open-websearch`	Install selected services only
`-m skip`	Skip MCP configuration

Available services include context7, open-websearch, spec-workflow, mcp-deepwiki, Playwright, exa, and serena.

Other Common Options

Option	Purpose
`-g zh-CN`	Use Chinese UI and Chinese output
`-s`	Disable interactive prompts; useful for scripts
`-r backup`	Decide how existing configuration is handled
`-x false`	Do not install extra status bar capability

Typical Command

For a quick initialization, start with:

npx zcf i -s -t api_key -k "sk-xxx" -u "https://api.nbility.dev/" -g zh-CN

Replace sk-xxx with the real token you got from /console/token.

Available Workflow Commands

After installation, these slash commands are usually available in Claude Code:

Command	Purpose
`/zcf:workflow`	Six-stage development workflow
`/zcf:feat`	Plan and implement new features
`/zcf:git-commit`	Generate commit messages
`/zcf:git-rollback`	Roll back history
`/zcf:git-worktree`	Manage worktrees
`/zcf:bmad-init`	Start a more complete agile workflow

MCP Service Overview

MCP lets coding tools connect to external docs, search, and automation capabilities. ZCF includes these services:

Service	Description	Requires extra key
`context7`	Query latest library docs and examples	No
`open-websearch`	Perform web search	No
`spec-workflow`	Organize work as requirements, design, and implementation	No
`mcp-deepwiki`	View GitHub repository information	No
`Playwright`	Browser automation and screenshots	No
`exa`	Semantic search	Yes
`serena`	IDE-like code search experience	No

Common uses:

context7: check latest API docs and avoid stale model suggestions
open-websearch: run web searches without connecting your own API
spec-workflow: break requirements and implementation into structured steps
Playwright: automate pages, fill forms, or capture screenshots

If you use exa, set this separately:

export EXA_API_KEY="your-api-key"

Configuration File Location

After installation, MCP configuration is usually written into ~/.claude/settings.json, with a structure like this:

{
  "mcpServers": {
    "context7": {
      "command": "npx",
      "args": ["-y", "@context-labs/context7"]
    },
    "open-websearch": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-open-websearch"]
    }
  }
}

Tip: If you encounter MCP path or connection issues on Windows, run npx zcf again and enter the MCP configuration options so the tool can repair them automatically.