The APIs.io network ingests blog posts from every API-bearing provider it indexes. Last week (Apr 26 → May 3) the feed pulled in 2,104 posts across 884 producers, of which 178 carried API-relevant signals in the title — APIs, SDKs, MCP, OAuth, GraphQL, webhooks, integrations, and the like. Here’s what stood out, grouped by what producers are actually shipping right now.
MCP servers, everywhere
The single loudest theme of the week was MCP. Eight different providers published MCP-related stories, and the pattern is consistent across categories — companies that already had a developer surface are now publishing MCP servers as a parallel access path.
HubSpot walked through building a Notion database via the HubSpot Dev MCP and Claude Code. Optimizely shipped a remote MCP server for experimentation tooling. n8n released an MCP server that builds and updates workflows. Port added the ability to connect external MCP servers into the developer platform. SigNoz shipped one for observability data. SoftwareSuggest covered the secure-MCP-for-test-data pattern. Document360 wrote about MCP server analytics. Naftiko framed the broader pattern — three capabilities (discovery, reusability, governance) on a single MCP surface for Claude and Copilot.
The provocative entry in this cluster was Naftiko’s piece on capability YAML vs x-mcp extensions, arguing that vendor extensions to OpenAPI aren’t the right shape for describing MCP surfaces and that a separate capability spec is.
API security and operations
Zuplo’s recap of Akamai’s 2026 API Security Survey was the headline number: 87% incident rate across the surveyed population. The survey is one of the most-cited industry datasets for API risk and a useful reference for budget conversations.
Truto published a practical piece on automating API key rotation and secret management at scale, plus a companion piece on declarative APIs for systems integrators. They also rolled out Slack and email alerts for SaaS API integration monitoring and agent skills designed to stop hallucinations during integration work.
On the cloud security side, AWS shipped VPC endpoint policy enforcement for IAM Roles Anywhere CreateSession, syndicated across 42 AWS service repos in the catalog — a useful signal for anyone running cross-account workload identity.
Agent skills as a developer surface
Banuba led the week’s headlines with a piece on shipping Agent Skills for their Video Editor and Photo Editor SDKs — a concrete example of a media SDK vendor packaging skills as part of the developer onboarding path. Truto’s agent skills post covered the same shape from the integration-platform side.
The trend underneath both is that “developer documentation” is fragmenting into a stack: REST docs, MCP servers, and agent skills all targeting different consumers (humans, agent runtimes, and IDE-resident assistants).
API management and integration platforms
Microsoft was named a Leader in the IDC MarketScape: Worldwide API Management 2026 Vendor Assessment — the most-syndicated story of the week, appearing across 32 Azure-related repos in the catalog.
Nango published a comparison of API integration platforms specifically for use with Claude Code, Cursor, and Codex — a sign that “best integration platform” reviews are now segmented by AI tooling rather than just by destination SaaS.
Naftiko continued profiling enterprise API management vendors, publishing capability profiles for Axway and Azure API Management.
API design, types, and developer experience
Fern published a 2026 guide to the different types of APIs — REST, GraphQL, gRPC, AsyncAPI, webhooks — a useful entry-point article for the period.
Microsoft .NET covered combining API versioning with OpenAPI in .NET 10. Vonage shipped a Laravel + API Platform tutorial. Appwrite announced the Variables API for managing function, site, and project variables from server SDKs.
Unified.to wrote a clean explainer on webhook vs API decisions — useful context alongside the AsyncAPI search post we published yesterday — and a NetSuite-specific integration guide.
Developer ecosystem updates
Adobe relaunched its developer blog, syndicated across 9 Adobe-product repos. Google Chrome expanded developer dashboard roles. Microsoft shipped the April release of Azure Developer CLI.
The developer-philosophy entry of the week came from Slashdot’s “The Case Against an Imminent Software Developer Apocalypse” — a useful counterweight to the AI-replaces-developers framing that runs through a lot of the rest of the week’s coverage.
What the week tells us
The signal-to-noise from 2,104 posts is consistent: producers are publishing about MCP servers, agent skills, integration tooling adapted for AI assistants, and the operational surface around all of it (security, secret rotation, monitoring). The traditional REST-API design content is still there — versioning, types of APIs, framework tutorials — but it’s now sitting alongside an MCP / agent-skills layer that didn’t exist a year ago.
That’s the shape of API-producer media right now: every category is being repackaged for an agent-consumer audience, and the producers writing about that transition (Naftiko, Truto, HubSpot, Optimizely, Port, n8n) are the ones generating the most signal in the feed.