Skip to content

docs(readme): add OpenCode install instructions - #287

Open
eloyred wants to merge 1 commit into
awslabs:mainfrom
eloyred:docs/opencode-install-section
Open

eloyred wants to merge 1 commit into
awslabs:mainfrom
eloyred:docs/opencode-install-section

Conversation

@eloyred

@eloyred eloyred commented Oct 16, 2026

Copy link
Copy Markdown

Adds an ### OpenCode section under ## Installation with per-plugin OpenCode MCP config and skill copy paths, translated from each plugin's .mcp.json and skills/. Notes that migration-to-aws is empty on main. Calls out aws-architecture-diagram as having no equivalent in the successor toolkit repo.

Related

Follow-up to the README's ### Cursor / ### Kiro (experimental) sections. No existing issue.

Changes

  • New ### OpenCode subsection in README.md, between ### Cursor and ### Kiro (experimental).
  • For each of the 9 plugins: a #### <plugin-name> block with the SKILL.md paths to copy and the OpenCode mcp entry translated from the plugin's .mcp.json.
  • Inline note under deploy-on-aws calling out the aws-architecture-diagram skill and its .drawio output.
  • One > [!NOTE] block warning that allowed-tools / user-invocable frontmatter keys are Claude-specific and OpenCode ignores them.
  • A #### Verifying it works block using opencode mcp list / opencode mcp debug <name>.

Mechanical changes documented inline:

  • type: "http" (Claude) → type: "remote" (OpenCode). OpenCode only accepts local or remote.
  • command / args (Claude) → command array (OpenCode). uvx must be on PATH.
  • disabled: true entries (aurora-dsql, cloudwatch in databases-on-aws) are omitted by default.

migration-to-aws is documented as empty on main — no .mcp.json, no skills/. Filing a separate issue for that.

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.

Adds an `### OpenCode` section under `## Installation` with per-plugin OpenCode MCP config and skill copy paths, translated from each plugin's `.mcp.json` and `skills/`. Notes that `migration-to-aws` is empty on main. Calls out `aws-architecture-diagram` as having no equivalent in the successor toolkit repo.

Signed-off-by: Eloy Redondo <eloyredondodealvaro@gmail.com>
@eloyred

eloyred commented Oct 16, 2026

Copy link
Copy Markdown
Author

Filed #288 separately for the empty migration-to-aws plugin. The new ### OpenCode section documents the current state; restoring or deprecating the plugin is a separate concern.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant