Connect your AI assistant

The RevenueBase MCP server lets your AI assistant search business contacts, inspect audience coverage, enrich known email addresses, and verify email deliverability using your RevenueBase account.

Before you connect

You need a RevenueBase account and an AI client that supports remote MCP connections over Streamable HTTP with OAuth. Available tools and data depend on your account access and plan. Sign in to the RevenueBase app once with the account you will connect. This links your sign-in to your RevenueBase account.

Connect in Claude

Add the connector

Open Claude’s connector settings and choose Add custom connector. Enter the production server URL:

https://mcp.revenuebase.ai/mcp

Choose Connect and complete the RevenueBase sign-in and authorization flow with the same account you used in the app. Your client handles OAuth; you do not paste an API key into the connector.

Check the connection

Start a conversation with the connector enabled. Ask:

List the fields available for a RevenueBase contact search.
Do not retrieve contact records.

Field discovery confirms access without retrieving contact rows.

Connect another MCP client

Use the same server URL and complete your client’s RevenueBase OAuth flow. For clients that accept an MCP configuration file, the connection entry is:

{
  "mcpServers": {
    "revenuebase": {
      "url": "https://mcp.revenuebase.ai/mcp"
    }
  }
}

Your client must support account OAuth for remote MCP servers. This connection uses your RevenueBase sign-in; a REST API key alone cannot authenticate it.

https://docs.revenuebase.ai/mcp is the separate documentation search server. Use https://mcp.revenuebase.ai/mcp for contact data and email verification.

Tools and credits

Tool	Result	Documented credit behavior
`list_columns`	Searchable fields and their types	Free
`column_values`	Values for an enumerable field	Free
`count_contacts`	Matching contact totals	Free
`audience_insights`	Aggregate reachability and coverage	Free
`search_contacts`	A bounded contact preview; default 20, maximum 100 records	Returned rows may use credits according to your plan
`enrich_email`	Contact details for up to 25 supplied emails	Returned matches may use credits according to your plan
`verify_email`	Valid, Invalid, or Unknown for one email	One credit for Valid or Invalid; none for Unknown
`verify_emails_batch`	A verification job for up to 1,000 emails	One credit per Valid or Invalid result as the job runs
`job_status`	The status of one of your verification jobs	Free
`list_verification_jobs`	Your verification jobs and totals	Free

Review the requested operation and credit cost before authorizing contact retrieval, enrichment, or email verification. Batch verification creates a job; completed results are available in the RevenueBase app.

Troubleshooting

Sign-in succeeds but tools reject access: sign in to the RevenueBase app with the same account, then reconnect the MCP server.
Email tools are absent: check your account’s access to email verification. Tool availability depends on the signed-in account.
Insufficient credits: check your balance and plan in the RevenueBase app. Free discovery and aggregate tools can still operate without paid credits.
Repeated authorization errors: confirm the connector URL is exactly https://mcp.revenuebase.ai/mcp, then reconnect through your client.

For help, contact support@revenuebase.ai. Read the privacy policy and terms of service for data handling and permitted use.

Getting Started

Setting Up Your Integration

Using Gigasheet

Resources

Connect your AI assistant

Before you connect

Connect in Claude

Connect another MCP client

Tools and credits

Troubleshooting

​Before you connect

​Connect in Claude

​Connect another MCP client

​Tools and credits

​Troubleshooting

Before you connect

Connect in Claude

Connect another MCP client

Tools and credits

Troubleshooting