Crush — MCP Configs

File format

JSON

Discovery path

crush.json

Syllago install method

JSON merge

Symlink support

No

Config file

crush.json

Transports

stdio, http, sse

Features

How each feature converts to syllago's canonical format. See format conversion for what these statuses mean.

Fields

Native frontmatter or config fields this provider exposes. The first column is the provider's own field name; the canonical key column links to syllago's cross-provider equivalent.

Config key	Conversion	Canonical key	Summary
type	Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more →	—	Supports stdio, http, and sse transports for MCP server connections, configured via the mcp key in crush.json.

Other features

Behaviors, conventions, and capabilities that aren't tied to a single named field — things like path-based activation, discovery rules, and lifecycle behavior.

Feature	Conversion	Summary
env_var_expansion	Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more →	env_variable_expansion: Crush MCP configuration supports environment variable references in server env blocks
transport_types	Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more →	transport_types: Crush documents stdio, http, and sse transports in its JSON schema for MCP server configuration
Unified crush.json config file	Not portable Conversion type: Not portable Unique to this provider — can’t be carried across providers. Learn more →	MCP servers, tools, permissions, and model settings all share a single crush.json config file rather than being split across multiple settings files.

Sources

Source
https://raw.githubusercontent.com/charmbracelet/crush/main/schema.json
https://raw.githubusercontent.com/charmbracelet/crush/main/README.md