Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[PR #4773] [MERGED] Upgrade MCP SDK to Latest (1.24.3) #4761

New Issue
Closed
opened 2026-02-22 18:36:29 -05:00 by yindo · 0 comments
yindo commented 2026-02-22 18:36:29 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/Mintplex-Labs/anything-llm/pull/4773
Author: @angelplusultra
Created: 12/12/2025
Status: ✅ Merged
Merged: 12/12/2025
Merged by: @timothycarambat

Base: master ← Head: update-mcp-sdk

📝 Commits (2)

  • 6d6381d upgrade mcp sdk to latest (1.24.3)
  • 798a27c Upgrade MCP version floor in package.json to 1.24.3

📊 Changes

2 files changed (+222 additions, -224 deletions)

View changed files

📝 server/package.json (+1 -1)
📝 server/yarn.lock (+221 -223)

📄 Description

Pull Request Type

  • ✨ feat
  • 🐛 fix
  • ♻️ refactor
  • 💄 style
  • 🔨 chore
  • 📝 docs

What is in this change?

This PR upgrades the MCP SDK (@modelcontextprotocol/sdk) in /server subrepo to 1.23.3.

Just to clarify, you might notice the version remains the same in package.json, it's using the semver range syntax (^) specifying that anything between 1.11.0 and 2.0.0 is compatible, but the exact version we're using is pinned in the yarn.lock.

After running yarn to update your packages, you can run

cat node_modules/@modelcontextprotocol/sdk/package.json | grep '"version"'

To verify what version is in your node_modules

Additional Information

Developer Validations

  • I ran yarn lint from the root of the repo & committed changes
  • Relevant documentation has been updated
  • I have tested my code functionality
  • Docker build succeeds locally

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/Mintplex-Labs/anything-llm/pull/4773 **Author:** [@angelplusultra](https://github.com/angelplusultra) **Created:** 12/12/2025 **Status:** ✅ Merged **Merged:** 12/12/2025 **Merged by:** [@timothycarambat](https://github.com/timothycarambat) **Base:** `master` ← **Head:** `update-mcp-sdk` --- ### 📝 Commits (2) - [`6d6381d`](https://github.com/Mintplex-Labs/anything-llm/commit/6d6381d33bfc253f45819f2b92f415f12885dc10) upgrade mcp sdk to latest (1.24.3) - [`798a27c`](https://github.com/Mintplex-Labs/anything-llm/commit/798a27c6a0653cd4e622735cb30852f27a2b8a00) Upgrade MCP version floor in package.json to 1.24.3 ### 📊 Changes **2 files changed** (+222 additions, -224 deletions) <details> <summary>View changed files</summary> 📝 `server/package.json` (+1 -1) 📝 `server/yarn.lock` (+221 -223) </details> ### 📄 Description ### Pull Request Type <!-- For change type, change [ ] to [x]. --> - [ ] ✨ feat - [x] 🐛 fix - [ ] ♻️ refactor - [ ] 💄 style - [ ] 🔨 chore - [ ] 📝 docs ### What is in this change? <!-- Describe the changes in this PR that are impactful to the repo. --> This PR upgrades the MCP SDK (`@modelcontextprotocol/sdk`) in `/server` subrepo to `1.23.3`. Just to clarify, you might notice the version remains the same in `package.json`, it's using the semver range syntax (`^`) specifying that anything between 1.11.0 and 2.0.0 is compatible, but the **exact** version we're using is pinned in the `yarn.lock`. After running `yarn` to update your packages, you can run ``` cat node_modules/@modelcontextprotocol/sdk/package.json | grep '"version"' ``` To verify what version is in your `node_modules` ### Additional Information <!-- Add any other context about the Pull Request here that was not captured above. --> ### Developer Validations <!-- All of the applicable items should be checked. --> - [x] I ran `yarn lint` from the root of the repo & committed changes - [x] Relevant documentation has been updated - [x] I have tested my code functionality - [x] Docker build succeeds locally --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-22 18:36:29 -05:00
yindo closed this issue 2026-02-22 18:36:29 -05:00
yindo changed title from [PR #4773] Upgrade MCP SDK to Latest (1.24.3) to [PR #4773] [MERGED] Upgrade MCP SDK to Latest (1.24.3) 2026-06-05 15:20:15 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#4761
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?