Skip to main content

​
Overview

This changelog tracks all notable changes to MCPJam Inspector. We follow Semantic Versioning and keep our changelog in the spirit of Keep a Changelog.

​
Latest Releases

​
2026-09-16

​
Changed

  • Swarm run detail now has a Run tab with the live persona × client matrix — opening a swarm run at /swarms/:id while a wave is in progress lands on a new Run tab that shows the same persona × client matrix and session stream previously only visible in the create wizard. The tab stays reachable via ?tab=run after the wave settles, so you can always return to the matrix. A still-running wave with no explicit ?tab= opens Run automatically; a finished wave still defaults to Findings.
  • Settled outcome moved to the header; the separate Complete strip is gone — once a wave finishes, the outcome chip (Complete / Stopped / Failed) and the session tally (N of N) appear in the header row before the Share button instead of on a second status bar below the tabs. The tab strip is no longer obscured by the strip on narrow viewports.
  • ?tab= is always present in the URL — navigating to any tab, including Findings, now writes ?tab=findings (or ?tab=run, ?tab=insights, ?tab=sessions) to the URL. Share links copied from the run detail page include the active tab.

​
2026-09-15

​
Changed

  • Session transcripts now match the Playground’s visual style — session transcripts (User Testing, Swarm, Scenarios) no longer show a generic chat-bubble icon in front of every assistant response, matching the Playground renderer which has never drawn one. JSON payloads in session transcripts are now syntax-highlighted with the same colors the Playground uses — keys, strings, numbers, booleans, and null each get a distinct color. Plain text, stack traces, and payloads over 100 KB render as uncolored monospace. Both changes apply wherever a session transcript appears; no configuration is required.
  • Sessions now shows tool payloads in the Playground’s collapsible JSON tree — tool input and output in session transcripts (User Testing, Swarm, cross-surface Sessions) are now displayed in the same interactive tree the Playground uses, instead of a plain preformatted block. Objects and arrays collapse, deep payloads open two levels and stop, long strings truncate with a control to see the rest, and every node has its own copy button — so pulling one id out of a tool result is a click rather than a select-and-trim.
  • Session tool cards now match the Playground’s card shell — a session transcript was showing tool calls differently from the Playground tab. The card in sessions now has the same header row (MCP mark, mono tool name, call state, chevron), and the same INPUT / RESULT headings over capped payload boxes. The whole card collapses and starts collapsed, so a transcript reads as a conversation rather than a wall of JSON. A failed call opens itself automatically — an error is the reason you opened the session, not something to put behind a disclosure.
  • Raw tab scroll edges fade like the Chat tab in User Testing — the Raw pane in a User Testing session detail now softens its top and bottom edges as you scroll, matching the Chat tab’s behavior. A hard edge that cuts a line mid-token no longer reads as a rendering glitch.
  • Detail-page back button is a raised control — the back link on User Testing study detail and Swarm run detail pages is now a raised pill button (h-8, rounded-lg) matching the Edit and Open preview controls on the same row. On hover the arrow glides toward the left and the label darkens.

​
2026-09-14

​
Changed

  • Selecting a stage in Findings now opens that stage’s sessions — on the Findings tab, clicking a stage in the user value chain (Connection → Discovery → Selection → Call → Response → Value) narrows the session list to the sessions that stage is actually about. A passing stage shows the sessions that passed there; a failing or warning stage shows the sessions that failed there. A stage with no verdict leaves the full goal list in place — narrowing there would show an empty list under a header that says the stage was never graded, which would read as “no sessions” rather than “not measured”. The persona’s sentiment filter and the hide-synthetic policy remain active alongside the stage filter, so the narrowed list stays consistent with the count that opened it.

​
2026-09-11

​
Added

  • “Back to study” exit on the scenario preview surface — when you open a User Testing scenario preview via Open preview, the chat header now shows a Back to study button beside Copy link. Clicking it returns you to the study detail page. The consent dialog’s Leave button on the preview surface also navigates back to the study instead of showing the “You left this session” panel. Share-link visitors are unaffected: they see no Back to study button, and Leave still shows the terminal panel with Rejoin.

