https://marketplace.visualstudio.com/items?itemName=Speakeasy.debugger-mcp
A VS Code extension that exposes an MCP (Model Context Protocol) server, allowing AI agents like Claude Code and Claude Desktop to control VS Code's debugger. Language-agnostic — works with any debug adapter (Node.js, Python, C++, Go, Rust, Java, etc.).
We built this because we found existing Go libraries struggled with the "sharp edges" of OpenAPI—specifically dynamic types (polymorphic fields) and complex reference architectures (circular refs/remote files).
This library uses Go generics to maintain strict type safety without losing flexibility and includes native support for the new Arazzo (workflows) and Overlay specifications.
Code is here: https://github.com/speakeasy-api/openapi
https://github.com/speakeasy-api/openapi
At Speakeasy, we spend a lot of time working with OpenAPI specs, and we kept running into the same issues: existing parsers are either too rigid, incomplete, or don’t provide the foundations needed to build tools on top of OpenAPI.So we built our own: speakeasy-api/openapi.This is a fully open-source library for parsing, validating, and working with OpenAPI specifications. It’s written in Go...
https://www.speakeasyapi.dev/openapi
Hey HN! I work at Speakeasy building SDK generation and general API tooling. As part of our work, we’ve been helping a lot of companies improve the overall quality of their OpenAPI documents. As popular as OpenAPI is, there is a shocking lack of good information for developers who are trying to learn how to effectively work with the standard.To fix that, we have put together the full OpenAPI...
Most of this telemetry either went to Datadog or Prometheus but we could also have them go to a central location that allowed us to build reports on usage and what all our integrations were.
Then we got all the tracking you mentioned for free whenever we implemented a new API. The initial lift was always a bit longer but very much worth it in the end