MCP Server

The Wized MCP server lets AI assistants read and modify your Wized project configuration on your behalf. Connect it to a coding tool like Claude Code, Codex, or Cursor, to Claude Desktop, or to any web client that supports custom connectors, and your AI can list apps, manage requests, inspect elements, create events, and more.

The Model Context Protocol (MCP) is an open standard that lets AI assistants connect directly to external tools and data sources, instead of you manually copying information back and forth. An MCP server exposes a set of capabilities that any compatible AI client can call as tools — in this case, your Wized project.

The Wized MCP server is hosted at:

https://server.wized.com/mcp

It is a remote, HTTP-based MCP server (also called "Streamable HTTP" in the MCP spec). You don't need to install anything locally; your client connects directly to the URL above and authorizes with your Wized account via OAuth on first use.

Connecting from Claude Desktop

Claude Desktop connects to remote MCP servers as custom connectors — the same account-level connectors used on Claude.ai and Cowork. Once you add Wized here, it's available across every Claude client without adding it again.

1. Open the connectors settings

In Claude Desktop, go to Customize → Connectors, click the + next to Connectors, and choose Add custom connector.

2. Configure the connector

• Name: Wized
• URL: https://server.wized.com/mcp

Leave the Advanced settings (OAuth Client ID/Secret) blank — Wized supports automatic OAuth client registration. Click Add.

3. Authorize the connection

Click Connect next to the Wized connector, or simply start using a Wized tool in a conversation. A browser window opens so you can sign in to your Wized account and approve the connection.

4. Use the tools in a conversation

Enable the Wized connector from the tools/connectors menu in a new conversation. The assistant can now list projects, read requests, update elements, create events, and so on.

Note

claude_desktop_config.json still exists, but it only configures local, stdio-based MCP servers running on your machine. Since Wized is a remote HTTP server, use the custom connector flow above instead of editing that file.

Connecting from Claude Code

Claude Code can add remote MCP servers directly from the CLI.

1. Add the server

claude mcp add --transport http wized https://server.wized.com/mcp

By default this adds the server for the current project only. Add --scope user instead if you want it available in every project, or --scope project to share it with your team via a committed .mcp.json.

2. Authorize the connection

Start (or continue) a session and run:

/mcp

Select wized, choose Authenticate, and sign in to your Wized account in the browser tab that opens.

3. Verify and use it

/mcp should now show wized as connected. Ask Claude to list your apps, read requests, or update elements — it now has access to the same projects you do.

If you'd rather configure it as JSON (e.g. in a project's .mcp.json), the equivalent entry is:

{
  "mcpServers": {
    "wized": {
      "type": "http",
      "url": "https://server.wized.com/mcp"
    }
  }
}

Connecting from Codex

Codex CLI can add remote MCP servers from the CLI, or by editing its TOML config.

1. Add the server

codex mcp add wized --url https://server.wized.com/mcp

This writes an entry to ~/.codex/config.toml:

[mcp_servers.wized]
url = "https://server.wized.com/mcp"

2. Authorize the connection

codex mcp login wized

This opens your browser to sign in to your Wized account and approve the connection.

3. Verify and use it

codex mcp list

wized should appear in the list. You can now ask Codex to work with your Wized project's apps, requests, elements, and events.

Connecting from Cursor

Cursor manages MCP servers from its Customize settings panel, backed by an mcp.json config file.

1. Add the server

Add a wized entry to .cursor/mcp.json for a single project, or to ~/.cursor/mcp.json to make it available in every project:

{
  "mcpServers": {
    "wized": {
      "url": "https://server.wized.com/mcp"
    }
  }
}

Alternatively, open Cursor → Customize and add the server through the UI.

Or share a one-click install link with your team:

cursor://anysphere.cursor-deeplink/mcp/install?name=wized&config=eyJ1cmwiOiJodHRwczovL3NlcnZlci53aXplZC5jb20vbWNwIn0=

2. Authorize the connection

Open the Customize panel, find the wized server, and click to sign in when prompted. Your browser opens to sign in to your Wized account and approve the connection.

3. Verify and use it

Once connected, the wized server shows as enabled in the Customize panel, and its tools become available to the Agent in any chat.

Connecting from a web client (custom connector)

Most modern AI web clients (Claude.ai, ChatGPT, and others) support adding custom connectors for remote MCP servers. The exact UI varies, but the steps are the same.

1. Open the connectors settings

In your client, find the section for adding a custom connector. In Claude on the web this lives under Customize → Connectors → Add custom connector.

2. Configure the connector

Fill in the form with:

• Name: Wized
• URL / Server URL: https://server.wized.com/mcp
• Transport: some clients also ask for a transport type — choose HTTP / Streamable HTTP, the default for remote MCP servers.

3. Authorize the connection

When you save the connector — or the first time you use a Wized tool from a conversation — the client will redirect you to sign in to Wized and approve the connection. After approval, the connector becomes active and the AI can call Wized tools.

4. Use the tools in a conversation

In a new conversation, enable the Wized connector from the tools/connectors menu. The assistant can now list projects, read requests, update elements, create events, and so on.

Available tools

Once connected, the assistant has access to tools to list, read, create, update, and delete the main configuration items of your project:

• Apps — connect and manage third-party app credentials.
• Requests — every provider (REST, Airtable, Firebase, Supabase, Memberstack, WordPress) and method.
• Elements — visibility, text, attributes, classes, styles, events, and more.
• Global events — triggers, page conditions, and actions.
• Data Store — variables, cookies, parameters.

All changes the AI makes go through the same branching system you use in the configurator, so you can review, preview, and merge them safely.