​
2026-09-09

​
Added

  • Findings tab on User Testing scenario detail — opening a User Testing scenario now lands on a Findings tab instead of Insights. The tab groups sessions by how users came across — Gave up, Frustrated, Neutral, Satisfied, or Uncategorized — and lists the goal clusters each group engaged with, ordered worst-first. Expanding a goal shows the per-goal user-value chain (Connection → Discovery → Selection → Call → Response → Value) once stage data is available. Click any goal’s session count to jump to Sessions with the matching transcript pre-selected. Insights and Sessions remain reachable from the tab strip.

​
Changed

  • User Testing scenarios analyze themselves — opening a User Testing scenario’s Findings or Insights tab when sessions exist but no analysis has run now starts the analysis automatically. The “Analyze sessions” button and the “These sessions haven’t been analyzed yet” state are gone; the tab shows an analyzing banner instead and fills in once the run completes. The cluster tuning control and the freshness chip still require an explicit action. Swarm and Benchmark scopes are unchanged — Swarm already queues analysis when a run settles, and Benchmark flow analysis remains explicitly requested.

​
2026-09-02

​
Added

  • GPT-5.6 models available with your own OpenAI key — gpt-5.6-luna, gpt-5.6-sol, and gpt-5.6-terra are now selectable in the model picker under Your providers → OpenAI when you have an OpenAI API key configured. Each model has a 1,050,000-token context window. These models were already available in the free hosted catalog; this change makes them reachable for BYOK users as well.

​
2026-08-31

​
Changed

  • Public score runner redesign — the score runner landing page has been rebuilt with a new design. After you paste a public MCP server URL and click Score this server, you are now prompted for an email address before the scan starts. The scorecard is delivered to that address once the run completes. The email is preserved across OAuth redirects, so servers that require authorization before scanning still collect it. Legacy OAuth resume records that predate the email step are kept on the email prompt rather than bypassing it. The featured scores section on the landing page now shows real MCP endpoints (Linear, GitHub Copilot, Notion), and each row populates the URL field when clicked. URL examples default to Streamable HTTP at /mcp.

​
2026-06-26

​
Added

  • Compatibility destination — a new Inspector page that evaluates your connected MCP server against a catalog of AI hosts (Claude, ChatGPT, Cursor, Copilot, Codex, and others). Shows conformance gates, per-host findings split into Apps and Server lanes, and live widget rendering. Accessible from the left sidebar when a server is connected.
  • OTLP/OpenInference trace export — export eval run traces as OTLP JSON from the run detail page. Compatible with Arize Phoenix, Datadog, and any OTLP-compatible observability backend. Supports exporting a single run or the whole project, with an opt-in to include content and artifacts.
  • @mcpjam/sdk/host-compat subpackage — the shared host-compatibility engine is now importable directly. Use deriveServerRequirements, evaluateHostCompat, evaluateAllHosts, scanWidgetSource, and detectHostCompatBridgeFromMeta to build your own compatibility checks in CI or custom tooling.

​
Version 1.1.0

​
Improved

  • Code Quality
    • Improved code consistency and maintainability

​
Recent Updates

​
Added

  • VS Code and Notion market hosts (@mcpjam/sdk minor)
    • VS Code (GitHub Copilot chat panel) is now a market host in the SDK’s host-compat catalog. It renders MCP UI inline and supports all display modes (inline, fullscreen, pip). Capabilities mirror the VS Code client template; updateModelContext and message are not advertised. Provenance: probe.
    • Notion is now a market host. It is a tools-only/headless client (no widget rendering) that supports protocol version 2025-11-25. Provenance: probe.
    • Both hosts are available via buildMarketHostProfiles() / evaluateMarketHosts() and carry logos in the inspector’s host-compat UI.
  • imageSupport dimension on all market hosts (@mcpjam/sdk minor)
    • Every market host now carries an imageSupport field on its HostCompatProfile describing how it handles MCP tool-result images.
    • Three image sources are tracked per host: toolImageContent (direct MCP image blocks), embeddedResourceImages (image blobs inside MCP resources), and resourceLinkImages (image links resolved via resources/read).
    • Each source records model (whether the image is passed to the model) and ui (whether the host UI renders it).
    • A single placement value ("inline" | "collapsed" | "none") describes where rendered previews appear in the host UI.
    • New exported types: HostImageSupport, ImageSourceSupport, ImagePlacement from @mcpjam/sdk/host-compat.
    • New capability matrix: MCP_APPS_VSCODE exported from @mcpjam/sdk/host-compat.

