Skip to content

Conversation

@pcarleton
Copy link
Member

Summary

Adds server conformance testing alongside the existing client conformance tests.

Changes

  • Move conformance server to src/conformance/everything-server.ts
  • Add scripts/run-server-conformance.sh to start server and run tests
  • Add server conformance scripts to package.json:
    • test:conformance:server - run active server tests
    • test:conformance:server:all - run all server tests
    • test:conformance:all - run both client and server tests
  • Update GitHub Actions workflow with both client and server jobs
  • Add src/conformance/README.md with usage instructions
  • Add express, cors, and @modelcontextprotocol/server to root devDependencies

Test Results

- Move conformance server to src/conformance/everything-server.ts
- Add scripts/run-server-conformance.sh to start server and run tests
- Add server conformance scripts to package.json
- Update GitHub Actions workflow with both client and server jobs
- Add src/conformance/README.md with usage instructions
- Add express, cors, and @modelcontextprotocol/server to root devDependencies
@pcarleton pcarleton requested a review from a team as a code owner January 12, 2026 18:45
@changeset-bot
Copy link

changeset-bot bot commented Jan 12, 2026

⚠️ No Changeset found

Latest commit: 8856303

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@pkg-pr-new
Copy link

pkg-pr-new bot commented Jan 12, 2026

Open in StackBlitz

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/client@1375
npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/server@1375

commit: 8856303

// Configure CORS to expose Mcp-Session-Id header for browser-based clients
app.use(
cors({
origin: '*',

Check warning

Code scanning / CodeQL

Permissive CORS configuration Medium

CORS Origin allows broad access due to
permissive or user controlled value
.
- Remove unused Tool type import
- Remove unused JSON_SCHEMA_2020_12_INPUT_SCHEMA constant
  (SEP-1613 test is pending - SDK validation supports the fields via PR #1135,
  but tool registration doesn't yet support generating raw JSON Schema)
- Remove emoji from console.log
- Alphabetize devDependencies in package.json
Pass through all arguments to conformance CLI instead of just suite name.
This allows passing --scenario, --suite, or any other flags.
Runs the conformance server standalone for debugging.
.idea/

# Conformance test results
results/
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: this feels slightly odd - it makes sense in the conformance repo because it's obvious what results is there, but here it could be slightly confusing.

E.g. src/conformance/results/ or conformance-results (nit only though, not sure if that might require a bunch of refactors)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yea... let me make an issue. i want to just not output the results by default, we don't use them.

#!/usr/bin/env node

/**
* MCP Conformance Test Server
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this file seems to be mostly a copy-paste from the everything-server we previously had in the conformance repo so sgtm

@pcarleton pcarleton merged commit 0073ab2 into main Jan 13, 2026
21 of 22 checks passed
@pcarleton pcarleton deleted the server-conformance-tests branch January 13, 2026 17:09
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.

3 participants