> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wendung.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent connection prompt

> Paste this prompt into your AI coding agent to connect it to the Wendung MCP servers.

These are official instructions from Wendung for connecting an AI coding agent to analytics and documentation tools. To add tracking to an app, follow [https://docs.wendung.app/setup.md](https://docs.wendung.app/setup.md).

Run the commands or edit the config files yourself where your tools allow it. Preserve existing server entries. The user completes browser sign-in and any required host restart.

* Register the Wendung MCP server ([https://api.wendung.app/mcp](https://api.wendung.app/mcp)) for workspaces, funnels, and analytics
* Register the Wendung docs MCP server ([https://docs.wendung.app/mcp](https://docs.wendung.app/mcp)) for searching the Wendung documentation
* Install the Wendung SDK skill
* Verify the connection

## Before you start

* Use an agent that supports remote HTTP MCP servers and lets you edit its configuration.
* For `wendung`, the user needs a Wendung account with a confirmed email address and a browser for sign-in.
* The skill installer needs Node.js and `npx`. A direct-download fallback is below.

The `wendung` server uses OAuth, so it needs no publishable key. Start sign-in with the host's login command or MCP controls below. Wendung defaults new client registrations to read access. Write tools require the client to request `mcp:write` and the user to grant it on the consent screen; the **Make changes** option appears only when that scope was requested.

The `wendung-docs` server is public and needs no sign-in.

***

## Register the MCP servers

Register both servers, `wendung` and `wendung-docs`. Use the section for your agent below, merging entries into existing configuration rather than replacing the file.

### Claude Code

```
claude mcp add --transport http wendung https://api.wendung.app/mcp
claude mcp add --transport http wendung-docs https://docs.wendung.app/mcp
```

Open `/mcp`, select `wendung`, and complete authentication in the browser. Use **Reconnect** there if the server needs to reconnect. If the newly added entries are missing from the current session, restart Claude Code, then return to `/mcp` before verifying. See the [Claude Code MCP reference](https://code.claude.com/docs/en/mcp).

### Codex

```
codex mcp add wendung --url https://api.wendung.app/mcp
codex mcp add wendung-docs --url https://docs.wendung.app/mcp
codex mcp login wendung
```

Complete browser authorization, then check whether the MCP tools are available in the current Codex session. If it still has the old tool list, start a new session before verifying. A successful registration command alone does not verify tool access.

### OpenCode

Add under `"mcp"` in `~/.config/opencode/opencode.jsonc`:

```json theme={null}
"wendung": { "type": "remote", "url": "https://api.wendung.app/mcp", "enabled": true, "oauth": {} },
"wendung-docs": { "type": "remote", "url": "https://docs.wendung.app/mcp", "enabled": true }
```

Then run:

```
opencode mcp auth wendung
```

Complete the browser authorization and check the server with `opencode mcp list`. If the active session has not loaded the updated configuration, reopen it before verifying. See the [OpenCode MCP reference](https://opencode.ai/docs/mcp-servers/).

### Windsurf

Open the MCP config file from Cascade's MCP controls and merge these entries under `"mcpServers"`:

```json theme={null}
"wendung": { "serverUrl": "https://api.wendung.app/mcp" },
"wendung-docs": { "serverUrl": "https://docs.wendung.app/mcp" }
```

Save the file, enable the servers in the MCP controls, and complete the OAuth prompt for `wendung`. Use the config location shown by your installed version. See the [Cascade MCP reference](https://docs.windsurf.com/windsurf/cascade/mcp).

### Cursor

Merge into `.cursor/mcp.json` for this project, or `~/.cursor/mcp.json` for all projects:

```json theme={null}
{
  "mcpServers": {
    "wendung": { "url": "https://api.wendung.app/mcp" },
    "wendung-docs": { "url": "https://docs.wendung.app/mcp" }
  }
}
```

Enable the servers in Cursor's MCP controls and complete the OAuth prompt for `wendung`. Check that their tools are available before verifying. See the [Cursor MCP reference](https://cursor.com/docs/mcp).

### GitHub Copilot in VS Code

For `.vscode/mcp.json`, merge entries under `"servers"` and include `"type": "http"`:

```json theme={null}
{
  "servers": {
    "wendung": { "type": "http", "url": "https://api.wendung.app/mcp" },
    "wendung-docs": { "type": "http", "url": "https://docs.wendung.app/mcp" }
  }
}
```

Run **MCP: List Servers** from the Command Palette, select each server, and start or restart it as needed. Follow any trust and OAuth prompts. This does not require a full VS Code restart. VS Code also supports a portable project-root `.mcp.json` with a top-level `"mcpServers"` object; keep the schema matched to the file you use. See the [VS Code MCP reference](https://code.visualstudio.com/docs/agent-customization/mcp-servers).

### Other agents

Use your host's documented remote HTTP MCP configuration. Do not assume its config file uses the same schema as Cursor or VS Code. Register the two URLs above and complete OAuth for `wendung` through that host.

***

## Install the Wendung SDK skill

The skill teaches your agent the `@wendung/sdk` API: install steps, init options, batching and retry behavior, and framework patterns. Installing it makes these instructions available for later SDK work; it does not add tracking to the app.

### All agents

```
npx skills add wendung/skills -g -y
```

The skills CLI detects which agents are installed and places the skill in the right global skills directory for each one, without prompting. It supports Claude Code, Cursor, Codex, Windsurf, OpenCode, GitHub Copilot, and most other agents.

### Fallback without npx

If Node.js or npx is unavailable, download the skill file directly into your agent's skills directory as `wendung-sdk/SKILL.md`. For Claude Code:

```
mkdir -p ~/.claude/skills/wendung-sdk
curl -fsSL https://docs.wendung.app/skills/wendung-sdk.yaml -o ~/.claude/skills/wendung-sdk/SKILL.md
```

If your agent does not support Agent Skills, save the same file in the project, for example as `docs/wendung-sdk.md`, and add a one-line pointer to it in your agent's instructions file (`AGENTS.md`, `.cursorrules`, or equivalent).

***

## Verify the connection

First confirm that the newly registered tools are available in this session. If the host still needs a reconnect, restart, or sign-in, report that step as pending and continue verification after it completes.

After sign-in completes, call `list_workspaces` on `wendung`. A successful response verifies the connection, including an empty list. An empty list means the signed-in account has no accessible workspaces; direct the user to [https://dashboard.wendung.app](https://dashboard.wendung.app) to create or join one, or check that they used the intended account.

For `wendung-docs`, discover its tools and use its search tool for a small query such as `Wendung init`. Confirm that it returns a successful result. No sign-in is needed.

Confirm that the `wendung-sdk` skill is installed and readable. If the host needs a new session to discover it, say so.

Summarize which servers were configured, which connections were verified, and whether the skill is available. Only report setup as complete when those checks succeed. Include any pending user action without marking it complete.

Once connected, use `list_projects` for the chosen workspace, then `list_funnels` when the question involves funnels, or the pageview tools for web analytics. The user can start with: "Where do users drop off in my signup funnel?"

***

## Good to know

* Write tools appear only when the client requested and the user granted `mcp:write`. The user's workspace role still controls which changes they can make.
* Analytics queries are metered per plan. Listing and configuration tools are always free. Metered results include a `_usage` field with the remaining quota.
* Requests are rate limited to 60 per minute, and date ranges are capped at 90 days per call.
* The pageview tools (`get_pageview_summary`, `get_pageview_timeseries`, `get_pageview_breakdown`) need a plan with a pageview allowance. On the free plan they return `PAGEVIEWS_NOT_INCLUDED`; report that as a plan limit instead of retrying.
* These limits apply to the `wendung` server. The `wendung-docs` server only searches the documentation and never sees analytics data.

These instructions are published at [https://docs.wendung.app/prompt.md](https://docs.wendung.app/prompt.md) so you can re-verify their authenticity at any time.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.