We literally just did something like this on Gram, not exactly what you're saying, but it's pretty close... https://www.speakeasy.com/blog/how-we-reduced-token-usage-by...

We have a platform (Gram) which is serverless MCP. Now users can launch MCP servers that only have 3 tools, search, describe, execute. Gram handles the tool routing, and execution (acting sort of like the sandbox). So the client only ever needs to know about those three tools. Everything else is abstracted.

This is an interesting approach and I just saw your post on reddit too, good stuff!

If you want a lightweight API docs replacement, I'd recommend Scalar. Simple and easy to use, but so much better than Swagger docs...

Caveat that I work for Speakeasy, but there are a few tools you can look at:

- Speakeasy

- Fern

- Stainless

First SDK with Speakeasy is free and we also have discounts for companies who are just starting out.

Feel free to shoot me an email if we can be useful: nolan@spakeasy.com :)

Typo in your email btw

I'd like to say this was a clever ruse so that real people could reach me and bots wouldn't, but that'd be a lie. I just fat fingered it.

Hi, I work at Speakeasy. Thanks for this. I'll look into this and correct the post. Thanks :)

Also "Multi-project runner" is supported, Vitest has workspaces feature.

Code-first or spec first, doesn't matter. Everything you need to figure out how to write an OpenAPI spec.

Anotha one

There's a lot of new companies that have started to address this issue. One of which I work at: https://www.speakeasy.com/

I genuinely think that the quality is beyond what exists in the GraphQl ecosystem.

I'm so excited to get 1.0 integrated on the site!

Hi all! we wrote this post a couple weeks ago. The TL;DR is that we recently built an API Key authorization flow that can integrate into any API provider's Gateway and makes it trivially easy for them to provide their users self-service API key management: https://speakeasyapi.dev/docs/product-reference/speakeasy-pl...

To get that working we first evaluated every commonly-used auth method before deciding on a fairly unique approach, Signed Tokens as API Keys, but with 1 Signing Key Per API key.

Happy to answer any questions people have about this novel approach, or anything API auth related. If anyone wants to try out the tool here's the sign up for the waitlist: https://speakeasyapi.dev/request-access/

Threw together a Python SDK: https://github.com/speakeasy-sdks/rows-python-sdk :) Hope it helps, and let me know what you think!