Skip to main content
Waniwani runs the MCP server in two regions. Add the URL for the region where your organization lives: It’s a remote MCP server (Streamable HTTP) that authenticates with OAuth 2.1. There is no API key to paste: you add the URL, your client opens a browser window, you sign in to Waniwani and approve the requested permissions. From then on the connection acts as you — same organizations, same role.
Each region is an independent stack with its own data. Sign in on the endpoint that matches your data residency — the region you chose when you created your organization. The US endpoint won’t show organizations that live in the EU, and vice versa. The examples below use the US URL; if your data is in the EU, swap in https://eu.mcp.waniwani.ai/mcp.

​
Claude (claude.ai and desktop)

  1. Open Settings → Connectors.
  2. Click Add custom connector.
  3. Enter https://mcp.waniwani.ai/mcp and confirm.
  4. A Waniwani sign-in window opens — sign in and approve the permissions.
On Team and Enterprise plans, an admin may need to enable custom connectors for your workspace first.

​
Claude Code

Then run /mcp inside Claude Code and select waniwani to complete the browser sign-in.

​
Cursor

Add the server to ~/.cursor/mcp.json (or Settings → MCP → Add new MCP server):
~/.cursor/mcp.json
Cursor prompts you to authenticate in the browser the first time it connects.

​
ChatGPT

Custom MCP connectors require developer mode:
  1. Open Settings → Apps & Connectors → Advanced settings and enable Developer mode.
  2. Back in Connectors, click Create and enter https://mcp.waniwani.ai/mcp.
  3. Complete the sign-in when prompted.
Client UIs change quickly. If a menu has moved, follow your client’s own guide for adding a remote MCP server and use the URL above — the server implements the standard discovery flow, so any MCP-capable client that supports OAuth can connect.

​
What happens when you sign in

1

Your client discovers Waniwani

The client reads the server’s metadata and learns which Waniwani stack handles sign-in for that region (app.waniwani.ai for US, eu.app.waniwani.ai for EU). It registers itself automatically — no manual client IDs.
2

You sign in to Waniwani

The browser opens your usual Waniwani login. If you’re already signed in, you go straight to consent.
3

You approve the permissions

The consent screen itemizes exactly what the connection may do (read environments and analytics, create environments and keys, and so on). You only see permissions your account is entitled to.
4

Connected

The client receives a token bound to this server and your approved permissions. Every call it makes runs under your identity.

​
First thing to try

Who am I signed in to Waniwani as, and what can you do for me here?
Your client will call the server’s whoami and search tools and report your account, your organizations, and the available operations. From there, ask for what you want in plain language — see the overview for example prompts.

​
Troubleshooting

Your token expired or was invalidated. Most clients refresh automatically; if yours doesn’t, disconnect and reconnect the server (re-running the sign-in) to mint a fresh token.
set_active_org only switches to organizations you belong to — the API rejects anything else with a NOT_ORG_MEMBER error. Ask “who am I?” — the whoami tool lists the organizations you can act on and their ids.
Expected. Each connection carries its own active organization, independent of the dashboard — switching in one place doesn’t switch the other. Ask the model to switch here too (it calls set_active_org), or check where you stand with “who am I?”.
The available surface is curated and grows over time. Ask the model to run search again — it returns the live catalog with exact signatures. If what you need isn’t there yet, tell us.