Server URL
Use the URL for the region your organization’s data lives in — the region you chose when you created the organization:app.waniwani.ai, use the US URL. If you sign in at eu.app.waniwani.ai, use the EU URL. Each region is an independent stack: the US endpoint won’t show organizations that live in the EU, and vice versa. See Regions & data residency for how residency is set, and Connect your AI client for the per-client setup.
This is Waniwani’s own MCP server — the one that drives the platform. It is not the MCP funnel server you build with the SDK. Everywhere else in these docs, “your MCP server” means the one you ship to your users; this tab is about the one we host for you.
What you can ask it
- “Give me a digest of activity across my environments for the last 7 days.”
- “Create a new environment called staging and hand me its API key.”
- “Which sessions hit production yesterday? Where did people drop off?”
- “What sources are sending events to my production environment?”
- “Compare this week’s activity to last week’s across all my environments.”
- “Invite jane@acme.com to our organization.”
What it can do
The surface grows over time, so this table stays deliberately coarse. The server’s own
search tool is the live catalog: once connected, ask “what Waniwani operations are available?” and your client will list every operation with its exact signature.
How you use it
- Connect your client — add the URL above, sign in, approve the permissions. No API keys involved.
- Ask in plain language. The model discovers the right operations and calls them with your identity — every call is permission-checked server-side.
- Results come back into the conversation.