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.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Company and contact data for AI agents. Connect to TargetWise over Streamable HTTP to find companies and employees, enrich selected records, and retrieve available work emails and business phones.
ai.targetwise/targetwiseAuthorization: Bearer ... headerThis repository contains the official connection guide, client configurations and directory manifest for the hosted TargetWise service. The hosted server implementation and database are not distributed in this repository.
TARGETWISE_API_KEY environment variable.Customer-key clients must use /api/mcp. The hosting platform reserves /mcp; it is not the customer-key endpoint.
Alternatively, use the included .mcp.json project configuration. It reads TARGETWISE_API_KEY from the environment. Keep credentials out of version control.
In Cursor's MCP settings, configure a remote server with the endpoint and Authorization header. The included cursor.mcp.json uses Cursor's environment interpolation syntax.
Install the included extension:
When prompted, enter your TargetWise workspace API key. The extension declares a sensitive setting, TARGETWISE_API_KEY, and uses it in the Bearer header. Gemini CLI stores sensitive extension settings in its system keychain. Calls still consume your TargetWise workspace credits.
Clients that require an OAuth authorization flow cannot connect directly to this bearer-key gateway. Use a client that supports custom authentication headers. Do not interpret directory publication as approval by an AI platform.
| Tool | Purpose |
|---|---|
targetwise_find_companies | Resolve a company name, website or registration number into candidates |
targetwise_search_companies | Find companies using supported business, location, industry or technology filters |
targetwise_search_contacts | Find professional candidates at known company domains |
targetwise_search_employees | Search employee records by company, person name, job title, department or seniority |
targetwise_get_employee | Retrieve available details for one selected employee |
targetwise_autocomplete_company | Populate company fields from an identity lookup |
targetwise_enrich_company | Retrieve a profile for one selected company or supported identifier |
targetwise_enrich_contact | Retrieve requested contact fields and available professional profile context |
targetwise_find_work_email | Look up one known professional's available work email |
targetwise_find_phone | Look up one known professional's available business phone |
targetwise_reverse_email_lookup | Resolve one business email into available person and employer context |
Discovery definitions are published at https://targetwise.ai/.well-known/mcp/server-card.json. They are generated from the same tool definitions used by the running server.
The official MCP Registry record is active at https://registry.modelcontextprotocol.io/v0.1/servers/ai.targetwise%2Ftargetwise/versions/latest. Directory review and client-gallery approval are separate from registry publication.
The host owns decisions and downstream actions. TargetWise MCP does not send outreach or write to a CRM.
Data calls are metered against the workspace allowance. Consult https://targetwise.ai/pricing for current plans and result charges. Do not automatically enrich every search candidate.
matched, partial and not_found outcomes and preserve unresolved_fields.Use Content-Type: application/json and Accept: application/json, text/event-stream. The documented compatibility flow uses protocol version 2025-11-25: initialize, send notifications/initialized, then list or call tools. Follow the live documentation for additional supported request modes.
The tools retrieve data, but calls can consume credits; consequently their annotations include readOnlyHint: false and idempotentHint: false.
The MIT license covers the connection examples and documentation in this repository. Access to the hosted service and returned data is governed by TargetWise's plans and terms: https://targetwise.ai/legal/terms. The service and data are not licensed under MIT.
Privacy: https://targetwise.ai/legal/privacy
Security: https://targetwise.ai/trust/security
Support: https://targetwise.ai/company/contact
Factual signals from GitHub, npm, and our automated checks β not a rating.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/targetwise)<a href="https://allmcps.com/mcp/targetwise"><img src="https://allmcps.com/api/badge/targetwise?style=directory" alt="TargetWise on AllMCPs" /></a>