MCP
Connect Claude, Cursor and other AI agents to Dropcontact through the MCP server.
The Dropcontact MCP (Model Context Protocol) server lets an AI assistant such as Claude, ChatGPT or Cursor use Dropcontact directly from a conversation.
You can connect to our MCP server natively like Claude Desktop or by using compatible clients such as Cursor, Windsurf, Visual Studio Code, and others. There is nothing to install: the server is hosted by Dropcontact.
It provides tools to:
- Enrich a contact from:
- First name + last name + company
- Full name + company
- LinkedIn URL
- Validate an email address
- Check your remaining credits
How it works
An enrichment or email validation runs in two steps:
- A first tool submits the request and returns a request ID. This step uses 1 credit, given back if no email is found (see Credits Policy).
- A second tool uses this request ID to retrieve the result. It usually takes 10 to 60 seconds, and up to 3 minutes.
Your AI assistant chains both steps for you: you only need to ask in plain language.
Example prompts
- "Find the professional email of Marie Dupont, who works at Dropcontact."
- "Enrich this LinkedIn profile: https://www.linkedin.com/in/mariedupont"
- "Is contact@example.com a valid email address?"
- "How many Dropcontact credits do I have left?"
Setup instructions
Remote MCP connections are still early and the connection may fail or require multiple attempts. If you experience issues, try restarting your client or disabling and re-enabling the Dropcontact MCP server.
To connect to the Dropcontact MCP server, use the following configuration in your compatible client:
- Server URL: https://mcp.dropcontact.com/mcp
- Authentication: Handled automatically via OAuth (recommended), but we offer other ways (see below). With an API key, use the same key as for the API, in the
Authorization: Bearer <apiKey>header instead ofX-Access-Token.
Claude
Individual (Claude Desktop)
- Go to Settings > Connectors and click Add connector
- Enter the URL: https://mcp.dropcontact.com/mcp
- Complete the OAuth flow in the browser that opens
Team, Enterprise
- Go to Settings > Integrations and click Add more
- Enter:
- Integration name: Dropcontact
- Integration URL: https://mcp.dropcontact.com/mcp
- Enable the tools in your chats
Cursor
Cursor supports multiple connection methods. Choose the one that fits your setup:
- CTRL/CMD P and search for View: Open MCP Settings
- Click on New MCP Server
- Add the Dropcontact configuration to the json configuration file
OAuth (recommended)
Authentication is handled automatically in the browser.
{
"mcpServers": {
"dropcontact-oauth": {
"url": "https://mcp.dropcontact.com/mcp"
}
}
}API key (direct URL)
Replace <apiKey> with your Dropcontact API key, available in the Dropcontact app.
{
"mcpServers": {
"dropcontact-token": {
"url": "https://mcp.dropcontact.com/mcp",
"headers": {
"Authorization": "Bearer <apiKey>"
}
}
}
}OAuth via npx mcp-remote
Use this if your Cursor version does not support native remote MCP.
{
"mcpServers": {
"dropcontact-npx-oauth": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.dropcontact.com/mcp"
]
}
}
}API key via npx mcp-remote
Replace <apiKey> with your Dropcontact API key, available in the Dropcontact app.
{
"mcpServers": {
"dropcontact-npx-token": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.dropcontact.com/mcp",
"--header",
"Authorization: Bearer ${API_TOKEN}"
],
"env": {
"API_TOKEN": "<apiKey>"
}
}
}
}ChatGPT
MCP servers can be added via the web app and are then available across all ChatGPT clients.
- Go to Settings > Apps > Create app
- Enter the following:
- MCP Server URL: https://mcp.dropcontact.com/mcp
- Authentication: OAuth
- Click Create and complete the OAuth flow in the browser that opens
- Once authenticated, the Dropcontact tools are available in your chats
Others
Many other tools now support MCP servers. You can configure them to use Dropcontact's MCP server with the following settings:
OAuth (recommended)
Authentication is handled automatically in the browser.
{
"mcpServers": {
"dropcontact-oauth": {
"url": "https://mcp.dropcontact.com/mcp"
}
}
}API key (direct URL)
Replace <apiKey> with your Dropcontact API key, available in the Dropcontact app.
{
"mcpServers": {
"dropcontact-token": {
"url": "https://mcp.dropcontact.com/mcp",
"headers": {
"Authorization": "Bearer <apiKey>"
}
}
}
}OAuth via npx mcp-remote
Use this if your client does not support native remote MCP.
{
"mcpServers": {
"dropcontact-npx-oauth": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.dropcontact.com/mcp"
]
}
}
}API key via npx mcp-remote
Replace <apiKey> with your Dropcontact API key, available in the Dropcontact app.
{
"mcpServers": {
"dropcontact-npx-token": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.dropcontact.com/mcp",
"--header",
"Authorization: Bearer ${API_TOKEN}"
],
"env": {
"API_TOKEN": "<apiKey>"
}
}
}
}Troubleshooting
| Problem or message | What to do |
|---|---|
| The connection fails or the OAuth window does not open | Restart your client, or disable and re-enable the Dropcontact MCP server, then connect again. |
The Dropcontact session has ended | Reconnect the Dropcontact connector in your client and sign in again. |
Dropcontact rejected this API key | Check that your API key is still active in the Dropcontact app. |
Your Dropcontact account is not yet set up for MCP | Sign in once to the Dropcontact app to activate your account, then try again. |
You have no remaining enrichment credits | Add credits to your account. If you still have credits, contact support@dropcontact.com: your API access may not be enabled. |
Timeout while waiting for enrich contact response | The result was not ready after 3 minutes. Ask your AI assistant to retrieve the result again with the same request ID, or retrieve it via the API once processing is complete. No extra credit is used. |
Dropcontact could not authenticate this request right now | Try again in a moment. |
Too many requests. Please wait a moment before trying again. | Wait a few seconds and try again. |
Dropcontact request failed, Dropcontact could not process this request or Dropcontact enrich request failed | Something went wrong on our side. Try again later. If it keeps happening, contact support@dropcontact.com. |
Failed to retrieve credits | Try again later. |
Still stuck? Contact us at support@dropcontact.com.