shreemaan-abhishek opened a new pull request, #14019:
URL: https://github.com/apache/apisix/pull/14019

   ### Description
   
   The `mcp-bridge` plugin was marked as deprecated in #13640, with a note that 
it would be removed in a future release. This PR removes it.
   
   Changes:
   
   - Delete `apisix/plugins/mcp-bridge.lua` and its `apisix/plugins/mcp/` 
modules (server, SSE transport, shared-dict broker), which no other plugin uses.
   - Drop it from the default plugin list, `conf/config.yaml.example`, the 
`Makefile` install target, and `t/admin/plugins.t`.
   - Delete its docs page and sidebar entry, and the README mention.
   - Delete its tests (`t/plugin/mcp-bridge.t`, `t/plugin/mcp-bridge.spec.ts`, 
`t/cli/test_mcp_bridge.sh`) and the CI step that built the filesystem MCP 
server they needed (`ci/prepare_filesystem_mcp.sh`).
   - The `mcp-session` shared dict is now declared only when `openapi-to-mcp` 
is enabled, which still uses it.
   
   Users who still list `mcp-bridge` in their `plugins` config need to remove 
it. `openapi-to-mcp` is the MCP plugin going forward.
   
   #### Which issue(s) this PR fixes:
   <!--
   *Automatically closes linked issue when PR is merged.
   Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
   -->
   Fixes #
   
   ### Checklist
   
   - [x] I have explained the need for this PR and the problem it solves
   - [x] I have explained the changes or the new features added to this PR
   - [ ] I have added tests corresponding to this change
   - [x] I have updated the documentation to reflect this change
   - [ ] I have verified that this change is backward compatible (If not, 
please discuss on the [APISIX mailing 
list](https://github.com/apache/apisix/tree/master#community) first)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to