Before you delete, disable, or reconfigure an MCP server, the confirmation now shows who's actively connected and when they last used it, so a routine change doesn't quietly cut someone off. Setting one up got clearer too: Platform MCP's setup banner and catalog card now name the exact step left instead of a generic "Finish setup." More on this in MCP Catalog and Tool Logs.

Features

• See who's connected before a breaking MCP server change #8432 - Deleting a server, turning it off, changing its sign-in, removing its upstream authorization server, or changing one of its addresses now shows a confirmation listing who holds an active connection and when each one last used it, with shared sign-ins called out, before you commit. (Author: @chase-crumbaugh)
• Setup banners and the catalog card name the exact step left #8676 #8607 - The Platform MCP card's setup link, and a banner on the MCP server's settings page, now say precisely what's left: add an API key, set up the OAuth client your team signs in with, or just sign in. Once it's done, the banner says the server is ready to use instead of always saying "Finish setup." (Author: @adaam2)
• Tool names read in plain language in Codex and other clients #8595 - MCP clients such as Codex now show plain-language titles for tool search, tool details, run, and code-mode tools, for catalog tools that used to say "Reviewed," and for the feedback tool, instead of raw internal names. The underlying tool names are unchanged. (Author: @adaam2)
• Gateway instructions tell an agent what it can reach before it searches #8654 - Gateway instructions now open with one line naming the servers the caller can use, so agents that load tools on demand, such as Codex, know what the gateway reaches up front. The line stays under 250 characters and ends with a count when servers don't fit; gateways with their own custom instructions keep them as written. (Author: @daviddanialy)
• Tool Logs names and links the real gateway behind a call #8565 #8608 - A tool call that reached an agent gateway or the organization gateway now shows that gateway's actual name and links to its own page (the agent's Permissions tab, or the Organization Gateway page) instead of a raw ID or a stored-gateway page with nothing on it. Tool Logs now names every gateway a call went through, including ones in other projects. (Author: @mfbx9da4)
• MCP client names can be forwarded to the provider, opt-in #8629 #8628 - Remote session clients can now send the connecting MCP client's self-reported name to the provider as speakeasy_client_name during authorization. It's off by default, and only sent for anonymous sessions. (Author: @daviddanialy)

Bug fixes

• Inspect now lists every tool, including ones you can't use #8600 - The Inspect tab now shows a server's whole tool catalog, split into Available and "Not available," instead of silently filtering to only what your own access includes. Viewing or syncing the tab no longer adds or removes recorded tools based on one person's access. (Author: @danielkov)
• Tool-blocking policies now cover tools the platform hasn't seen yet #8599 - Rules that block MCP tools by type, like "block destructive tools," now apply to tools on remote MCP servers that haven't been recorded yet, instead of depending on someone first opening the server in the dashboard. A call is refused if the tool can't be checked. (Author: @danielkov)
• Large tool inventories get a clear size error instead of a retry loop #8673 - Consent capture, gateway serving, explicit selections, and related paths now share one 10,000-tool budget. An inventory over that limit shows an actionable administrator-facing error instead of asking you to retry. (Author: @adaam2)
• OpenClaw calls through a gateway are classified correctly #8585 #8569 - OpenClaw's MCP tool calls now show as Shadow MCP calls in Tool Logs, named after the server they reached, instead of as local tools; and calls that actually reached a Speakeasy gateway now show as Gateway calls instead of Shadow MCP calls, so a gateway named "speakeasy" no longer looks like an unrelated third-party server. (Author: @mfbx9da4)
• OpenClaw and Kit prompt events no longer inflate tool-call counts #8559 - Prompt and session events from hook-based agents such as OpenClaw and Kit no longer count as tool calls, including rows stored before this change. (Author: @mfbx9da4)
• OpenClaw cron sessions get a readable title #8561 - OpenClaw cron sessions are now titled "Cron: <job name>" instead of showing the raw cron envelope, including sessions stored before this change. (Author: @mfbx9da4)
• Failed gateway tool calls are now logged, with clearer errors #8558 - Gateway tool calls that fail before dispatch now write a failed tool call row instead of disappearing from the log, and functions that fail with unset environment variables now say which ones are missing. (Author: @mfbx9da4)
• Platform tools work when called through a gateway #8545 - Platform tools such as Slack now run when an agent or organization gateway calls them through execute_tool, instead of failing with "platform tool requires project auth context." (Author: @mfbx9da4)