Skip to content

feat: migrate mcp-server and virtual-server endpoints to v1 API paths - #98

Open
marekdano wants to merge 2 commits into
mainfrom
85-migrate-v1-endpoints
Open

feat: migrate mcp-server and virtual-server endpoints to v1 API paths#98
marekdano wants to merge 2 commits into
mainfrom
85-migrate-v1-endpoints

Conversation

@marekdano

Copy link
Copy Markdown
Contributor

Closes #85

Summary

  • Migrate MCP-server and virtual-server CRUD calls from the legacy /gateways and /servers API paths to the versioned /v1/mcp-servers and /v1/virtual-servers paths
  • Update corresponding unit tests, e2e specs, and MSW mock handlers to match the new paths
  • Leave the user-facing MCP connection URL (utils.ts getVirtualServerEndpoint) unchanged, since it reflects protocol data, not the admin API

Details

This is a mechanical rename with no behavior changes. The new versioned paths are already live on the backend (mounted alongside the legacy paths since mcp-context-forge commit f9af132ee), so this is a forward-compatible migration ahead of the legacy paths being deprecated.

Test plan

  • All 494 tests across the 15 affected files pass
  • Verified no remaining references to the old /gateways or /servers API paths in src/ or e2e/
  • Confirmed the new /v1/mcp-servers and /v1/virtual-servers routes are mounted on the backend

Signed-off-by: Marek Dano <mk.dano@gmail.com>
Signed-off-by: Marek Dano <mk.dano@gmail.com>
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.

Migrate web UI to /v1/mcp-servers and /v1/virtual-servers

1 participant