Skip to content

ci: add isolated MCP server conformance smoke checks - #27

Open
AKzar1el wants to merge 1 commit into
devnoname120:mainfrom
AKzar1el:ci/mcp-conformance-smoke-20261116
Open

AKzar1el wants to merge 1 commit into
devnoname120:mainfrom
AKzar1el:ci/mcp-conformance-smoke-20261116

Conversation

@AKzar1el

Copy link
Copy Markdown
Contributor

Why

Codexify already tests its MCP transport internally, but an independent protocol smoke check can catch regressions in the public server handshake and tool-catalogue response.

Changes

  • Add a small, read-only GitHub Actions job (PR path-filtered and manually dispatchable), with a 15-minute bound and reusable Rust cache.
  • Start a freshly compiled Codexify binary against an ephemeral configuration, workspace and port, with user MCP imports, agent chat, skills and worktree cleanup disabled.
  • Run the pinned official @modelcontextprotocol/conformance@0.1.16 checks for server-initialize and tools-list.
  • Shut down the child process and remove the temporary workspace on both success and failure.

Verification

  • The same isolated launcher and both scenarios passed on a separate pilot branch: successful 2/2 run.
  • This PR's CI should revalidate against current upstream main.

Scope and trade-offs

This is a small protocol smoke gate, not full MCP certification. It deliberately does not claim OAuth, resources, prompts, or tool-invocation conformance. No Rust dependencies, runtime logic, production configuration, API tokens, or Cloudflare integration are added. The new workflow is independent of the existing CI job and only runs for relevant PR paths or manual dispatch.

The branch contains one commit and two new files based directly on upstream main.

@AKzar1el
AKzar1el marked this pull request as ready for review November 16, 2026 21:23

This branch has not been deployed

No deployments
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