Has anyone gotten a Python stdio tool to work reliably on Linux? #539
Postmanplayx
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Pre-submission Checklist
Discussion Topic
Hi everyone,
I'm trying to figure out an issue I'm having with stdio tools on Linux and was hoping someone here might have some ideas.
The Current Problem (Python):
I'm trying to connect my local Obsidian vault to AnythingLLM using a Python tool called Basic Memory. It runs as a stdio subprocess. I've managed to get the service running correctly – it connects to the client and indexes all my files on startup. The problem is that when the client sends a query, the Python code on the server that is supposed to handle the search is never actually called. The request just silently fails. I've documented this in a bug report here:
https://github.com/modelcontextprotocol/python-sdk/issues/1278
The Previous Problem (TypeScript):
What's strange is that I ran into the exact same issue a while ago with a different tool (Cursor, the code editor), which uses the TypeScript version of this protocol. The symptoms were identical: the service would connect, but the tool handlers would never fire. I documented that here:
https://github.com/modelcontextprotocol/typescript-sdk/issues/576
Since I'm seeing the same "silent failure" in two different tools with two different language SDKs (Python and TypeScript), I'm starting to think this is a deeper issue with the stdio transport on Linux.
My questions are:
Has anyone else run into this?
More importantly, has anyone found a reliable workaround or a different setup that works for this kind of use case?
Thanks in advance for any help!
Beta Was this translation helpful? Give feedback.
All reactions