May 2026 Summaries

MCP Night: Agent Mode, organized by WorkOS and attended by AI industry leaders, highlighted the rapid evolution of AI technologies and their integration into consumer and business applications. The event focused on the increasing role of AI agents in decision-making processes, as evidenced by the launch of auth.md, a WorkOS product that standardizes service registration for agents. The night featured lightning demos, such as Rys's tool executor, and a panel discussion with industry leaders like Brendan Irvine-Broque, Claire Vo, and David Cramer, who explored the implications of agents as decision-makers. The event emphasized the San Francisco area's significant role in AI development and concluded with an engaging afterparty, fostering community connections. Attendees were also invited to future tech events, including NY Tech Week, to continue exploring developments in AI and agent technologies.

Postman has introduced several new features aimed at enhancing the API lifecycle, including first-class support for AsyncAPI 3.0, which is crucial for event-driven systems using technologies like Kafka, MQTT, and WebSockets. The update allows users to create, validate, and manage AsyncAPI 3.0 specifications with ease, providing a unified editing and preview experience similar to OpenAPI. Additionally, a centralized diagnostics pane now consolidates validation issues across open API specifications, enabling more efficient error management. Users can also move API specifications between workspaces, simplifying reorganization without duplication. A new live streaming feature for CLI performance runs allows real-time monitoring of API tests, reducing wasted time in CI/CD pipelines by providing immediate feedback on performance issues. The Postman CLI can act as an automated quality gate, enforcing performance thresholds to prevent regressions from reaching production. For enterprise teams, service accounts provide a secure, non-human identity for automation and system interactions, mitigating risks associated with personal API keys. Collectively, these updates demonstrate Postman's focus on improving feedback loops, protocol coverage, and automation infrastructure, particularly in hybrid architectures combining REST and event-driven services.

Testing modern applications requires a comprehensive approach that encompasses both frontend UI interactions and backend API validations. The integration of Postman's Application Inventory feature with Playwright UI tests addresses a common issue where UI tests may pass despite API contract breaches, or API tests succeed while the frontend miscalls endpoints. This workflow is exemplified with a user permissions management app using a React/JavaScript frontend and REST APIs to handle CRUD operations for permissions. Postman's Agent Mode automatically generates Playwright tests from frontend code, ensuring alignment between UI tests and API contracts. The process involves initializing with Postman CLI, running tests that combine UI testing with API validation, and utilizing Application Inventory for a holistic view, capturing real-time API calls and validating them against documented specifications. This integrated method reveals discrepancies such as contract drift, silent backend errors, and missing API coverage, ultimately enhancing the reliability and realism of testing by validating the complete user journey from browser interactions to backend responses.

Postman's latest release significantly enhances its platform by introducing features such as Git integration, Local Mocks, an embedded terminal, multi-protocol support in a single collection, and an AI assistant with repository context, transforming it into a comprehensive local development environment. By using the Intergalactic Banking API as a practical example, users can set up a Git-backed workspace, run Local Mocks offline, generate tests using Agent Mode, and execute a multi-protocol collection in continuous integration (CI). The platform's Unified Workbench consolidates collections, environments, API specs, and mock servers into a single customizable sidebar, reducing the need for panel switching during API development. Local Mocks allow developers to define expected responses and iterate offline, facilitating an efficient development process without reliance on live servers. The embedded terminal streamlines Git workflow and debugging within Postman, while the ability to handle REST, WebSocket, and gRPC requests in the same collection enables comprehensive end-to-end testing. Overall, Postman integrates these tools into a cohesive development loop, minimizing the need for multiple separate tools and enhancing productivity.

The text discusses the implementation of Postman Local Mock Servers to replace third-party API calls, specifically focusing on a train booking platform's Weather service that uses the OpenWeather API. By creating a local mock of the OpenWeather API, developers can avoid rate limits and costs associated with the API's usage, while ensuring consistent test scenarios, such as triggering a travel warning for snow in Edinburgh. The mock setup involves capturing real API requests using Postman, creating a mock that mirrors the request and response structure, and integrating it into the development environment via configuration settings. This approach not only facilitates predictable testing conditions but also enhances error handling by simulating real-world API responses like missing API keys or unknown cities. The same strategy can be applied to other services, such as payments or SMS notifications, to achieve deterministic testing outcomes without the overhead of third-party dependencies.

