MCP

Connect an agent with MCP

Wavefront is a remote MCP server. Add it to your AI client with this URL and sign in when the client asks:

https://wavefront.adwave.com/mcp

The client then works as you, in the workspaces you belong to: it can read the plan and documents, draft and revise, follow reviews, schedule and publish approved work. Only a person can approve a version, and only in the web app. On the consent page, leave read, write and stay connected checked. How the sign-in works: OAuth for MCP.

Claude

1. In Claude (web or desktop), open Settings → Connectors → Add custom connector.
2. Name it Wavefront and enter https://wavefront.adwave.com/mcp. Leave the OAuth client ID and secret empty: Claude registers itself.
3. Click Connect, sign in to Wavefront with an emailed code or Google, leave read, write and stay connected checked, and click Allow.
4. In a chat, turn the connector on from the tools menu and ask Claude to list your Wavefront workspaces.

On a Team or Enterprise plan, an owner adds the connector for the organization first.

Claude Code

claude mcp add --transport http wavefront https://wavefront.adwave.com/mcp

Then run /mcp in Claude Code and choose Wavefront to sign in.

ChatGPT

1. Open Settings → Apps & Connectors → Advanced settings and turn on developer mode (Plus, Pro, Business, Enterprise or Edu).
2. Under Apps & Connectors, choose Create, name it Wavefront, enter https://wavefront.adwave.com/mcp and choose OAuth authentication.
3. ChatGPT opens the Wavefront consent page. Sign in, keep the requested access and click Allow.
4. In a chat, add Wavefront from the tools menu and ask it to list your workspaces.

Cursor

Add Wavefront to ~/.cursor/mcp.json, or to a project's .cursor/mcp.json:

{
  "mcpServers": {
    "wavefront": { "url": "https://wavefront.adwave.com/mcp" }
  }
}

Cursor shows Needs login next to the server. Click it to sign in in your browser.

Grok

1. In Grok, open Settings → Connectors → Add custom connector (MCP).
2. Enter https://wavefront.adwave.com/mcp and leave authentication on OAuth.
3. Grok opens the Wavefront consent page. Sign in, leave read, write and stay connected checked, and approve.
4. In a chat, ask Grok to list your Wavefront workspaces.

Other clients

Any MCP client that supports Streamable HTTP and OAuth 2.1, with Dynamic Client Registration or Client ID Metadata Documents, works with the URL alone. A client that can only start local processes can use the mcp-remote bridge:

npx mcp-remote https://wavefront.adwave.com/mcp

Working with an agent

• Start with wavefront_list_workspaces; the tool reference lists every tool and its inputs.
• Generation is asynchronous: wavefront_generate returns an id, and wavefront_get_generation follows it. Pass idempotency_key on generate, create strategy, message strategist, request revision and add comment so a retried call never does the work twice.
• Results default to response_format: "concise", about 8,000 characters. Long text comes a page at a time (offset, max_chars), and lists page with cursor. detailed returns full metadata.
• Errors come back as tool errors that read Error <code>: <message>, with a Fix: line when there is one. The codes are the same as the REST API's: errors.
• Agents can't approve, withdraw a published page, post to social networks or send a newsletter. Publishing through MCP never emails a newsletter.

Troubleshooting

• 403 insufficient_scope on a write tool: the connection was granted read only. Reconnect and leave write checked.
• Asked to sign in again after a month: a connection lasts 30 days from when you approved it. Sign in again to renew it.
• 401 from the MCP URL: that is how a client discovers the sign-in. If your client stops there, it doesn't support OAuth; use mcp-remote as above.
• Allow does nothing in the browser: tell us the client and its redirect URI at support@adwave.com.
• A tool says the workspace isn't found: the connection sees only the workspaces the person who connected belongs to. Use the slug from wavefront_list_workspaces.