Skip to content

docs(mcp): correct stale codex-exec gap + flag divergent MCP packages (revert #474 v2 tool)#475

Merged
samxu01 merged 1 commit into
mainfrom
wedge-rollout
Jun 9, 2026
Merged

docs(mcp): correct stale codex-exec gap + flag divergent MCP packages (revert #474 v2 tool)#475
samxu01 merged 1 commit into
mainfrom
wedge-rollout

Conversation

@samxu01

@samxu01 samxu01 commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Follow-up to #474 after discovering I'd tested/fixed the wrong MCP package.

Corrections

1. codex exec MCP gap is FIXED on codex 0.133 (the 2026-05-16 finding was 0.125-specific). Captured the model-request payload from codex exec against a mock Responses endpoint — 0.133 forwards the full commonly_* namespace to the model inline (mcp__commonly__ namespace tool). Updated CLAUDE.md + docs/MCP_INTEGRATION.md. Action: bump Cody/cloud-codex codex to ≥0.133. The openclaw-extension gap (moltbots, separate non-MCP path) remains and is now flagged as distinct.

2. Two packages both present as "the Commonly MCP server":

  • commonly-mcp/ (root) = @commonlyai/mcp v0.1.2 — published, used by the cluster + npx + all real tools. Already has commonly_read_agent_memory / commonly_save_my_memory.
  • packages/commonly-mcp/ = @commonly/mcp-serverunpublished CAP-rewrite, local-dev/demo only, divergent tool set.

Root @commonlyai/mcp is canonical. Added a banner to the v2 README so it stops misleading readers.

Revert

Reverts the v2-package commonly_memory_read addition from #474 — the shipped package already has read-back, so it only deepened divergence in an abandoned package. The package-independent backend convergence smoke test from #474 stays on main.

Net of the wedge investigation: the wedge already works on shipped tooling (@commonlyai/mcp has envelope read+write; codex 0.133 surfaces them). The real issues were a stale doc and a confusing two-package split — both addressed here.

🤖 Generated with Claude Code

Two corrections after smoke-testing the shared-memory wedge:

1. codex `exec` MCP-tool surfacing is FIXED on codex 0.133 (the 2026-05-16
   "no commonly_* tools visible" finding was specific to 0.125). Verified by
   capturing the model-request payload codex builds against a mock Responses
   endpoint: 0.133 forwards the full commonly_* namespace inline as an
   mcp__commonly__ namespace tool. Updated CLAUDE.md + docs/MCP_INTEGRATION.md;
   action is to bump Cody/cloud-codex codex to >=0.133. The openclaw-extension
   gap (moltbots, separate non-MCP path) remains and is now called out as such.

2. Two packages both present as "the Commonly MCP server" and had diverged:
   - commonly-mcp/ (root) = @commonlyai/mcp v0.1.2 — PUBLISHED, used by the
     cluster + npx + all real tools. Has commonly_read_agent_memory /
     commonly_save_my_memory.
   - packages/commonly-mcp/ = @commonly/mcp-server — UNPUBLISHED CAP-rewrite,
     local-dev/demo only, divergent tool set (commonly_memory_sync).
   Root @commonlyai/mcp is canonical. Added a prominent banner to the v2
   README so it stops misleading readers (it misled this investigation).

Also reverts the v2-package read-tool addition from #474 (commonly_memory_read
in packages/commonly-mcp) — the shipped @commonlyai/mcp already has read-back,
so that change only deepened divergence in an abandoned package. The
package-independent backend convergence smoke test from #474 stays on main.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@samxu01 samxu01 merged commit 897aed6 into main Jun 9, 2026
9 checks passed
@samxu01 samxu01 deleted the wedge-rollout branch June 9, 2026 14:59
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