AI clients implementation guide
Connect TargetWise to Cursor and Claude Code
Configure bearer authentication for TargetWise MCP in Cursor and Claude Code, discover tools and make a bounded contact lookup with clear client requirements.
Updated 10 September 2026 · Documentation and review policy
Use a client that supports bearer headers.
Create a dedicated workspace key and expose it to your client as TARGETWISE_API_KEY. The production MCP endpoint is https://targetwise.ai/mcp. The current gateway authenticates with a bearer key; it does not provide an OAuth authorization flow.
| Client | Connection path |
|---|---|
| Cursor | Remote MCP URL with Authorization header and environment interpolation |
| Claude Code | Remote HTTP MCP with a configured Authorization header |
| Claude web / ChatGPT apps | An OAuth-only setup cannot connect directly to this bearer-only gateway. Use a compatible client or an separately implemented authenticated adapter. |
Configure Cursor or Claude Code.
Cursor
Add this configuration to .cursor/mcp.json. Start Cursor with the environment variable available, then enable the server and inspect its tool list. See Cursor’s MCP and interpolation documentation.
{
"mcpServers": {
"targetwise": {
"url": "https://targetwise.ai/mcp",
"headers": {
"Authorization": "Bearer ${env:TARGETWISE_API_KEY}"
}
}
}
}Claude Code
Use the HTTP transport and bearer header, then inspect the connection with /mcp. The command stores connection configuration locally; keep it private. See Claude Code’s MCP instructions.
claude mcp add --transport http targetwise https://targetwise.ai/mcp \
--header "Authorization: Bearer $TARGETWISE_API_KEY"Discover tools, then make one narrow request.
Discovery should return eleven tools. Select targetwise_find_work_email for an email-only lookup. Use one identity pattern; the example below must be replaced with a known professional.
{
"first_name": "Alex",
"last_name": "Reed",
"company_domain": "example.com"
}Find the work email for this reviewed contact using one TargetWise call. If no email is returned, report it as unavailable. Do not request a phone, start another search, update a CRM or send a message.Read result.structuredContent, check result.isError and the business status, and preserve unresolved fields. Enrichment calls are metered. Retrieval permission does not automatically authorize outbound communication.
Separate server checks from client installation.
The gateway’s initialize, discovery and tool contracts are tested locally. After adding your actual key, verify discovery and one controlled lookup in the chosen client. If discovery succeeds but a lookup fails, check the workspace balance and permissions. If authentication fails, replace or rotate the bearer key; do not put it in the URL.
For the exact request lifecycle, use the MCP reference. For client-specific app requirements, consult the Claude connector documentation and ChatGPT apps documentation.