RevorRevor

REVOR AI MCP

REVOR AI MCP connects target-company discovery, company research, contact discovery, and customs trade intelligence to AI clients that support MCP. Once connected, you can request work in natural language and let the client choose the appropriate REVOR AI tools.

Server URL

https://revor.ai/api/mcp

This is a remote service; no local server is required. API key authentication is the default installation method: create a key on the API Keys page, then store it in the client's private x-api-key header.

Use browser OAuth only as a compatibility option when the client cannot securely store a custom header.

To let an AI assistant install it for you, send the assistant the AI installation guide. It contains the API key entry point, header configuration, OAuth compatibility path, and post-install verification steps.

Get started

  1. Create or select a REVOR AI API key on the API Keys page.
  2. Add a new MCP service in WorkBuddy or another client that supports remote MCP.
  3. Enter REVOR AI as the name and https://revor.ai/api/mcp as the server URL.
  4. Add x-api-key: sk-revor-... in the client's private Header or Secret settings.
  5. Save the connection, reload tools, and call revor_whoami to verify the account and permissions.

Use browser OAuth only when the client has no secure Header/Secret setting. Do not treat OAuth as a silent fallback after an API key fails.

Clients may label the entry point as MCP, Tools, Connectors, or Custom Services. The server URL remains the same.

See Connect an MCP client for detailed steps.

You can also send this exact request to an AI assistant that can manage MCP settings:

Text
Read https://revor.ai/docs/mcp/install and install REVOR AI MCP exactly as instructed. Use https://revor.ai/api/mcp. Create an API key at https://revor.ai/my-api-keys if needed and use it only in the client's private x-api-key Secret input. Never ask me to send an API key in chat. If private secret storage or custom headers are unavailable, use REVOR AI browser OAuth. After installation, call revor_whoami to verify the connection.

What you can do

  • Create a company Webset from a natural-language target profile and page through matching companies.
  • Research companies, markets, and recent developments from public information.
  • Find business contacts by verified company domain and role.
  • Resolve customs company names and query counterparties, product categories, trade trends, and country distribution.
  • Create a complete customs trade report.
  • Check asynchronous job progress, results, and credit usage.

See MCP tool reference for the complete list.

Account access and data isolation

MCP uses the REVOR AI account represented by the API key or OAuth grant. A client can only use that account's capabilities and retrieve jobs owned by that account. It cannot read another user's data.

You can revoke or rotate an API key, or revoke an OAuth client grant from REVOR AI. The client must receive a valid credential again before it can continue.

Credits and plans

MCP uses the same capabilities, permissions, and credit rules as the REVOR AI API:

  • Billable tools consume credits according to the corresponding API pricing rules.
  • Customs company-name discovery is currently free.
  • When a completed job includes billing details, those details are the source of truth.
  • Plan permissions, account balance, and usage limits still apply.

How jobs return results

Webset creation and some research and customs queries take time. Action tools first return a job or resource ID.

  • succeeded: the result is ready.
  • queued or running: call revor_get_job with the job ID.
  • failed: review the public error code, adjust the input, or retry later.

Reading an existing job does not create another job or charge again for the original operation.

Webset creation returns webset.id and preparation_job.id. A successful preparation job means that discovery has started, not that all results are complete. Use revor_get_webset for overall progress and revor_list_webset_items to page through results.

Best practices

  • Provide an accurate company name, website domain, date range, and company role.
  • Resolve a customs company name before running a billable customs query.
  • Ask the client to continue checking revor_get_job until the job reaches a final state.
  • Use an API key only through the client's private Secret input. Never ask for or accept an API key in chat. If the client cannot securely store a custom header, use browser OAuth.