Wiza

Usage Guide

Wiza MCP

Wiza MCP provides remote contact enrichment, company enrichment, credit visibility, and prospect search over the Model Context Protocol. This page covers setup, authentication, usage examples, support, and privacy details in one place.

Endpoint https://mcp.wiza.co/mcp

Transport Streamable HTTP

Authentication OAuth 2.1 with PKCE, or bearer token when supported

Production Status Remote MCP service intended for production use

Tools

enrich_contact

Enrich a contact with email, phone, title, company, and profile data using a LinkedIn URL, email, or name plus company/domain.

enrich_company

Enrich a company profile with firmographic details such as industry, size, location, founding year, and social links.

get_credits

Return current API, email, phone, and export credit balances for the authenticated account.

search_companies

Search Wiza companies with firmographic, location, industry, and funding filters and return preview results with pagination.

search_prospects

Search Wiza prospects with person, company, industry, location, and pagination filters and return preview results.

Setup

Prerequisites

• A Wiza account with API access enabled
• Available API credits for the actions you want to perform
• An MCP client that supports remote HTTP servers and OAuth, or bearer-token headers

Remote MCP Configuration

Configure your MCP client with the following values:

• Server name: Wiza
• Server URL: https://mcp.wiza.co/mcp
• Transport: HTTP

Authentication

Most remote MCP clients will initiate OAuth in a browser the first time you connect. Wiza supports secure HTTPS callback URLs for remote clients and localhost HTTP callbacks for development environments.

If your client only supports static headers, generate a Wiza API key in your account settings and send it as a bearer token.

{
  "url": "https://mcp.wiza.co/mcp",
  "headers": {
    "Authorization": "Bearer YOUR_WIZA_API_KEY"
  }
}

AI Agent Setup

Configure Wiza MCP in your preferred AI agent. CLI setups support OAuth or API keys. UI-based agents use OAuth.

CLI Agents

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.

UI Agents

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:

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

Examples

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.

Operational Notes

• Responses are designed to remain compact and practical for MCP client usage.
• Browser-based MCP clients may require CORS; Wiza supports secure HTTPS origins and local development origins.
• If your network uses IP allowlisting or a firewall, make sure the remote MCP client platform can reach the server for both OAuth and MCP requests.
• Keep test credentials and sample data out of source control. Share them only through secure channels.

Support

• Email: [email protected]
• Documentation: /usage.html

Privacy

See the Wiza privacy policy for details on data handling and account usage: https://wiza.co/privacy

This guide is intended as a generic MCP usage reference for Wiza integrations and partner reviews.