skills & mcp
Install Agent Skills from GitHub or a registry, and run BitRouter's origin MCP server.
skills installs and manages Agent Skills for your harness; mcp runs BitRouter's own MCP server — the tool surface any MCP client can drive instead of shelling out. What the server exposes (backends, transports, the gateway distinction) lives on the MCP Server page.
bitrouter skills
Install and manage Claude Code skills from GitHub, a git URL, or a BitRouter registry
Usage: bitrouter skills [OPTIONS] <COMMAND>
Options
| Flag | Description |
|---|---|
-j, --json | Force JSON output (the default; agent-native). Conflicts with --human |
--human | Render the human-readable view to stdout instead of JSON |
bitrouter skills add
Install a skill from a source (GitHub owner/repo, a git URL, or a registry skill name)
Usage: bitrouter skills add [OPTIONS] <SOURCE>
Arguments
| Argument | Description |
|---|---|
<SOURCE> | Source: owner/repo, a full git URL, or a registry skill name |
Options
| Flag | Description |
|---|---|
-j, --json | Force JSON output (the default; agent-native). Conflicts with --human |
--skill <NAME> | When the source exposes several skills, install the one with this frontmatter name |
-g, --global | Install into ~/.claude/skills/ instead of ./.claude/skills/ |
--human | Render the human-readable view to stdout instead of JSON |
-y, --yes | Overwrite an existing install of the same skill |
--registry <URL> | Registry base URL used when source is a bare skill name |
-n, --namespace <NSID> | Namespace id whose registry hub to query (required for registry operations) |
bitrouter skills add bitrouter # the /bitrouter skill, from the registry
bitrouter skills add owner/repo # from GitHubbitrouter skills list
List installed skills
Usage: bitrouter skills list [OPTIONS]
Options
| Flag | Description |
|---|---|
-g, --global | Operate on the global skills directory (~/.claude/skills/) |
-j, --json | Force JSON output (the default; agent-native). Conflicts with --human |
--human | Render the human-readable view to stdout instead of JSON |
bitrouter skills remove
Remove an installed skill by name
Usage: bitrouter skills remove [OPTIONS] <NAME>
Arguments
| Argument | Description |
|---|---|
<NAME> | The skill name to remove |
Options
| Flag | Description |
|---|---|
-g, --global | Remove from the global skills directory |
-j, --json | Force JSON output (the default; agent-native). Conflicts with --human |
--human | Render the human-readable view to stdout instead of JSON |
bitrouter skills find
Search the configured registry for skills
Usage: bitrouter skills find [OPTIONS] <QUERY>
Arguments
| Argument | Description |
|---|---|
<QUERY> | Query matched against name, description, and tags |
Options
| Flag | Description |
|---|---|
-j, --json | Force JSON output (the default; agent-native). Conflicts with --human |
--registry <URL> | Registry base URL to search |
--human | Render the human-readable view to stdout instead of JSON |
-n, --namespace <NSID> | Namespace id whose registry hub to query (required for registry operations) |
bitrouter skills init
Scaffold a new SKILL.md in the current directory
Usage: bitrouter skills init [OPTIONS] <NAME>
Arguments
| Argument | Description |
|---|---|
<NAME> | Skill name written into the generated frontmatter |
Options
| Flag | Description |
|---|---|
-j, --json | Force JSON output (the default; agent-native). Conflicts with --human |
-o, --output <OUTPUT> | Output path for the SKILL.md [default: SKILL.md] |
--human | Render the human-readable view to stdout instead of JSON |
bitrouter skills update
Re-install installed skills from the registry to their latest version
Usage: bitrouter skills update [OPTIONS] [NAME]
Arguments
| Argument | Description |
|---|---|
[NAME] | Update only this skill. When omitted, updates every installed skill found in the registry |
Options
| Flag | Description |
|---|---|
-g, --global | Update the global skills directory |
-j, --json | Force JSON output (the default; agent-native). Conflicts with --human |
--human | Render the human-readable view to stdout instead of JSON |
--registry <URL> | Registry base URL to update from |
-n, --namespace <NSID> | Namespace id whose registry hub to query (required for registry operations) |
bitrouter mcp
Run or install BitRouter's origin MCP server
Usage: bitrouter mcp [OPTIONS] <COMMAND>
Options
| Flag | Description |
|---|---|
-j, --json | Force JSON output (the default; agent-native). Conflicts with --human |
--human | Render the human-readable view to stdout instead of JSON |
bitrouter mcp serve
Serve the MCP server (stdio by default)
Usage: bitrouter mcp serve [OPTIONS]
Options
| Flag | Description |
|---|---|
-j, --json | Force JSON output (the default; agent-native). Conflicts with --human |
--transport <TRANSPORT> | stdio (local daemon) or http (cloud) Possible values: |
- stdio: Newline-delimited JSON-RPC over stdio (local clients launch this) | |
- http: | Streamable HTTP, mounted at /mcp-control [default: stdio] |
--backend <BACKEND> | local or cloud. Defaults: stdio→local, http→cloud Possible values: |
- local: The local BYOK daemon at 127.0.0.1:4356`` | |
- cloud: BitRouter Cloud at api.bitrouter.ai`` | |
--human | Render the human-readable view to stdout instead of JSON |
--local-url <LOCAL_URL> | Local daemon root [default: http://127.0.0.1:4356] |
--cloud-url <CLOUD_URL> | Cloud root [default: https://api.bitrouter.ai] |
--token <TOKEN> | Cloud bearer token (else BITROUTER_TOKEN) |
--bind <BIND> | HTTP bind address [default: 127.0.0.1:4357] |
bitrouter mcp serve # stdio → local daemon at 127.0.0.1:4356
bitrouter mcp serve --backend skills # the AgentSkills gateway as a standalone server
bitrouter mcp install --client claude # print the mcpServers config block to pastebitrouter mcp install
Write/print the client config block
Usage: bitrouter mcp install [OPTIONS]
Options
| Flag | Description |
|---|---|
--client <CLIENT> | claude or cursor [default: claude] [possible values: claude, cursor] |
-j, --json | Force JSON output (the default; agent-native). Conflicts with --human |
--config <CONFIG> | Config file to merge into; omit to print to stdout |
--human | Render the human-readable view to stdout instead of JSON |
How is this guide?