DEV Community

Cover image for APIDOG January Feature Update: MCP Support, Test Suite and Network Details
Preecha
Preecha

Posted on

APIDOG January Feature Update: MCP Support, Test Suite and Network Details

Apidog's January 2026 release bridges traditional API engineering and the emerging AI agent economy. The two headline additions: a native MCP (Model Context Protocol) client — making Apidog one of the first platforms to offer a native debugging experience for LLM toolchains — and Test Suites for dynamic, scenario-based test orchestration. This post walks through what shipped and how to put each feature to work.

Try Apidog today

⭐ New Updates

🔥 Native MCP Client Support

The Model Context Protocol is now built directly into Apidog, creating a unified bridge between your LLM applications and external data sources. You get a native debugging environment for all three MCP pillars:

  • Tools — executable functions
  • Prompts — templates
  • Resources — data context

How to connect an MCP server:

  1. Pick a transport. Use STDIO for a local process (paste an npx command) or HTTP/SSE for a remote server. Apidog handles the handshake automatically.
  2. Paste your config. Drop in an MCP server configuration file (JSON) or a URL — Apidog parses the server name, environment variables, and connection arguments so you're running in seconds.

A typical STDIO config looks like this:

{
  "mcpServers": {
    "my-server": {
      "command": "npx",
      "args": ["-y", "@example/mcp-server"],
      "env": {
        [REDACTED CREDENTIAL]
      }
    }
  }
}
Enter fullscreen mode Exit fullscreen mode

Auth and troubleshooting:

  • Complex auth flows are supported out of the box: OAuth 2.0 auto-discovery, API Keys, and JWT Bearer [REDACTED].
  • Toggle "With Envelope" mode to inspect the raw JSON-RPC message structure when you need deep troubleshooting.

Team collaboration: configured MCP clients save to your project like any other endpoint, so the whole team debugs their agents against the same standard.

Read the MCP Client Documentation →

🚀 Scenario-Based Orchestration: Test Suites

Testing endpoints in isolation is no longer enough. Test Suites group test cases and scenarios into a single, manageable unit — with two orchestration modes:

  • Static mode (precision control): manually select specific cases to build a stable, "locked-down" verification package. Ideal for hotfixes or core business paths like "Order-Payment".
  • Dynamic mode (zero maintenance): define inclusion rules by Priority (e.g., P0), Tags, or Folder location. The suite automatically scans and pulls in matching test cases at runtime, so regression coverage always includes your latest tests — no manual updates.

Run suites wherever you need them: smoke tests locally, via CLI in your CI/CD pipeline, or as scheduled tasks for unattended production monitoring. Test Suites provide unified reporting plus granular per-run control over Environment, Error Handling, and Test Data.

Explore Test Suites →

🔬 Enterprise-Grade Visibility: Deep Network Details

When debugging endpoints, Apidog now exposes deep network details, including HTTP version (h1/h2) and TLS protocol. This protocol-level clarity is what you need for troubleshooting handshake failures, diagnosing latency issues, and verifying security configurations — so your APIs meet strict infrastructure and compliance standards.

Image

⚡️ Optimizations

  • Test Suite reordering: drag-and-drop to reorder resources within a static suite's steps, making orchestration more intuitive.
  • Collaboration links for Test Suites: copy a suite link instantly, streamlining QA ↔ developer communication.
  • Enum selection for arrays: when debugging array-type parameters, select enum values directly for child elements to reduce input errors.
  • Expanded OpenAPI support: imports now handle Query-type HTTP methods and additionalOperation for broader compatibility with diverse spec standards.

🐞 Bug Fixes

  • JSONPath action: fixed right-click context options like "Copy JSONPath" not appearing on response data, restoring rapid data extraction.
  • Security visibility: WebSocket endpoints no longer appear in public documentation when root folder visibility is set to "Internal".
  • Organization transfers: teams without a bound payment method now transfer into an organization correctly.
  • Database connectivity: MongoDB passwords containing the special character % are now parsed correctly.

🌟 Looking Ahead

The 2026 roadmap centers on unifying your development workflow for an AI-native future: deeper Git and text-mode integrations aligned with git-first habits, an architecture evolving to be seamlessly accessible by AI Agents, and continued refinement of multi-protocol support plus the core debugging and documentation tools you use every day.

💬 Join the Conversation!

  • Join the Discord community for real-time discussions.
  • Participate in the Slack community for technical deep dives.
  • Follow on X (Twitter) for the latest updates.

P.S. Explore the complete details of all these updates in the Apidog Changelog! 🚀

Happy API Building!

Top comments (0)