WavefrontDevelopers

Reference

Changelog and versioning

Changes to the REST API and the MCP server that integrations should know about.

2026-10-14

  • MCP connections keep the access they were granted. The consent page offers read, write and stay connected whatever the client asked for, and a token's scope is never narrowed on the code exchange or a refresh. Connections that lost write an hour after it was granted are fixed by disconnecting and connecting again.
  • Connected agents: see and disconnect the agents connected as you under Account → Connected agents (GET /me/connections, DELETE /me/connections/{id}).
  • MCP tools: wavefront_whoami, wavefront_get_overview, wavefront_list_content_versions, wavefront_list_destination_types and wavefront_set_indexnow; wavefront_set_autopilot works with an autopilot API key. 95 tools in all.
  • System administrators: Wavefront's administrators manage users, workspaces and billing from an agent with the mcp:admin scope, which only they are offered when connecting. A workspace's owners see every change an administrator makes in its activity.
  • Slack and Microsoft Teams over MCP: owners change which messages go to the connected channel and send a test with wavefront_update_slack, wavefront_test_slack, wavefront_update_teams and wavefront_test_teams. Connecting and disconnecting stay in the web app.
  • Event deliveries over MCP: wavefront_get_event_delivery shows one delivery's body and attempts, and wavefront_get_event_subscription pages its deliveries with cursor.
  • Comments from API keys over MCP: wavefront_add_comment accepts a key with generations:write, as /v1 does, and records the comment as the key's.

2026-10-13

  • API key scopes: autopilot, destinations and integrations, so a key can run what an owner automates.
  • MCP tools: add, edit and test destinations (webhooks; a CMS returns a link for a person to connect), approve, edit and dismiss suggestions, and wavefront_apply_strategist_proposal. 90 tools in all.
  • Strategist replies carry a diff of the calendar (added, moved, removed, retitled) and saved_before. A reply that moves more than five posts holds them until you apply it, and plan items can be a refresh_of a page on your site, which keeps its URL.
  • REST: GET …/versions/{vid}/diff compares two versions.
  • MCP sign-in through the older host now completes on https://wavefront.adwave.com.
  • Instructions for your agent to paste into Grok, Claude or ChatGPT, and updated Grok connector steps.

2026-10-12

The public developer docs launch, describing the API and MCP server as they are today:

  • REST API at https://wavefront.adwave.com/v1, with an OpenAPI 3.1 document that names every operation (operationId), groups it by tag, gives the API key scope it needs (x-required-scope), marks web-app-only operations (x-session-only) and describes every event webhook.
  • Workspace API keys with seven scopes: generations:read, generations:write, publish, context:read, context:write, context:git-sync (legacy) and webhooks.
  • MCP server at https://wavefront.adwave.com/mcp (Streamable HTTP, OAuth 2.1 with dynamic client registration, client ID metadata documents and PKCE), where every tool has a title and read-only, destructive, idempotent and open-world hints.
  • Event webhooks signed with Standard Webhooks, with a delivery log, redelivery and secret rotation.
  • Hosts: https://wavefront.adwave.com is the home of the API and MCP server. Integrations set up on wavefront.adwave-apps.com keep working.

Versioning policy

The REST API is versioned in its path. /v1 is a contract:

  • Additive changes can ship at any time, without notice: new operations, new optional request fields and query parameters, new response fields, new event types, new error codes for new situations, and new values in lists such as destination types. Write clients that ignore fields they don't know and handle unknown enum values.
  • Breaking changes get a new version and notice: removing or renaming a field or operation, changing a field's type or meaning, or making an optional input required. They ship under a new path such as /v2, announced here ahead of time, while /v1 keeps working.
  • Error code values are stable; message and hint wording can change at any time.
  • MCP tools follow the same rule: new tools and new optional inputs can appear at any time; a tool is not removed or changed incompatibly without notice.

Questions about a change: support@adwave.com.