perf: Reduce MCP server memory usage by 53% - #64
Open
kdcokenny wants to merge 1 commit into
Open
Conversation
kdcokenny
marked this pull request as ready for review
July 30, 2026 23:28
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addresses #63
This is the minimal TypeScript fix described in the issue. It reduces memory usage from around 89 MB to 42 MB without replacing Node or the official MCP SDK.
The main change is generating the advertised JSON schemas during the existing build step and only creating each Zod validation schema when its tool is actually called. The Dokploy API client is also loaded on its first use.
All 524 tools and their advertised schemas remain identical. Stdio, Streamable HTTP, SSE, tag filtering, validation, redaction, and existing packaging are preserved.
The only measured tradeoff is around 65 ms of additional latency on the first tool call. Later calls perform approximately the same as before.
Tests, type-checking, build, package verification, and MCP transport checks pass.