OpenAPI 🤝 OpenMCP

Will OpenMCP be the hero we need to bring existing standards together with a nascent protocol? Also: DELETE -> HTTP204, gRPC in Node.js, php-node, and JSON Schema Tooling.

OpenAPI 🤝 OpenMCP

For the last two months, my feeds have been awash with API and MCP content.

The relentless tidal wave became a little boring until something caught my eye. Say hello to OpenMCP. First, their example makes converting any OpenAPI documents into an MCP server easy. However, what excites me is the push for best practices and focusing on the challenges that MCP servers can face, such as scaling and authorization.

-- Alexander

Help shape the future of APIs

Take the Survey

The API Round-Up

API News, links, and tools from around the web

HTTP 204 Is the Best DELETE Response

The best DELETE response is not 200. Bruno Pedro talks about why he thinks 204 is the best response type for a DELETE endpoint. Bruno also shared some of the feedback he got from his socials on the idea. Funny, my go-to is to send back a 200 with the body containing the resource you deleted.

H3

H3 came up in my feed this week, and I immediately found myself diving into their docs. It is a server framework built on web standards, focusing on performance and composability. H3 is runtime agnostic, so it will work the same across Deno, Bun, and Node. They recently had a new release with some interesting inclusions. Check out the release blog for more info.

Node and PHP Together at Last

A new package called php-node allows you to run PHP inside a Node.js environment. Instantly route requests that need PHP processing to a PHP worker, which is then executed and delivered back to the Node.js application. Check out the blog for the full breakdown, as some interesting things are happening to make this work.

Building a gRPC Node.js API

A fantastic guide on how to build a gRPC API with Node. While also covering the basics of setting up a project and API, Salem explains how gRPC works and some of the tradeoffs. However, I disagree with the statement that REST APIs are less efficient due to HTTP overhead. Once again, I feel I should hit you with the statement that you should choose the right tool for the job, and your REST API is only as good as the level of planning/design you put in.


APIs You Won't Hate

The latest from the team at API's You Won't Hate.

API Basics: Cache-ability

Designing an API with cache-ability in mind produces a more sensible and better separated set of resources, and it just so happens to be more performant, cheaper, and better for the environment.


From our Community

Articles written and shared in our free Slack community.

JSON Schema Tooling

An interesting thread on defining JSON Schema through a DSL popped up in our Slack community last week. Jeremy shared a link to the wonderful JSON Schema Tooling page. I often forget about these lists of resources, which usually save me from building something myself. It's worth remembering they exist.

🫣 Support APIs You Won't Hate

Become a paid member to get access to members-only content while directly supporting our work. Your support helps us to keep making resources for the API community.

Become a member today

Thanks so much to our members: Kin L, Juxt, Alex R, Nolan S, Frank, James D, Rich, Ryan T, and Umair. Your support means the world to us!

✌️ Until next time,
Alexander, Phil & Mike