[GH-ISSUE #460] Publish REA as a discoverable MCP server in the MCP Registry #253

New issue

Closed

opened 2026-10-15 18:23:01 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-15 18:23:01 +00:00

Owner

Originally created by @morluto on GitHub (Aug 1, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/460

Current limitation

REA exposes an MCP server through its npm distribution, but the repository does not currently publish MCP Registry metadata or an automated registry release path. Users therefore cannot discover the server through the official MCP Registry and may need to configure it manually.

Desired outcome

Publish REA under the registry name io.github.morluto/rea, with:

an mcpName ownership marker in the npm package;
a checked-in server.json describing the npm package, npx runtime, stdio transport, and version;
package and registry metadata kept at the same release version;
a trusted release-tag workflow using mcp-publisher and GitHub OIDC;
documentation for installing, launching, and configuring the published MCP server.

The registry entry should point at the existing npm artifact rather than introduce a second distribution path.

Originally created by @morluto on GitHub (Aug 1, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/460 ## Current limitation REA exposes an MCP server through its npm distribution, but the repository does not currently publish MCP Registry metadata or an automated registry release path. Users therefore cannot discover the server through the official MCP Registry and may need to configure it manually. ## Desired outcome Publish REA under the registry name `io.github.morluto/rea`, with: - an `mcpName` ownership marker in the npm package; - a checked-in `server.json` describing the npm package, `npx` runtime, stdio transport, and version; - package and registry metadata kept at the same release version; - a trusted release-tag workflow using `mcp-publisher` and GitHub OIDC; - documentation for installing, launching, and configuring the published MCP server. The registry entry should point at the existing npm artifact rather than introduce a second distribution path.

bsakaguchi

2026-10-15 18:23:01 +00:00

closed this issue
added the
area: mcp

enhancement
labels

bsakaguchi commented

2026-10-15 18:23:03 +00:00

Author

Owner

@morluto commented on GitHub (Aug 1, 2026):

Jacobian now has a working release pattern that this issue can follow:

keep server.json at the release tag with matching top-level and package versions;
add mcpName: io.github.morluto/rea to the published npm package;
add a publish-mcp job after npm publication;
install a pinned mcp-publisher release, run mcp-publisher validate, authenticate with mcp-publisher login github-oidc, and publish;
grant only contents: read and id-token: write; no interactive login or long-lived registry token is needed.

The registry name should remain io.github.morluto/rea; the display title can be “REA”. See Jacobian’s implementation in .github/workflows/release.yml and the MCP Registry GitHub Actions guide.

@morluto commented on GitHub (Aug 1, 2026): Jacobian now has a working release pattern that this issue can follow: - keep `server.json` at the release tag with matching top-level and package versions; - add `mcpName: io.github.morluto/rea` to the published npm package; - add a `publish-mcp` job after npm publication; - install a pinned `mcp-publisher` release, run `mcp-publisher validate`, authenticate with `mcp-publisher login github-oidc`, and publish; - grant only `contents: read` and `id-token: write`; no interactive login or long-lived registry token is needed. The registry name should remain `io.github.morluto/rea`; the display title can be “REA”. See Jacobian’s implementation in [.github/workflows/release.yml](https://github.com/morluto/jacobian/blob/main/.github/workflows/release.yml) and the [MCP Registry GitHub Actions guide](https://modelcontextprotocol.io/registry/github-actions).

bsakaguchi referenced this issue

2026-10-16 21:12:21 +00:00

[PR #253] [MERGED] chore(main): release rea-agents 2.0.0 #1904

bsakaguchi added

enhancement

and removed

enhancement

labels

2026-10-31 00:28:55 +00:00