​
Changed

  • Stateless MCP protocol version updated to 2026-07-28 RC
    • The stateless transport protocol version has been updated from the retired DRAFT-2026-v1 placeholder to the upstream RC literal 2026-07-28, matching the canonical pin in modelcontextprotocol/main.
    • The protocol version picker in the inspector UI now shows Latest (2025-11-25) and 2026 RC (2026-07-28) instead of “Latest” and “Draft”.
    • The SDK constant STATELESS_DRAFT_2026_V1 has been renamed to LATEST_STATELESS_PROTOCOL_VERSION and now equals "2026-07-28".
    • Migration required: If you had servers pinned to DRAFT-2026-v1, you must re-select the protocol version in the inspector UI. Stored DRAFT-2026-v1 pins are rejected by spec-conforming servers with a -32004 UnsupportedProtocolVersionError.

​
Added

  • OAuth Protocol 2025-03-26 Support
    • Added support for original MCP OAuth specification (2025-03-26)
    • Direct RFC8414 discovery from MCP server base URL with fallback endpoints
    • PKCE required for all clients
    • DCR and pre-registered client registration strategies
  • OAuth Debugger Enhancements
    • Edit Config button to modify server settings without reconnecting
    • Copy logs feature with guide and raw formats for debugging
    • Deprecated transport detection with migration guidance for HTTP+SSE servers
    • RFC 8707 compliant resource URL canonicalization
  • GPT-5 Model Support
    • Added support for GPT-5 model variants: gpt-5, gpt-5-mini, gpt-5-nano, gpt-5-chat-latest, gpt-5-pro, gpt-5-codex
    • Organization verification notice for GPT-5 access

​
Improved

  • OAuth Flow
    • Refined diagram focusing and zoom behavior for better step visualization
    • Improved error handling for expected 4xx responses during transport detection
    • Enhanced header merging in OAuth state machines across all protocol versions
  • Error Handling
    • Enhanced streaming error handling in chat interface
    • Errors now display as inline alerts instead of failing silently
    • Better error messages from AI providers

​
Version 1.0.0

​
Added

  • MCP Server Connection Management
    • Support for STDIO, SSE, and Streamable HTTP transports
    • Multi-server connection support
    • Real-time connection status monitoring
  • LLM Playground
    • OpenAI integration (GPT-3.5/4)
    • Anthropic Claude integration (Claude 2/3)
    • DeepSeek AI support (DeepSeek R1)
    • Ollama local model compatibility
    • Interactive chat interface with streaming responses
  • Tools & Resources Testing
    • Tool execution and validation
    • Resource schema verification
    • Prompt testing interface
    • Real-time parameter validation
  • OAuth 2.0 Testing
    • Guided OAuth flow setup
    • Token management
    • Scope verification
    • Refresh token handling
  • MCP Evals
    • Automated compliance testing
    • Custom evaluation framework
    • Test result reporting
    • Performance benchmarking
  • Developer Tools
    • Comprehensive logging system
    • Request/response tracing
    • Error reporting and analysis
    • Performance monitoring

​
Improved

  • Enhanced UI/UX with modern design
  • Better error messages and debugging support
  • Optimized performance for large MCP responses
  • Improved documentation and examples

​
Fixed

  • Various bug fixes and stability improvements
  • Memory leak fixes in long-running sessions
  • Edge cases in MCP protocol handling

​
Coming Soon

We’re working on:
  • Enhanced evaluation templates
  • More LLM provider integrations
  • Advanced debugging tools
  • Performance analytics dashboard

​
Stay Updated

​
Reporting Issues

Found a bug or have a feature request? Please open an issue on GitHub.