Repository navigation
server@2.18.0
Minor Changes
-
396924e: The MCP server Team Access tab gains a Check access section: pick an organization member to see whether they can connect to, view, and manage the server, and which rules decide it. The new
access.explainResourceAccessendpoint returns the decision from the same evaluation as runtime enforcement, naming each rule's source, whether it is blocked or overridden, and the directory role mapping behind a role for organization admins. -
0c87be8: Hosted MCP servers (
/mcp/{slug}), MCP gateways, agent gateways (/agent-mcp/{agentID}), and platform toolsets (/platform/mcp/{toolsetSlug}) now serve MCP protocol revision2026-07-28alongside the earlier revisions. A request declaring2026-07-28gets that revision's behavior:server/discoverinstead ofinitialize, spec-mandated HTTP statuses for protocol errors, and no session ids. Clients that negotiate an earlier revision atinitializesee no change. A notification declaring an unsupported protocol revision is now refused with HTTP 400 instead of being acknowledged. Platform toolset errors raised before a request is dispatched, such as a missing token or an unknown toolset, are now JSON-RPC error responses. MCP gateway responses no longer carry anMCP-Protocol-Versionheader, which no revision defines on responses. -
36a200f: Assistants have an Identity tab. An assistant without an agent identity can be set up from it, either with a new agent you name or with an existing agent of the project that you own or can authorize. The tab links to the assigned agent. Deleting an assistant withdraws its trigger workload identities and leaves its agent in place, to be managed like any other agent. The upgrade endpoint and the Platform MCP upgrade tool accept the same agent choice.
-
1a1da25: Add dedicated
assistant:readandassistant:writepermissions. Grants can cover every assistant, every assistant in selected projects, or a single assistant, and agent policies can hold them too. Admins keep full assistant access and members keep read access by default;project:*grants no longer open assistants. -
33d333c: In organizations where agent identity credentials are enabled, new assistants get their own dedicated agent, which starts with access to every MCP server and skill in the assistant's project and to administering that assistant, and can be renamed, transferred, or narrowed like any other agent. Existing assistants keep their current behaviour until an administrator explicitly upgrades them with the new upgrade endpoint or Platform MCP tool. API keys and OAuth credentials that act for a user can still create and upgrade assistants.
-
c5f5fd1: Persist Claude Tag message participants independently of session ownership, resolve them through the Slack directory, and show their session rollup. Recognize standing-owner deliveries and retain Claude Tag classification across ambiguous source reports. Persist and display parent/subagent relationships and Slack channels. Detect nonce-prefixed channel wake deliveries regardless of the reported source.
-
a51a8db: Add the
dashboardsservice: a project's layouts of saved widgets on a 12-column grid. Any member can create a dashboard, lay out its cards (each chart type has a minimum size), place or remove saved widgets, and save the date range and filters it opens on; editing or deleting someone else's needs project write access. Widgets are linked, not copied, so editing one changes it on every dashboard. Duplicating a dashboard copies its widgets into new saved widgets, so the copy is independent. Every change is audited. -
ca8de79: Keep each organization's emailed links on its own host. Invitations, setup and access request emails, trial and billing emails, weekly usage summaries, and custom domain health alerts now build their links from the organization's recorded default host instead of the site URL. Organizations with no recorded host use
GRAM_LEGACY_DEFAULT_HOST, which defaults to the site URL, so they keep their current links when the canonical host moves.GRAM_NEW_ORG_DEFAULT_HOSTrecords a default host on organizations created from now on; empty records none. The worker and admin server now also readGRAM_PLATFORM_HOSTSto re-check recorded hosts. -
53c0436: Send people to their organization's own host. When an organization's recorded default host is a different platform host from the one a login finishes on, the login callback now sends the browser on to sign in on that host, keeping the page they asked for.
auth.infoalso returnsactive_organization_dashboard_urlwhen the active organization lives on a different platform host from the request, so the dashboard can move an existing session there. Organizations without a recorded host, custom domains, private network ingress, and support or impersonation sessions are never moved. -
136ac53: Clicking a Risk Events row opens a detail drawer for every finding kind, including MCP findings. For MCP findings it shows the call path, and with chat:read the full scanned tool-call payload with each finding highlighted in place. Payload reveals are audited.
-
1cf9faa: A widget now says which dashboards it is placed on, in
widgets.list,widgets.getand the result of an update, so an edit can warn where it will reach. Deleting a widget takes it off every dashboard it was on; the dashboards stay. -
c1cef83: Widgets and Explore now use the dashboard's date presets (15 minutes to 90 days), and Explore's Window control is the dashboard's date picker. Widgets saved with "24h" still open, as "1d". A page that places widgets uses the shared filter bar, configured to show only the catalog fields it names, and every widget on it answers within that bar:
- The page's date range replaces each widget's own window, and the buckets follow it.
- Page filters are ANDed with each widget's own filters, and a card names any page filter its dataset cannot apply.
- Dragging across a time chart narrows the page.
Open in Explore shows exactly what the card showed.
Patch Changes
- 454d44b: Add Vercel Connect connectors wildcard to CIMD known clients.
- 2bc22b4: User session issuers in shared mode serve one OAuth authorization server at
/oauth/usi/{id}for all of their MCP servers. Clients name the MCP server they want with theresourceparameter, and each access token is bound to that one server. The MCP servers' protected resource metadata names the shared authorization server, while their existing per-server authorization servers keep working. Issuers in the default per-endpoint mode are unchanged. - c1ac8ef: When a remote MCP server's protected resource metadata is rejected, the recorded reason now names the resource the document claimed or the location it was read from.
- c3135eb: Add
scope_overridetoremote_protected_resources, the per-server operator pin for the scopes a login requests, andomit_scope_fallbacktoremote_session_issuers, the org-admin setting to send noscopeinstead of the authorization server's whole list. Nothing writes or reads either yet. - 5110638: Remote MCP servers now record the OAuth protected resource metadata discovered for their URL, including the scopes the resource advertises and the scopes its authorization challenges ask for.
- e93d0a1: Add the
remote_protected_resourcestable, the permanent home for a remote MCP server's RFC 9728 protected resource metadata: its advertised scopes, authorization servers, display members and the lastWWW-Authenticatescope challenge. Nothing writes to it yet. - 315511f: The Okta connection form accepts a pasted Admin Console address, and the Okta setup instructions match the current Admin Console, including each server's issuer for enabling Cross App Access.
- 12e7197: Conductor (conductor.build) joins the CIMD known-client catalog and the Shadow AI scan target list. Presets-mode issuers now admit its client_id (
https://api.conductor.build/oauth/client-metadata.json), and device agents now detect its macOS desktop app by bundle ID (com.conductor.app) and process name (conductor). - 97605ca: Standard MCP request headers (
MCP-Protocol-Version,Mcp-Method,Mcp-Name,Mcp-Param-*) are no longer read as tool environment variables, and MCP server settings and function manifests now reject variable names or header display names that would require one, such asNAMEorMETHOD. Conflicting protocol version declarations now returnHeaderMismatch(-32020) with HTTP 400. - 411442c: The MCP connect page now shows a service's catalog name and logo when the organization's own identity provider entry has none, instead of an internal identifier and no logo.
- c80569d: Publish conversation message snapshots through the transactional outbox alongside persisted messages and correlated provenance updates. The shared Pub/Sub topic supports independent downstream consumers with stable logical message identities, structured content, and asset references for large bodies.
- fa242b0: Agent-backed assistant turns can connect to MCP servers again when the acting user or the agent's owner has a role that blocks some other server. Blocking one server now removes only that server from the turn's access. Before, it removed access to every MCP server.
- cd3677d: Keep a project's plugin marketplace name stable once it has published. Renaming the organization, changing the project slug, or deleting the organization's oldest project no longer renames the marketplace, so managed settings that reference it keep installing and updating plugins. Setting a marketplace name in the dashboard still renames it, and clearing that name returns the marketplace to the default name the dashboard shows.
- 668278c: Fix the gateway "Installation page" link showing "Server Not Found". Gateways with private network access enabled now render their public install page, and a gateway on a custom domain opens its install page on the Gram host you are signed in to, with the custom-domain URL in the instructions.
- 8139c31: Let an agent create and rename projects through the Platform MCP.
create_projectmakes an empty project from a display name, deriving its slug exactly as the dashboard does, andrename_projectchanges only a project's display name, keeping its slug. Each tool is authorized as its dashboard counterpart is: creating a project requires organization administrator access, and renaming one requires write access to that project. Both require explicit confirmation and an idempotency key, so a retried creation returns the project the first call made instead of a second one. The dashboard and the Platform MCP now share one project creation path, so an agent-created project gets the same Default environment, Default plugin and audit entries, and a name with no letters or digits is refused as an invalid request instead of failing as a server error. - 19c3436: Connecting to a remote MCP server now sends its RFC 8707 resource indicator exactly as the server is registered, trailing slash included. Providers that match the resource exactly against their published RFC 9728 resource, such as one publishing
https://host/, no longer reject sign-in because Gram senthttps://host. - 79ff692: The Platform MCP no longer says sign-in needs manual setup for an MCP server whose OAuth provider supports client ID metadata documents but not dynamic client registration.
inspect_mcp_candidatenow classifies such a provider as automatic sign-in setup (oauth_discovery: available_cimd) and reports which automatic path applies in a newautomatic_client_registrationfield.attach_platform_mcp_identity_providerconnects these providers through a client ID metadata document, the same path the dashboard's automatic setup uses, instead of refusing them. Providers that offer dynamic client registration keep using it. - 036c20e: Evict expired entries from the in-memory cache of organization default hosts that hook deny links use, so it only holds organizations seen within the last five minutes.
- 05f6816: Put hook deny links on the organization's default host. The block page link, the risk policy bypass request link and the risk policy acknowledgement link that Gram returns when a hook denies an action now use the organization's recorded default host. Organizations with no recorded host keep the legacy host, which defaults to the site URL.
- 6084dd2: Record the return URL on every Stripe Checkout intent, including intents created on the site host, so a retried checkout replays the same success and cancel URLs after the site URL changes.
- dfe5c0f: Platform MCP can now pause and resume one data export route. Only the route's on/off state changes; its data source and destination are left untouched, resuming a route whose destination is missing or deleted is refused, and each change is recorded in the audit log as
data_export_route:pauseordata_export_route:resume. Data produced while a route is paused is dropped, not delivered later. - 5e24636: Let an agent create an MCP server from tools a project's functions already produce through the Platform MCP.
create_mcp_from_functionscreates the server and the tool list behind it through the same code the dashboard uses, refuses any tool the project's latest completed deployment does not produce, schedules the tool-search index the new server needs, previews the exact slugs before it is confirmed, and reports whether the server joined the project's Default plugin. Creating a toolset now refuses a name or description longer than its column allows as a bad request instead of an unexpected error, stores a blank description as none, and fails instead of auto-enabling the toolset when the organization's enabled-server count cannot be read. - 7e6c1bf: The Platform MCP can now create a plugin and rename one, so an agent can finish setting up an MCP server without sending the administrator to the dashboard to make a plugin first. Renaming changes only the display name; the plugin's install name stays the same.
- 10c24ea: Support MCP 2026-07-28-only servers when inspecting and registering remote URLs through Platform MCP. Probe with
server/discoverbefore falling back to legacy initialization, while preserving OAuth discovery, JSON-only admission, and inspection safety limits. - 5749029: The Platform MCP
get_plugintool now shows administrators the project marketplace's latest publish attempt next to package freshness. It reports whether a publish is queued, running, retrying, succeeded, or failed, when Gram last recorded a successful publish, and a short, safe explanation of any failure with its next step, so an agent can say why a plugin is stale. - 56c556b: Organization administrators can now republish a stale plugin from the Platform MCP with
republish_plugin. Whenget_pluginreports that a plugin's published package is out of date, an agent can request a publish of the project's plugin packages right away instead of waiting for the hourly refresh. The tool asks for confirmation first, because the publish covers every plugin in the project. It does nothing when the package is already current and refuses with a dashboard link when no package repository is connected. The publish runs in the background, andget_pluginreports when it has landed. - 056c69f: Increase Platform MCP rate limits for skill review, documentation search, plugin and tool inventory, and bulk metadata and access administration. Preserve separate limits for external requests, sensitive data retrieval, and higher-impact security operations.
- bf47a32: People using a plugin now get skill and MCP server changes promptly instead of within the hour. A new skill version (added directly, approved from a suggestion, or restored), a skill rename or archive, deleting an MCP server built from a toolset, linking or unlinking its sign-in provider, and changing the headers its users supply each republish the plugins that carry them.
- c74d043: PII findings on JSON content now point at the matched text in the original content.
- 59d97c1: Automatic role distribution no longer retries indefinitely for organizations that have no project yet. Roles are distributed when the organization creates its first project.
- d69b6c6: Read a disabled inference key's monthly usage through the OpenRouter provisioning key. OpenRouter rejects a disabled key's own credentials with 401, which made the billing page's spend caps request fail for any organization with a disabled key.