- Register the Wendung MCP server (https://api.wendung.app/mcp) for workspaces, funnels, and analytics
- Register the Wendung docs MCP server (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.
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
/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.
Codex
OpenCode
Add under"mcp" in ~/.config/opencode/opencode.jsonc:
opencode mcp list. If the active session has not loaded the updated configuration, reopen it before verifying. See the OpenCode MCP reference.
Windsurf
Open the MCP config file from Cascade’s MCP controls and merge these entries under"mcpServers":
wendung. Use the config location shown by your installed version. See the Cascade MCP reference.
Cursor
Merge into.cursor/mcp.json for this project, or ~/.cursor/mcp.json for all projects:
wendung. Check that their tools are available before verifying. See the Cursor MCP reference.
GitHub Copilot in VS Code
For.vscode/mcp.json, merge entries under "servers" and include "type": "http":
.mcp.json with a top-level "mcpServers" object; keep the schema matched to the file you use. See the VS Code MCP reference.
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 forwendung 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
Fallback without npx
If Node.js or npx is unavailable, download the skill file directly into your agent’s skills directory aswendung-sdk/SKILL.md. For Claude Code:
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, calllist_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 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
_usagefield 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 returnPAGEVIEWS_NOT_INCLUDED; report that as a plan limit instead of retrying. - These limits apply to the
wendungserver. Thewendung-docsserver only searches the documentation and never sees analytics data.