Dark-Alex-17/coyote
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

docs: Updated --install mcp_config from snake_case to kebab-case

Dark-Alex-17
2026-08-28 12:20:10 -06:00
parent d50c3ef611
commit f00cd88450
4 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Bundles.md
+5 -5
@@ -123,11 +123,11 @@ Restrict an install to a single asset category with `--filter`:
| `skills` | `skills/` only | | `skills` | `skills/` only |
| `macros` | `macros/` only | | `macros` | `macros/` only |
| `functions` | `functions/tools/` only (does **not** include `mcp.json`) | | `functions` | `functions/tools/` only (does **not** include `mcp.json`) |
| `mcp_config` | `mcp.json` only (merged) | | `mcp-config` | `mcp.json` only (merged) |
```sh ```sh
coyote --install <source> --filter agents coyote --install <source> --filter agents
coyote --install <source> --filter mcp_config coyote --install <source> --filter mcp-config
``` ```
REPL form: REPL form:
@@ -137,7 +137,7 @@ REPL form:
``` ```
Note that `--filter functions` is intentionally narrow. It installs the global tools under `functions/tools/` and Note that `--filter functions` is intentionally narrow. It installs the global tools under `functions/tools/` and
**not** `mcp.json`. To install just the MCP config, use `--filter mcp_config`. To install both, use no filter. **not** `mcp.json`. To install just the MCP config, use `--filter mcp-config`. To install both, use no filter.
Repeated filtered installs of the same bundle merge into a single bundle record, and a later Repeated filtered installs of the same bundle merge into a single bundle record, and a later
[update](#updating-a-bundle) always processes the whole remote, including categories a filtered install excluded. [update](#updating-a-bundle) always processes the whole remote, including categories a filtered install excluded.
@@ -213,7 +213,7 @@ How names are kept unambiguous:
first (a fork or typo-squat is the likely cause); declining aborts before anything is written, and non-interactive first (a fork or typo-squat is the likely cause); declining aborts before anything is written, and non-interactive
installs keep the deterministic qualification. Lifecycle commands accept the qualified name. installs keep the deterministic qualification. Lifecycle commands accept the qualified name.
- **Category names are reserved.** A bundle cannot be named `agents`, `roles`, `skills`, `macros`, `functions`, or - **Category names are reserved.** A bundle cannot be named `agents`, `roles`, `skills`, `macros`, `functions`, or
`mcp_config`. A repository or manifest that wants one of those names is owner-qualified at install time (e.g. `mcp-config`. A repository or manifest that wants one of those names is owner-qualified at install time (e.g.
`x/agents`), so a bundle can never shadow an asset category. `x/agents`), so a bundle can never shadow an asset category.
--- ---
@@ -524,7 +524,7 @@ coyote --install https://github.com/your-org/coyote-config --filter agents
### Install only the MCP servers, force-replace conflicts ### Install only the MCP servers, force-replace conflicts
```sh ```sh
coyote --install https://github.com/your-org/coyote-config --filter mcp_config --install-force coyote --install https://github.com/your-org/coyote-config --filter mcp-config --install-force
``` ```
### See what you have installed, then update one bundle ### See what you have installed, then update one bundle
MCP-Servers.md
+1 -1
@@ -550,7 +550,7 @@ Coyote ships with an `mcp.json` file that includes some useful MCP servers:
and requires the `iwec` binary. Pairs with the built-in `iwe-knowledge-base` [skill](Skills), which enables this server on load. and requires the `iwec` binary. Pairs with the built-in `iwe-knowledge-base` [skill](Skills), which enables this server on load.
The `mcp.json` file is created from a bundled template on first run. It is your own configuration to edit freely. The `mcp.json` file is created from a bundled template on first run. It is your own configuration to edit freely.
To pick up new default servers added in a Coyote update, run `coyote --install mcp_config` (or `.install mcp_config` To pick up new default servers added in a Coyote update, run `coyote --install mcp-config` (or `.install mcp-config`
in the REPL). This **merges** the bundled template into your existing configuration: only servers not already present in the REPL). This **merges** the bundled template into your existing configuration: only servers not already present
in your file are added; your existing servers and any custom secret references are left untouched. in your file are added; your existing servers and any custom secret references are left untouched.
REPL.md
+3 -3
@@ -474,7 +474,7 @@ when an update ships improved built-ins you want to adopt.
| `.install macros` | Reinstall the built-in macros | | `.install macros` | Reinstall the built-in macros |
| `.install skills` | Reinstall the built-in skills | | `.install skills` | Reinstall the built-in skills |
| `.install functions` | Reinstall the built-in tool functions (leaves your `mcp.json` alone) | | `.install functions` | Reinstall the built-in tool functions (leaves your `mcp.json` alone) |
| `.install mcp_config` | Merge new bundled MCP servers into `mcp.json` (existing servers are preserved) | | `.install mcp-config` | Merge new bundled MCP servers into `mcp.json` (existing servers are preserved) |
The same operation is available from the command line: `coyote --install-builtins <category>` (e.g. The same operation is available from the command line: `coyote --install-builtins <category>` (e.g.
`coyote --install-builtins agents`). `coyote --install-builtins agents`).
@@ -482,7 +482,7 @@ The same operation is available from the command line: `coyote --install-builtin
`.install` prompts for confirmation before overwriting anything. Assets you created yourself are never touched. Only `.install` prompts for confirmation before overwriting anything. Assets you created yourself are never touched. Only
Coyote's own bundled assets are replaced. Coyote's own bundled assets are replaced.
`.install mcp_config` merges the bundled MCP server list into your existing `mcp.json`. Only servers not already `.install mcp-config` merges the bundled MCP server list into your existing `mcp.json`. Only servers not already
present in your file are added; your existing servers and any custom secret references are left untouched. This present in your file are added; your existing servers and any custom secret references are left untouched. This
behaves consistently with the other install categories, which also leave your own customizations alone. behaves consistently with the other install categories, which also leave your own customizations alone.
@@ -499,7 +499,7 @@ This is the primary mechanism for sharing and reusing Coyote configurations; an
| `.install <owner>/<repo>` | Shorthand; expands to `https://github.com/<owner>/<repo>` | | `.install <owner>/<repo>` | Shorthand; expands to `https://github.com/<owner>/<repo>` |
| `.install <owner>/<repo> --git-host <h>` | Expand the shorthand against a different git host | | `.install <owner>/<repo> --git-host <h>` | Expand the shorthand against a different git host |
| `.install <source>#<ref>` | Pin to a tag, branch, or commit (e.g. `#v1.0.0`, `#main`) | | `.install <source>#<ref>` | Pin to a tag, branch, or commit (e.g. `#v1.0.0`, `#main`) |
| `.install <source> --filter <category>` | Restrict to one of `agents`, `roles`, `skills`, `macros`, `functions`, `mcp_config` | | `.install <source> --filter <category>` | Restrict to one of `agents`, `roles`, `skills`, `macros`, `functions`, `mcp-config` |
| `.install <source> --force` | Skip all conflict prompts; overwrite local files unconditionally | | `.install <source> --force` | Skip all conflict prompts; overwrite local files unconditionally |
| `.install <bundle-name>` | Update an installed bundle from its recorded source | | `.install <bundle-name>` | Update an installed bundle from its recorded source |
Tools.md
+1 -1
@@ -51,7 +51,7 @@ Details on what configuration, if any, is necessary for each tool can be found i
Built-in tools are written to your functions directory on first run and never overwritten afterward, so your edits are Built-in tools are written to your functions directory on first run and never overwritten afterward, so your edits are
preserved across Coyote updates. To discard local changes and reinstall the built-in tools from the current Coyote build, preserved across Coyote updates. To discard local changes and reinstall the built-in tools from the current Coyote build,
run `coyote --install functions` (or `.install functions` in the REPL). Tools you created yourself are not affected, and run `coyote --install functions` (or `.install functions` in the REPL). Tools you created yourself are not affected, and
your `mcp.json` is left untouched. Use `coyote --install mcp_config` to reset that separately. your `mcp.json` is left untouched. Use `coyote --install mcp-config` to reset that separately.
## Sandbox Compatibility ## Sandbox Compatibility