APIs sind mehr als Endpunkte. Sie sind Verträge, Produkte und Integrationsflächen, die klares Design, verlässliche Implementierung, nutzbare Dokumentation und belastbare Governance über die Zeit brauchen. In diesem Bereich schreibe ich über API-First Design, Lifecycle-Management, Developer Portals, Sicherheit und operative Muster für tragfähige API-Landschaften.
Fokusbereiche
Beiträge
API Changelogs with Docusaurus
Add versioned OpenAPI snapshots, CI-based diffs, and a practical changelog flow to Docusaurus so API consumers can understand and migrate releases safely.
MCP Resources: Adding Climate Data to Your Weather Server
Extend MCP servers with Resources for read-only data. Add 30-year climate normals to the weather server, understand Resource Templates, and combine Tools + Resources for powerful AI workflows.
Publish Once or Fragment Forever? About the State of MCP Registries
From modelcontextprotocol.io's Registry Preview and Generic Registry API to GitHub, Docker, Azure, Smithery, Raycast, MCP.so, PulseMCP, and FluidMCP—what MCP registries actually do and how to choose.
AsyncAPI – Documenting Message-Driven APIs
How AsyncAPI complements OpenAPI for documenting asynchronous message-driven APIs, with a practical example, diagram, CI/testing tips, and documentation options.
OpenAPI Specification 3.2 Released – What’s New?
OpenAPI 3.2 brings path templating, new HTTP methods, streaming support, and richer documentation features.
Internal API Documentation with Docusaurus
Docusaurus is great for public developer portals, but what if you want to keep your API documentation internal?