I’ve written and talked extensively about Hypermedia APIs for about a decade. The HATEOAS constraints in representing resources for a RESTful API has numerous advantages in API design, readability, discoverability, and performance over a hand-rolled REST API. Unfortunately, adoption of Hypermedia APIs is very low compared to, for example GraphQL, but I find the implementation a lot simpler and continue adding Hypermedia APIs to my pet projects.

The RubyLA blog offers insights, tutorials, and community updates for Ruby developers in Los Angeles and beyond. Developers can explore Ruby language features, web development frameworks, and best practices for building Ruby applications. Additionally, the blog covers Ruby meetups, events, and job opportunities in the Los Angeles area, fostering collaboration and networking within the local Ruby community.

RUBYLAND

Demonstrates how to convert Hypermedia APIs into Model Context Protocol (MCP) servers using a new Ruby gem called hyperclient-mcp. The approach leverages the self-documenting nature of HATEOAS-compliant APIs to automatically generate MCP resources, enabling AI assistants like Claude to interact with any Hypermedia API without custom client code. Includes practical examples using a Slack bot API and step-by-step instructions for setting up the MCP server.

Turning Hypermedia APIs into MCPs