You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(server): MCP endpoints API consolidation (#2829)
## Overview
This PR serves as the foundational layer that will eventually merge all
upcoming PRs for the new test harness and new MCP integration tests for
multiple databases.
**Before** | **After**
--- | ---
<img width="1133" height="1032" alt="image"
src="https://github.com/user-attachments/assets/4a4fe226-aea8-43d7-9c80-fbedf0ce2e5b"
/> | <img width="1323" height="1539" alt="image"
src="https://github.com/user-attachments/assets/75526df2-3351-4dd9-a3d7-f3e04d177d0e"
/>
## Strategy
While the legacy integration tests continue to run over the legacy
`/api` endpoints, we are introducing the new native MCP JSON-RPC harness
in parallel. This allows us to verify both pathways side-by-side without
breaking existing CI coverage.
To support this, we utilize the `--enable-api` flag to control whether
the server initializes the legacy API handlers or runs in MCP-only mode.
This ensures that the new tests can accurately verify the behavior of
the server when running in its final intended configuration.
## Changes
- Updates to `internal/server/server.go` to support dynamic execution
and flag-controlled initialization.
- Frontend files updated (`loadTools.js` and `runTool.js`) to streamline
how tools are loaded and invoked in the UI, aligning it with the
upcoming native MCP transition.
## Checklist
- [x] Ensure the tests and linter pass
- [x] Manually verified functionality of Toolbox UI
---------
Co-authored-by: Yuan Teoh <yuanteoh@google.com>
Copy file name to clipboardExpand all lines: UPGRADING.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,6 @@ If you still require the legacy `/api` endpoint, you must explicitly activate it
26
26
endpoint exclusively, as the `/api` endpoint is now deprecated. If your workflow
27
27
relied on a non-standard feature that is missing from the new implementation, please submit a
28
28
feature request on our [GitHub Issues page](https://github.com/googleapis/genai-toolbox/issues).
29
-
***UI Dependency:** Until the UI is officially migrated, it still requires the API to function. You must run the toolbox with both flags: `./toolbox --ui --enable-api`.
30
29
31
30
### 2. Strict Tool Naming Validation (SEP986)
32
31
Tool names are now strictly validated against [ModelContextProtocol SEP986 guidelines](https://github.com/alexhancock/modelcontextprotocol/blob/main/docs/specification/draft/server/tools.mdx#tool-names) prior to MCP initialization.
@@ -110,4 +109,4 @@ The following CLI flags are deprecated and will be removed in a future release.
110
109
111
110
***Prebuilt Tools:** Toolsets have been resized for better performance.
112
111
## 📚 Documentation Moved
113
-
Our official documentation has a new home! Please update your bookmarks to [mcp-toolbox.dev](http://mcp-toolbox.dev).
112
+
Our official documentation has a new home! Please update your bookmarks to [mcp-toolbox.dev](http://mcp-toolbox.dev).
0 commit comments