dan-kwiat
Joined 7 years ago
Karma
3
Submissions
10
Member since
Mar 20
Recent submissions
Comment · 3 months ago
Great work! Any word on when to expect support across claude clients?
Comment · 3 months ago
URL Elicitation works well if a human is driving the client. Unfortunately MCP client support is patchy but I expect that will change now the protocol is stateless.
Comment · 1 year ago
I'm building a registry of typescript servers here: https://github.com/wegotdocs/open-mcp
Comment · 1 year ago
Thanks, I just added support for relative URLs, try again. Your OpenAPI spec defines a relative base URL for the server /metatx but no domain. You can now specify the full base URL in your MCP client's environment variables:
`OPEN_MCP_BASE_URL="https://engineapi.moonstream.to/metatx"`
Comment · 1 year ago
I just made a tool which parses any OpenAPI spec to MCP spec: https://www.open-mcp.org (literally just deployed so I don't know if the DNS has propagated globally yet..)
Comment · 7 years ago
I agree they are great but isn't most of the work in fetching & sorting the data? I can't see how this would work as a general widget.
In terms of the UI - I made a react component for showing dynamic suggestions (essentially a wrapper for downshift). And I've found the options out there for the sorting part quite good (e.g. match-sorter for sync or Elasticsearch completion suggester for async)