Wiza MCP

Claude CLI (with API key)

claude mcp add --transport http wiza https://mcp.wiza.co/mcp \
  --header "Authorization=Bearer YOUR_WIZA_API_KEY"

Claude CLI (OAuth, no API key)

claude mcp add --transport http wiza https://mcp.wiza.co/mcp

Then run /mcp in Claude Code and follow the browser OAuth flow.

Codex CLI (with API key)

codex --mcp-config <(echo '{
  "mcpServers": {
    "wiza": {
      "url": "https://mcp.wiza.co/mcp",
      "headers": { "Authorization": "Bearer YOUR_WIZA_API_KEY" }
    }
  }
}')

Codex CLI (OAuth, no API key)

codex --mcp-config <(echo '{
  "mcpServers": {
    "wiza": {
      "url": "https://mcp.wiza.co/mcp"
    }
  }
}')

On first run, Codex will open a browser for OAuth authentication.

Claude Desktop (Claude Cowork)

Edit the Claude Desktop configuration file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %AppData%\Claude\claude_desktop_config.json

Add the Wiza server configuration:

{
  "mcpServers": {
    "wiza": {
      "type": "http",
      "url": "https://mcp.wiza.co/mcp"
    }
  }
}

Save the file and restart Claude Desktop. On first use, Claude will open a browser for OAuth authentication.

Claude.ai Web (Connectors)

Go to claude.ai/settings/connectors and add a custom MCP server with URL:

https://mcp.wiza.co/mcp

Complete the OAuth flow in the browser when prompted. The connector will then be available across all your Claude.ai conversations.

Codex Web / Desktop App (OAuth)

Visit chatgpt.com/codex or run codex app. Navigate to Settings → MCP, and add the server URL:

https://mcp.wiza.co/mcp

Save and start a new chat. Codex will prompt for OAuth on first tool invocation.

Prompt: "Look up the email for John Smith at Acme Corp."

What happens: The client calls enrich_contact with a person and company match. Wiza returns available work contact details such as verified email, title, LinkedIn profile, and phone data when requested.

Prompt: "Get company info for wiza.co."

What happens: The client calls enrich_company with the company domain. Wiza returns firmographic details such as industry, size, founding year, location, description, and public company profile links.

Prompt: "How many Wiza credits do I have left?"

What happens: The client calls get_credits. Wiza returns current API, email, phone, and export credit balances, and includes a purchase path when API credits are depleted.

Prompt: "Find VP Sales prospects at SaaS companies in Toronto with 51-200 employees."

What happens: The client calls search_prospects with title, location, and company filters. Wiza returns a preview page of matching people and a pagination token when additional results are available.

Prompt: "Find SaaS companies in Toronto with 51-200 employees."

What happens: The client calls search_companies with location, size, and industry filters. Wiza returns matching accounts, their websites, revenue and funding signals, and a pagination token when more results are available.

Prompt: "Find SaaS companies in Toronto, then get VP Sales and CRO leadership for the top matches and enrich their contact details."

What happens: The client first calls search_companies to identify matching accounts. It then uses those companies to drive search_prospects for leadership roles such as VP Sales or CRO, and finally calls enrich_contact plus enrich_company on the selected records. The result is an account-first workflow with leadership discovery and enriched contact plus company context.