The API Dispatch #5: Beyond the endpoint, Upon the OpenAPI Spec, Above MCP

The July installment of a monthly ‘newsletter’ about APIs. This issue looks back on API meetup, OpenAPI Spec 3.2, and a few optimistic opinions about MCP.

Author's note

The API Dispatch is a series I started as an internal newsletter at work. It's also available on LinkedIn.

Originally published in July 2025.

In the mid-summer edition of The API Dispatch, we’ll review the June API meetup, check how to leverage GitHub Copilot for more efficient API development and also take a look at OpenAPI Spec 3.2 And I have also two pieces about greater implications of MCP as an universal plugin system, prying the platforms open.

Looking back Beyond the Endpoint

At the end of the June our awesome R&D Community team organized API meetup in the Prague office. If you didn’t make it, don’t worry: all talks have been recorded and available on YouTube:

Mews Meetup: Beyond the Endpoint (5 videos • YouTube)

AI Development Kit for Your IDE

During his talk, Matyáš also showed prompts and instructions for LLM tools in editors, particularly GitHub Copilot. These resources are available in GitHub repository, generously shared by Matyáš and DX Heroes:

DXHeroes/ai-dev-setup (GitHub)

Use it as a starting point for your LLM-enhanced API development setup!

OpenAPI Specification 3.2 is coming soon

Erik Wilde highlights the features of the next minor version of OpenAPI Specification.

Erik Wilde: OpenAPI 3.2: New Features for Query, Tags, and Multipart Support (1 min • LinkedIn)

OpenAPI 3.2 introduces built-in support for the HTTP QUERY method, enabling API designers and developers to leverage richer query capabilities natively. […]

Tags will get a powerful upgrade! The improved tag model in OpenAPI 3.2 allows for more granular categorization, flexible grouping, and richer metadata on your APIs. […]

OpenAPI 3.2 also enhances multipart support, simplifying how complex file uploads and structured multipart requests are described and validated.

You can also follow the v3.2.0 milestone on GitHub.

Will your toaster start taking phone calls thanks to MCP?

You surely heard about Model Context Protocol (and if not, I’ve covered it in The API Dispatch #2) and how it allows for connecting of AI models to the outside world. But it doesn’t have to be just for AI right? That’s what Scott Werner argues: similar to how HTTP, Bluetooth, and USB expanded way beyond their original use cases, MCP has a potential to become a universal plugin ecosystem.

MCP: An (Accidentally) Universal Plugin System (4 mins • Substack)

USB-C [is] special because it's a possibility space. It's a hole that says "put something here and we'll figure it out." […]

MCP is the same thing but for functionality. It's not saying "I'm for AI." It's saying "I'm a well-designed hole. Put something here."

MCP is bringing the optimism of Web 2.0 back

And in a similar vein, Anil Dash notices that MCP is bringing back the openness and interoperability last experienced during the era of Web 2.0. Not Facebook-style social media (which actually killed Web 2.0), but interoperability through standardized protocols and formats, pushing the web to its natural, decentralized, programmable state.

MCP is the coming of Web 2.0 2.0 (6 mins • Anil Dash)

The rise of MCP gives hope that the popularity of AI amongst coders might pry open all these other platforms to make them programmable for any purpose, not just so that LLMs can control them.