speakeasy-api / speakeasy-api/docs-mcp
Not connecting/discovering tools behind an MCP Proxy
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 8
- Forks
- 3
- Avg merge
- 6m
- Merged PRs (30d)
- 8
Description
Hi. Great tool.
I installed and deployed the server, and it works great when I connect directly.
I tried putting a FastMCP proxy in front of it, using the something like the code below:
docs_mcp_server_v2 = create_proxy(
[URL to docs-mcp server], name="Docs MCP Proxy Server"
)
(https://gofastmcp.com/servers/composition)
In VS Code, I see: "Discovered 0 tools". though, there is not an error in the output of VS code.
In the terminal, I see: "connect_tcp.failed exception=ConnectError(OSError('All connection attempts failed'))". (This is the proxy).
Also, I am starting the server via http transport.
So, essentially, the server works perfectly (discovers 2 tools) when I connect to it directly from VS Code or another MCP client, but seems to have some error when I try to add a proxy in front of it.
Thanks in advance.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the direct connection and the FastMCP create_proxy setup described in the issue, using the HTTP transport and the VS Code discovery flow. Compare the proxy's connection output with the direct server behavior; done means the proxy connects successfully and VS Code discovers the server's two tools.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend-api-design
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100