docs(mcp): add a local stdio MCPToolset example using vestige-mcp-server#536
Open
samvallad33 wants to merge 1 commit into
Open
docs(mcp): add a local stdio MCPToolset example using vestige-mcp-server#536samvallad33 wants to merge 1 commit into
samvallad33 wants to merge 1 commit into
Conversation
|
@samvallad33 is attempting to deploy a commit to the deepset Team on Vercel. A member of the Team first needs to authorize it. |
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
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.
Hi deepset team. I maintain Vestige (github samvallad33), a local-first MCP memory server, and I have been running it through the existing mcp-haystack integration. The MCP page documents StdioServerInfo with uvx and the time server, and I wanted to add one more local-stdio example to the Usage section, this time loading a stateful server with MCPToolset rather than a single MCPTool, in case it is useful.
Nothing new is needed on the Haystack side. Vestige is a stdio MCP server published on npm, so MCPToolset reaches it the same way it reaches any other stdio server. The example loads the whole toolset and runs it through ToolInvoker, which felt like a nice complement to the single-tool examples already on the page.
For context: Vestige is a local-first cognitive memory MCP server for AI coding agents. FSRS-6 retention, prediction-error gating, active forgetting, spreading activation, 3D dashboard. Single Rust binary, npm install -g vestige-mcp-server. It is community-maintained by me and not affiliated with deepset.
I deliberately did not open a new integrations/vestige.md, since Vestige does not ship a vestige-haystack package yet and memory is already represented by mem0.md, so a standalone index entry would not match how the catalog is structured. If you would rather this example live in the Haystack docs instead of the index, or not at all, that is completely fine, just say so and I will close it. If a standalone catalog entry would be welcome down the line, I am happy to build a proper vestige-haystack wrapper package first so it follows the same pypi-backed pattern as everything else. Thanks for maintaining this.