MCP server

RenewSell runs a remote MCP server. Once an AI assistant connects, it can read credits and Targets, find contacts, query customs data and send outreach. This page covers connecting, the tools, and what to watch for in write tools.

Connect

1. Create a key on the API keys page, described in API keys. Tick Allow outreach actions if the assistant should send messages or like posts.
2. In your AI assistant's MCP settings, add a remote HTTP server. The URL is https://www.renewsell.com/api/mcp, with the header Authorization: Bearer <your API key>.
3. The assistant calls initialize, then tools/list. The server identifies itself as RenewSell.

The server takes POST only and speaks JSON-RPC 2.0. It supports MCP protocol versions 2024-11-05, 2025-03-26 and 2025-06-18. A GET request returns 405.

Tools

The server exposes 22 tools. Every tool name shares one fixed prefix; the table lists the part after it, and the assistant shows the full name and arguments once connected.

What it does	Tool	Authorization
Show the key's scopes, plan and connected-channel counts	whoami	Default key
Show balance, reserved credits and usage this period	get_credits	Default key
List connected channels, without credentials	list_connect_accounts	Default key
List and read Targets	list_targets, get_target	Default key
Read criteria and each search round	get_target_strategy	Default key
Read items in a Target (cursor pagination)	list_target_items	Default key
Create a Target and start a search	create_target	Default key
Raise the desired result count	expand_target	Default key
Read or cancel a job	get_job, cancel_job	Default key
Run company research	research_public_web	Default key
Find contacts for one company	find_contacts	Default key
Run one of the seven customs queries	customs_company_candidates and the other six	Default key
Send one outreach message	send_outreach	Allow outreach actions
Like a LinkedIn post	like_linkedin_post	Allow outreach actions

Write tools

• create_target, expand_target, send_outreach, like_linkedin_post and billable customs queries all require an idempotency_key. Retrying with the same key does not run the work or charge twice.
• send_outreach only targets an existing conversation, or a contact plus a channel. There is no bulk sending.
• create_target rejects a count above the plan's result ceiling per list.
• Billable write tools use the same credit units as the app; see How credits are charged.

Billing

Tool	Charge
Read tools (whoami, get_credits, lists and lookups)	None
create_target	Searching is free; accepted results cost Qualified lead
find_contacts	Contact discovery, per company
research_public_web	Company research, up to 25 credits per report
Customs queries	Customs trade data, per returned row
send_outreach, like_linkedin_post	Customer interaction, per action

Errors and rate limits

• A failed tool call returns isError: true with { code, message }. A missing grant reports insufficient_scope.
• Common codes: invalid_params (bad arguments), not_found (no such object), idempotency_conflict (the same key was used for a different request).
• Too many requests return the JSON-RPC error -32001 with retry_after_ms; wait, then retry.
• A malformed JSON-RPC request returns -32600. Tool argument failures are tool errors (isError: true with invalid_params), not JSON-RPC errors.

Examples

List the tools:

curl "https://www.renewsell.com/api/mcp" \
  -H "Authorization: Bearer $RENEWSELL_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Call a read-only tool:

curl "https://www.renewsell.com/api/mcp" \
  -H "Authorization: Bearer $RENEWSELL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"<full tool name>","arguments":{}}}'

FAQ

The assistant shows no tools. First check the key: GET /v1/credits with the same key should return a balance. Then check that the client uses a remote HTTP MCP server and sends Authorization: Bearer.

Can it send messages in bulk? No. The outreach tool sends one message at a time and must target an existing conversation or contact.

The research tool reports unavailable. That environment has no research data source configured. The call fails up front instead of queueing work, and it costs no credits.