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

docs: updated docs to mention support for enabled_mcp_servers to be either a YAML list or a CSV string

Alex Clarke
2026-06-03 13:23:09 -06:00
parent 9e1ad70b08
commit de0a051002
4 changed files with 18 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
MCP-Servers.md
+10 -4
@@ -170,11 +170,16 @@ The following settings are available in the global configuration for MCP servers
mcp_server_support: true # Enables or disables MCP server support (globally).
mapping_mcp_servers: # Alias for an MCP server or set of servers
git: github,gitmcp
enabled_mcp_servers: null # Which MCP servers to enable by default (e.g. 'github,slack')
enabled_mcp_servers: null # Which MCP servers to enable by default.
# Accepts either a YAML list or a comma-separated string. Examples:
# enabled_mcp_servers: github,slack
# enabled_mcp_servers:
# - github
# - slack
```
A special note about `enabled_mcp_servers`: a user can set this to `all` to enable all configured MCP servers in the
`functions/mcp.json` configuration.
A special note about `enabled_mcp_servers`: a user can set this to `all` (or include `all` in the list) to enable all
configured MCP servers in the `functions/mcp.json` configuration.
(See the [Configuration Example](https://github.com/Dark-Alex-17/coyote/blob/main/config.example.yaml) file for an example global configuration with all options.)
@@ -187,7 +192,8 @@ When running in REPL-mode, the `mcp_server_support` and `enabled_mcp_servers` se
When you create a role, you have the following MCP-related configuration options available to you:
```yaml
enabled_mcp_servers: github # Which MCP servers the role uses.
enabled_mcp_servers: # Which MCP servers the role uses. Accepts either a YAML list (as shown)
- github # or a comma-separated string (e.g. `enabled_mcp_servers: github,slack`).
```
The values for `mapping_mcp_servers` are inherited from the `[global configuration](#global-configuration)`.
REPL.md
+1 -1
@@ -218,7 +218,7 @@ The following settings can be adjusted at runtime:
| `temperature` | float | Model temperature parameter |
| `top_p` | float | Model top-p parameter |
| `enabled_tools` | string | Comma-separated list of enabled tools |
| `enabled_mcp_servers` | string | Comma-separated list of enabled MCP servers |
| `enabled_mcp_servers` | string | Comma-separated list of enabled MCP servers (e.g. `github,slack` or `all`); the saved YAML config also accepts a list form |
| `enabled_skills` | string | Comma-separated list of enabled [skills](Skills) (e.g. `git-master,ai-slop-remover`); `null` clears the override |
| `save_session` | boolean | Whether to auto-save sessions |
| `compression_threshold` | integer | Token threshold for session compression |
Roles.md
+1 -1
@@ -57,7 +57,7 @@ The following table lists the available configuration settings and their default
| `temperature` | Default `temperature` for the preferred model | Controls the creativity and randomness of the model's responses |
| `top_p` | Default `top_p` for the preferred model | Alternative way to control the model's output diversity, affecting the <br>probability distribution of tokens |
| `enabled_tools` | Global setting for `enabled_tools` | The tools that this role utilizes |
| `enabled_mcp_servers` | Global setting for `enabled_mcp_servers` | The MCP servers that this role utilizes |
| `enabled_mcp_servers` | Global setting for `enabled_mcp_servers` | The MCP servers that this role utilizes. Accepts either a YAML list or a comma-separated string |
| `skills_enabled` | Global setting for `skills_enabled` | Master switch for [skills](Skills) under this role. Set to `false` to hide all skills |
| `enabled_skills` | Global setting for `enabled_skills` | The [skills](Skills) this role activates. Accepts either a YAML list or a comma-separated string |
| `auto_continue` | Global setting for `auto_continue` | Enable the [Todo System](TODO-System) auto-continuation for this role |
Skills.md
+6 -6
@@ -68,12 +68,12 @@ To see complete examples, look at the [bundled built-in skills](https://github.c
The YAML frontmatter at the top of `SKILL.md` is where you declare the skill's metadata and what extra capabilities it
grants when loaded. All fields are optional.
| Field | Default | Description |
|-----------------------|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `description` | empty | Short one-line description shown to the model when it lists available skills. Make it specific: this is what helps the model decide when to load. |
| `enabled_tools` | none | Comma-separated tool names that become available while the skill is loaded. Union with the active role/agent/session's tools. Tools must exist in [visible tools](Tools). |
| `enabled_mcp_servers` | none | Comma-separated MCP server names. Skills can reference servers from your `mcp.json`; those servers are auto-acquired on load and released on unload via reference counting. |
| `auto_unload` | `false` | If `true`, the skill is automatically removed from the registry at the end of every turn where the model produced a final response (no more tool calls). |
| Field | Default | Description |
|-----------------------|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `description` | empty | Short one-line description shown to the model when it lists available skills. Make it specific: this is what helps the model decide when to load. |
| `enabled_tools` | none | Comma-separated tool names that become available while the skill is loaded. Union with the active role/agent/session's tools. Tools must exist in [visible tools](Tools). |
| `enabled_mcp_servers` | none | MCP server names the skill needs. Accepts a YAML list (preferred) or a comma-separated string. Skills can reference servers from your `mcp.json`; those servers are auto-acquired on load and released on unload via reference counting. |
| `auto_unload` | `false` | If `true`, the skill is automatically removed from the registry at the end of every turn where the model produced a final response (no more tool calls). |
## Body