Skip to content

[DO NOT MERGE] Mcp 538 no express#1272

Draft
manupedrozo wants to merge 4 commits into
mainfrom
MCP-538-no-express
Draft

[DO NOT MERGE] Mcp 538 no express#1272
manupedrozo wants to merge 4 commits into
mainfrom
MCP-538-no-express

Conversation

@manupedrozo

Copy link
Copy Markdown
Collaborator

Quick branch to see if we can implement mocks using Node's built-in http package instead of express.

See #1268

maastha added 3 commits June 21, 2026 15:03
Stand up the wrapper package's offline test tiers, reusing the repo's Vitest
setup (auto-discovered by the existing run-tests CI job, no workflow change):

- Unit scaffold (tokenManager.test.ts) — network-mocked, it.todo for MCP-539.
- Integration harness: an in-process fake remote MCP server
  (src/testHelpers/fakeRemote.ts, excluded from dist) driven via the MCP SDK
  client over a spawned wrapper (WRAPPER_CLI_PATH override); one live sanity
  test plus it.todo scenarios for MCP-539.
- Add @modelcontextprotocol/sdk, express, @types/express devDeps + pretest
  compile so dist/cli.js exists for the harness.
- Document wrapper unit/integration testing in CONTRIBUTING.md.

Builds and runs green without any wrapper logic (cli.ts is still a stub).
…upport SSE+JSON (MCP-538)

- Rename the test double from 'fake' to 'mock' (file, type, function, literals).
- Rewrite comments in plain language; add a reason to the eslint-disable.
- Mock remote now defaults to SSE (matching cloud-dev per MCP-542) with a
  responseMode: 'json' option; notifications return 202.
Replace the ASCII diagram with a short verbal description of how the
integration tests are wired.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants