Skip to content

server@2.35.0

Choose a tag to compare

@gram-bot gram-bot released this 17 Nov 04:12
· 207 commits to main since this release
2ecf52e

Minor Changes

  • 8d58f27: Org admins can send a test event to any data export's destination, from the management API (dataExports.testRoute) or the Platform MCP (send_data_export_test_event). Speakeasy sends the test straight to the destination and says in plain words whether it was accepted, refused, not found, or could not be reached. Tool call logs, risk findings and MCP connection logs send one test log. Product telemetry sends one test log, one trace and one metric, and the answer lists each one.

    Test events are easy to filter out. Every test log, span and metric data point, and every request's resource, carries speakeasy.test_event=true. The test log and span also carry a speakeasy.test_event_id that is the same for every signal in one test; the metric does not, so tests add no metric time series. Every test log is named speakeasy.test_event and its message starts with "Speakeasy test event:". Speakeasy drops speakeasy.test_event and speakeasy.test_event_id from data it receives, so only tests carry them. To filter tests out, filter on speakeasy.test_event=true, not on the name or message: real data can use those too. A product telemetry test adds one span under service speakeasy and one metric named speakeasy.test_event to your destination.

    Each export can send 5 tests a minute, and each organization 20 across all its exports. If Speakeasy can't check these limits, it sends nothing and asks you to try again shortly. Each test, with its test event ID, is recorded in the audit log.

  • a4d94ce: MCP connection log exports set to "Warnings and errors" or "Info, warnings and errors" now also send failed sign-in steps that may still recover, such as a saved sign-in the service no longer accepts. They arrive as warnings with speakeasy.mcp_connection.final=false. Normal sign-in steps are not sent. Exports set to "Errors only" are unchanged.

  • eae71eb: Admins can mark an MCP server's upstream setup guide as done with the new mcpServers.setSetupGuideCompleted endpoint. MCP servers now report setup_guide_completed_at, shared by everyone in the project.

  • 23721bd: Platform MCP tools now identify MCP servers by mcp_id and projects by project_slug, as list_projects returns it, instead of accepting project IDs. This includes list_gateway_sessions project scope, get_organization_gateway_activity, select_assistant_runtime and set_assistant_reasoning_effort. Write tools that take a confirmed field preview on confirmed: false: data export pause, resume and level changes and risk policy audience changes run the same checks as the confirmed call and return a preview without writing. Tool descriptions and shipped Platform MCP skills were sharpened from tool-selection eval findings.

  • 33a5bf2: Each project's MCP Servers list now leads with its Project Gateway, the Organization Gateway limited to that project's servers, in place of the Organization Gateway. The Project Gateway page shows the project's endpoint, installation steps, connections, and activity to anyone with access to the project, and carries the switch that turns gateways on or off for organization members. The Organization Gateway page now points to Project Gateways and keeps only its endpoint and switch. organizations.getProjectGateway returns the selected project's gateway URL. gatewaySessions.list and gatewaySessions.listFacets accept project_id to list one project's gateway sessions, and telemetry.getProjectGatewayOverview and telemetry.getProjectGatewayUsage replace the organization-wide gateway activity endpoints. In the Platform MCP, list_gateway_sessions gains a project scope and get_organization_gateway_activity accepts project_id.

  • c6e9a3e: An MCP Authentication Provider's page warns when the remote session clients it binds don't match the ones its MCP servers use, and shows which clients differ on each side.

    The new listRemoteSessionClientBindings endpoint is marked deprecated from the start: the remote session clients bound to a provider are no longer authoritative, and readers are moving to each MCP server's own client associations. The endpoint exists only to surface drift during that migration.

  • afa354f: Self-serve Stripe Checkout and the access-paused email after a trial ends are now on for every organization. Their rollout flag is removed. The unused usage.createCheckout endpoint, which created Polar checkout links, is removed.

  • e36428b: Remove the deprecated toolsets.setUserSessionIssuer endpoint, which reached its sunset date. Link a sign-in provider with mcpServers.update and user_session_issuer_id, and detach it with clear_user_session_issuer.

  • 2cfabd7: Hosted MCP servers are now reached only through their endpoints. An older address that only the toolset still held, with no endpoint at that slug, stops serving: /mcp/<slug> requests, its sign-in metadata, its sign-in routes and its install page return not found. Access tokens must name the server they were issued for; tokens issued for the toolset before hosted servers had endpoints are rejected, and clients sign in again. To keep an address working, add it as an endpoint on the server. Plugins include a hosted server only when it has an endpoint, and adding a toolset to a plugin needs one.

    The one-off legacy-alias-endpoints backfill is removed with the alias it read. Its audit action stays listed so the entries it recorded still display.

  • 9b16c1d: Private network ingresses can now be hosted by the tsnet-based tailnet gateway instead of the Tailscale Kubernetes operator. The networkIngress.create hostname is optional and defaults to speakeasy, so new ingresses are reachable at speakeasy.<tailnet>.ts.net.

  • 8a01941: access.createTemporaryGrant takes optional challenge_ids: each must be an unresolved denial of the same scope, raised by the grant's recipient, on a resource the grant covers, and they are resolved together with the grant in one transaction. Authorization challenges and challenge buckets carry a new temporary_grant resolution with the grant's id, status (active, expired or revoked) and end time. access.listScopes reports temporary_grantable for each permission.

Patch Changes

  • 3442a20: The data export test event ID attribute is now speakeasy.test_event_id, so destinations that nest dotted names, such as Datadog, keep speakeasy.test_event=true and filtering on it works.

  • 1150f4f: Adds the legacy-alias-endpoints operator backfill, which gives each hosted MCP server an explicit endpoint for every address its legacy toolset alias still serves, so stored client URLs keep working once the alias is removed. The backfill keeps those addresses' slugs even when they lack the organization slug prefix or exceed the 40-character hosted slug limit. Updating an MCP endpoint checks the prefix only when its address changes, so an existing unprefixed endpoint can still be saved. The dashboard's address editor shows such a slug as it is stored and adds the prefix only when the address is renamed.

    A hosted MCP server that has an endpoint on the organization's live custom domain now shows that custom-domain URL in its toolset view, its exported MCP metadata and assistant connections, the same URL plugins already use. Before, these showed the platform URL when the server also had one. The dashboard still lists a domain-root server's address in its /mcp/<slug> form, which also serves.

  • 79bc913: When Speakeasy is the company sign-in provider and won't vouch for an account (for example, the person isn't a member, was deprovisioned, or used a sign-in method the organization doesn't allow), the connect page now tells them to ask their administrator or use a separate sign-in, and connection health records it as something an admin has to fix. Company sign-ins that need renewing are now recorded on MCP requests, too.

  • fbaa46c: Fix Command K resource search failing for members whose access is enforced by roles. The search asked whether the member could list gateways without naming the project, which the authorization engine rejects, so every search returned an error and the palette fell back to loading full resource lists.

  • e60ccfb: Agent Sessions now labels a Claude Cowork session as Claude Cowork even before Claude's own telemetry reaches Speakeasy. The live hook events from Cowork carry the Cowork surface, and their messages are now stored with the same Cowork source as the session transcript.

  • a344fb5: The demo seed safety fixture no longer plants toolsets on a custom domain, ahead of dropping the toolset hosting columns.

  • 38d220e: Search authorized project resources, active organization members, and registered agent identities through one bounded request so Command K avoids cold-open inventory fan-out while preserving identity actions, access controls, and privacy-safe deterministic ranking.

  • 4608105: When a gateway server's service refuses the sign-in details saved for it, people and agents are now told what failed in plain words, whether connecting helps, and what to ask their administrator to fix.

  • a2d4e9d: Blocking a principal's view access to an MCP server now also takes away manage access, matching how blocks already work for projects, environments, skills and assistants. Blocking connect still leaves view and manage in place. The MCP access page shows the manage line as blocked when a view block covers it.

  • ce1a480: Build organization encryption in the MCP, private ingress and admin processes, and refuse to start any process that handles OAuth credentials without it outside local and test environments. Set GRAM_ORG_ENCRYPTION_DISABLED to run without it.

  • a455f85: Name the owner of a refused, already-used refresh token on its connection row, and name a gateway member's upstream host on request rows where that upstream itself failed.

    For deployers: refused used-token rows now carry a subject; member upstream failures (rejected credential, rate limited, server error, unreachable) now carry the upstream host. In daily outcomes, fix pairing and totals are unchanged; repeated refusals now fold per person.

  • d077556: Remove the external MCP fields from the API. Deployments no longer list external MCP sources, evolving a deployment ignores exclude_external_mcps, toolsets no longer carry external MCP header definitions, and the externalmcp tool type is no longer a valid tool filter. The deployment external MCP counts stay, always 0, so older clients keep working. The dashboard drops its external MCP views, warnings and OAuth auto-setup.