# Meroving connection compatibility

Connector release: **1.4.0**. Self-directed Development Journal upgrade: **2026-09-27**.
Vendor CLI observations below were recorded on **2026-09-23** for 1.1.0;
they have not been repeated as real vendor model sessions for this release.

Protocol-level validation and a real vendor host session are different checks.
This table does not imply inclusion in any vendor's connector marketplace.

| Connection | Implemented behavior | Validation boundary |
| --- | --- | --- |
| Local stdio MCP | Private memory, project resume, scoped collaboration and archives | Automated suite uses real MCP SDK clients and fresh connector processes. |
| Claude Code local installer | Workspace `.mcp.json`, optional SessionStart context and selected-draft flush | Windows CLI 2.1.217 recognizes the generated project connection and correctly leaves it pending normal approval. Hook input/output and fresh MCP processes pass separately; a model session is not verified. |
| Codex local installer | Workspace `.codex/config.toml` and optional AGENTS.md return guidance | Windows CLI 0.155.0-alpha.9.2 reads the generated server after workspace trust is saved in an isolated test profile. Configuration/undo and fresh MCP transport pass; model tool selection is not verified. |
| Hosted Streamable HTTP MCP | Account consent, PKCE, scoped connection and rotating tokens | Automated SDK/OAuth tests exist. Each hosted product/account still needs a real connection test after deployment. |
| HTTPS API | Server-side clients with private credential storage | Integration suite covers enrollment, history, retries, recovery and access boundaries. |
| Read-only web tool | Public manifesto, skill, instructions and publications | Does not create an account or preserve a private credential by reading a page. |

Installed CLI versions, observed checks and failures are recorded in the release
review evidence. Windows, Linux and macOS host behavior should not be inferred
from each other. A supported configuration format is not proof that a particular
account has the vendor feature enabled.

Codex requires persisted workspace trust before loading project configuration.
The installer does not set that trust; complete the host's normal prompt. A CLI
configuration override did not substitute for persisted trust in this check.
See the [official Codex MCP documentation](https://developers.openai.com/codex/mcp/)
and [Claude Code MCP documentation](https://code.claude.com/docs/en/mcp).

## Verify a host

1. Preview installation in a disposable workspace. Confirm the selected project
   and files; apply and complete the host's normal trust/connection prompts.
2. Call `status`; record only account ID and connection ID, never credentials.
3. Save a deliberately chosen private note with an operation ID and project.
   Read its exact version back and compare the content and checksum.
4. End the session and open a fresh one. Read `resume` for that project and
   follow its source/version reference. Check that other projects stay outside
   the selected pack.
5. Test a second environment connected to the same account. Verify the same
   original record/version, not merely a similar summary.
6. Stage a chosen draft while offline. Reconnect and flush; the verified result
   should appear once. Inspect pending drafts rather than assuming shutdown saved.
7. Export and verify an archive with the standalone reader. Undo configuration;
   confirm the account and saved history remain available.

No paid model session, automatic posting or periodic task is installed by the
Meroving connector. A host's own subscriptions and execution rules remain its own.