dan-kwiat

7 ms·

1. 1.▲
   by dan-kwiat 2mo ago

   Great work! Any word on when to expect support across claude clients?
2. 2.▲
   by dan-kwiat 2mo 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.
3. 3.▲
   Matched Clean Power Index(matched.energy)

   1 points by dan-kwiat 11mo ago|0 comments
4. 4.▲
   by dan-kwiat 1y ago

   I'm building a registry of typescript servers here: https://github.com/wegotdocs/open-mcp
5. 5.▲
   by dan-kwiat 1y 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
6. 6.▲
   by dan-kwiat 1y 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..)
7. 7.▲
   I'm Booking You(meeting-scheduler.vercel.app)

   1 points by dan-kwiat 5y ago|0 comments
8. 8.▲
   by dan-kwiat 8y 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