Automating Postman tests is crucial for ensuring the reliability of APIs, as manual testing often fails due to human error, time constraints, and oversight. By integrating Postman collections with Git repositories using Native Git, tests become a seamless part of the development workflow, versioned alongside the code they validate. This integration allows tests to be automatically executed on every change through continuous integration pipelines, such as GitHub Actions, reducing the risk of deploying broken APIs. By running tests automatically and making deployments conditional on their success, teams can prevent issues from reaching production, ensuring that APIs function as expected and enhancing the reliability of release processes.

Playwright, a popular frontend test runner, is widely used for its realistic API traffic during tests, yet many teams neglect the underlying API validation, risking undetected issues until production. To address this, Postman introduces new CLI commands and a Playwright plugin that validate APIs in tandem with Playwright's UI tests. This integration allows teams to capture and validate API traffic without altering their existing workflows, providing insights into API coverage, contract drift, and potential gaps, while filtering out irrelevant noise. The setup involves linking a GitHub repo to a Postman workspace, installing necessary tools, and configuring network capture, enabling comprehensive API validation alongside UI testing. This system not only aids in catching false positives and silent degradations but also facilitates the creation of API collections from captured traffic, helping teams build a robust API contract suite over time.

With the release of Postman API collection v1.39.0, users can now access eight new endpoints across API Catalog services and Spec Hub version tags, empowering them to programmatically query and manage their API data. The API Catalog provides a centralized view of organizational services, offering insights into analytics, compliance, and governance, while the new endpoints enable automation of these tasks. Users can list services, evaluate endpoint performance, and access compliance signals, facilitating the creation of dashboards and automation of health reports. Spec Hub's version tags allow users to manage API specifications by creating immutable snapshots, comparable to Git tags, which aid in tracking changes and ensuring integration stability. This update bridges the gap between Postman's dashboard capabilities and automation potential, aligning with API-first development workflows by enabling tagging at each release and programmatic comparisons to catch changes before production deployment.

Postman demonstrates a strong commitment to ensuring HIPAA compliance by continuously testing and enhancing its security measures to protect customer data while minimizing friction for users. Historically, Postman required customers to implement Advanced Security Administration (ASA) features like Bring Your Own Key (BYOK) encryption, which posed challenges for customers not using AWS environments. However, advancements in Postman's baseline security controls now independently satisfy HIPAA's technical safeguards, eliminating the need for mandatory ASA features, though BYOK remains available for those who prefer managing their encryption keys. The company dedicated approximately 700 hours over a year to thoroughly examine data movement within its platform, validate controls, and enhance data protection measures such as encryption, access control, and data classification, thereby ensuring robust protection of sensitive information. Postman continues to innovate by investing in stronger security controls and governance practices, particularly as it explores new areas like AI, and encourages potential healthcare customers to engage with its Trust Center for further information.

At the API Days Singapore event, over 150 developers gathered to explore innovative API practices through a workshop centered around the Artemis Mission Control API, which simulated a complex lunar mission system. The workshop highlighted the transformative potential of Postman's Agent Mode and Model Context Protocol (MCP), which allow users to automate API workflows using natural language instructions, thereby minimizing manual intervention and maximizing efficiency. Participants experienced firsthand how these features enable seamless creation of scripts, environment setups, and visualizations, shifting API testing from manual scripting to automated processes driven by AI. The session underscored an inflection point in API consumption, where agent-driven interactions are becoming the norm, offering significant time savings and reshaping traditional API development practices. Attendees, many of whom were seasoned Postman users, were surprised by the capabilities they had been unaware of, emphasizing the importance of awareness in leveraging advanced features within familiar tools.

The Postman MCP server revolutionizes the traditional, manual API development and testing workflow by allowing developers to perform tasks using AI agents rather than relying on the Postman UI. This server exposes Postman's full API capabilities, enabling developers to manage workspaces, collections, environments, mock servers, and monitors directly from their editor or terminal. The workflow described in the text involves using Claude Code, an AI agent, to automate the entire API lifecycle, from importing an OpenAPI spec to setting up a mock server, creating a test suite, and establishing a monitoring schedule—all without ever opening the Postman app. The server can be accessed remotely or run locally, supporting OAuth and API key authentication, facilitating a more streamlined and efficient API development process. This approach not only enhances productivity by reducing manual clicks but also supports advanced features like environment separation, automated test scripts, and continuous validation, ensuring that API-first development can progress smoothly and quickly.