MCP 2026-07-28 spec: what a stateless protocol core means for agent architecture
What MCP's 2026-07-28 stateless protocol core changes for agent systems: load balancing, session handling, transports, external state, and migration work.
Tag
#API
6 matching blog articles with repeat coverage under this topic.
Tag wiki
#API is a interface design pattern used directly in these articles.
Definition
APIs (application programming interfaces) define how different software components or services communicate, typically using REST, GraphQL, or gRPC protocols.
Why it matters
It matters when building systems that integrate, scale, or allow third-party access to services.
In this archive
Here APIs show up in service integration, webhook design, third-party integrations, versioning, security, and decisions around exposing functionality programmatically. It currently appears in 6 articles and crosses 3 categories.
Nearest categories
AI Agents & LLM Apps , Automation & Integrations , Infrastructure & DevOps
Reference
Often appears with
Tool-Use Patterns for AI Agents in 2026: Function Calling vs MCP vs Custom Integrations
Compare the three dominant tool-use patterns for AI agents in 2026 — OpenAI function calling, MCP, and custom integrations — with a practical decision framework for production systems.
When Magnolia's Integration Framework Beats Custom CMS Glue Code
Magnolia's integration framework becomes valuable when teams need DAM, commerce, CRM, analytics, and optimization systems to feel like part of one publishing platform instead of a pile of custom glue code.
Why GraphQL Schema Discipline Matters More Than Resolver Count
Strong GraphQL APIs come from a durable schema and business logic layer, not from exposing every database relation.
How to Design an OpenAPI and OAuth 2.0 Integration Layer
OpenAPI and OAuth 2.0 work best together when the integration layer is documented, testable, and clear about permissions.
Why GraphQL Still Matters for API-First and Headless Apps
GraphQL is still useful when multiple clients need one flexible API with strong types, fewer round trips, and predictable schemas.