Skip to content llms.txt

OpenCode — MCP Configs

File format
JSON with comments
Discovery paths
opencode.json, opencode.jsonc
Syllago install method
JSON merge
Symlink support
No
Config file
opencode.json
Transports
stdio

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 keyConversionCanonical keySummary
type Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more → Local MCP servers launched via command/args/env and communicate over stdio.

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.

FeatureConversionSummary
env_var_expansion Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more → env_variable_expansion: environment variables configured in server env blocks
JSONC config file format Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more → MCP servers are configured in opencode.json or opencode.jsonc at the project root; JSONC allows comments.
transport_types Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more → transport_types: OpenCode documents stdio transport; remote transports (http/sse) are available on sst/opencode depending on version

Sources

Source
https://opencode.ai/docs/mcp-servers/
https://raw.githubusercontent.com/sst/opencode/dev/schema.json