# TargetWise [Health: Active]

**Category:** 🎯 Marketing  
**Repository:** https://github.com/sens663/targetwise-mcp  
**GitHub Stars:** 0  
**Views:** 5  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/targetwise

## Description
Hosted B2B prospecting and enrichment MCP with 11 tools for company/contact discovery, employee search, profile enrichment, work email lookup, business phone lookup and reverse email lookup. Streamable HTTP at https://targetwise.ai/api/mcp; requires a TargetWise workspace Bearer API key. Requests consume workspace credits. Public repo provides connection examples, not the server implementation.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "targetwise": {
    "url": "https://targetwise.ai/api/mcp"
  }
}
```

## Documentation

## What the TargetWise MCP server does

The TargetWise MCP server exposes hosted B2B data capabilities to MCP-compatible clients. It helps agents identify companies, search for employees and professional contacts, fill in company or contact details, and retrieve available business contact information.

The service supports several research patterns. A company can be resolved from a name, website, or registration number, or searched with business, location, industry, and technology filters. Employee searches can use a company, person name, job title, department, or seniority. After reviewing candidates, an agent can request enrichment for a selected company, employee, or contact.

Available contact lookups include work email, business phone, and reverse resolution from a business email to associated person and employer information. The server does not send outreach or write to a CRM.

## How it works

Connections use the hosted Streamable HTTP endpoint at `https://targetwise.ai/api/mcp`. Clients authenticate by sending the workspace API key in an `Authorization: Bearer ...` header. The documented protocol flow uses JSON requests, the `application/json` and `text/event-stream` response types, and protocol version `2025-11-25`; clients should follow the live documentation for other supported request modes.

A practical workflow is to run a bounded discovery search, inspect the returned candidates, and enrich only the selected records. Prospecting results are limited to 25 candidates per page and 10 pages. Company identity searches return no more than five candidates per page. Calls may consume workspace credits, including searches, so automated enrichment of every candidate should be avoided.

Returned data can indicate `matched`, `partial`, or `not_found` outcomes and may include unresolved fields. Optional professional profile fields depend on account access and record availability. Retrieval timestamps identify when TargetWise made the request, while source provenance is included only when available.

## Setup and configuration

Create a TargetWise account and obtain a workspace API key from Dashboard → Developers. Store the key in the client's secret store or in `TARGETWISE_API_KEY`, then configure a client that supports Streamable HTTP and custom bearer headers. Customer-key connections must use `/api/mcp`, rather than the platform's reserved `/mcp` path.

Claude Code can add the remote endpoint with an HTTP transport and bearer header. Cursor uses a remote MCP configuration with the endpoint and Authorization header. The repository also provides a Gemini CLI extension, a Claude Code plugin, and a Claude Desktop extension. The Claude plugin requires Node.js 20 or newer. Claude web accounts may connect directly when custom request headers are supported.

Clients that require OAuth authorization cannot connect directly to this bearer-key gateway. Keep API keys out of version control and use a dedicated workspace key where appropriate.

## Tools and capabilities

The TargetWise MCP server provides 11 tools:

- `targetwise_find_companies` resolves company names, websites, or registration numbers into candidates.
- `targetwise_search_companies` searches with supported company, location, industry, or technology filters.
- `targetwise_search_contacts` finds professional candidates at known company domains.
- `targetwise_search_employees` searches employee records by company, name, title, department, or seniority.
- `targetwise_get_employee` retrieves available details for one selected employee.
- `targetwise_autocomplete_company` fills company fields from an identity lookup.
- `targetwise_enrich_company` retrieves a profile for a selected company or supported identifier.
- `targetwise_enrich_contact` requests contact fields and available professional profile context.
- `targetwise_find_work_email` looks up an available work email for a known professional.
- `targetwise_find_phone` looks up an available business phone.
- `targetwise_reverse_email_lookup` resolves a business email into available person and employer context.

## Limitations and notes

The hosted implementation and its database are not included in the public repository. The repository contains connection guides, client configurations, discovery metadata, documentation, and MIT-licensed Claude connectors for the hosted service. The hosted service and returned data are governed by TargetWise plans and terms, not by the repository's MIT license.

A returned phone is not necessarily a verified mobile number, and a work-email result does not prove mailbox ownership or deliverability. Data availability varies by record and account access. Usage charges and current plan details should be checked in TargetWise pricing documentation.

_Full upstream README: https://allmcps.com/mcp/targetwise/readme_

