Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

MCP

Connect your AI agents (Cursor, VS Code, Claude, ChatGPT) directly to Delpha's Data Quality APIs using the open Model Context Protocol (MCP).

Model Context Protocol ( MCP )

Let your AI agents call the Delpha Data Quality APIs over the Model Context Protocol.

The Delpha MCP server exposes the same Data Quality tools as the Delpha API — Find, Validate, Enrich, Score — through the open MCP standard, so any MCP-compatible client (Cursor, VS Code, Claude Code, Claude.ai, ChatGPT) can use them directly. Authentication is scoped per tenant, via OAuth (recommended) or a restricted API key.

Server URL — https://mcp.delpha.ai/mcp

Auth — OAuth 2.1 with PKCE (recommended) — sign in with your Delpha account — or a restricted API key (Authorization: Bearer dlp_…) for clients that can't do OAuth. Manage your connection, API keys, and team access from app.delpha.ai.

Connect to Delpha's MCP server

Install in Cursor

To open Cursor and automatically add the Delpha MCP, click install. Alternatively, add the following to your ~/.cursor/mcp.json file. To learn more, see the Cursor documentation.

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

Install in VS Code

To open VS Code and automatically add the Delpha MCP, click install. Alternatively, add the following to your .vscode/mcp.json file in your workspace. To learn more, see the VS Code documentation.

{
  "servers": {
    "delpha": {
      "type": "http",
      "url": "https://mcp.delpha.ai/mcp"
    }
  }
}

To add Delpha to Claude Code, run the following command. To learn more, see the Claude Code documentation.

claude mcp add --transport http delpha https://mcp.delpha.ai/mcp

After adding the server to Claude, finish authentication:

claude /mcp

Available on Claude Pro, Team, and Enterprise plans. Open Settings → Connectors → Add custom connector, paste the server URL, and choose OAuth as the connection mechanism:

  • Server URL: https://mcp.delpha.ai/mcp

  • Connection mechanism: OAuth

Claude completes the OAuth handshake against Delpha's identity provider and you'll be redirected back to the connector once authorized.

Available on ChatGPT Pro, Plus, Business, Enterprise, and Education plans. Follow the OpenAI documentation for adding a custom connector, then use:

  • Server URL: https://mcp.delpha.ai/mcp

  • Connection mechanism: OAuth

MCP is an open protocol with a growing client ecosystem. Any client that supports remote MCP servers with OAuth can connect — see the client's own documentation. The minimum configuration is:

The server advertises its OAuth endpoints via the standard discovery documents at /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server, so compliant clients negotiate auth automatically.

Authentication

Delpha MCP supports two credential types, scoped per tenant:

  • OAuth 2.1 with PKCE (recommended) — every call is bound to a Delpha user account, so usage stays auditable per person. Use this whenever your client supports it.

  • API key — a restricted dlp_ API key sent as Authorization: Bearer dlp_..., for clients that can't complete an OAuth handshake. Calls are bound to the team that created the key rather than an individual user.

OAuth 2.1 with PKCE

  1. Have a Delpha account — sign up at app.delpha.ai (your team is created with it) or accept a teammate's invitation.

  2. From your MCP client, add the connector with the server URL above.

  3. Your client opens Delpha's sign-in page. Choose Continue with DelphaAI, sign in with your app.delpha.ai credentials, and approve the consent screen.

  4. The client receives an access token bound to your team's workspace — first-time connections are set up automatically, nothing to configure. The MCP server validates the token on every request and routes tool calls to the Delpha API.

Need an account? Create one at app.delpha.ai, or ask a team admin to invite you. Questions — support.api@delpha.io.

API key (fallback)

Create a key from Settings → API keys — the key is shown once at creation, so copy it right away — or straight from the connect panel at Settings → MCP. Then pass it as a bearer token instead of doing the OAuth handshake:

API keys are team-wide and, until scoped keys ship, full-privilege — treat one like a password. Store it in a secrets manager, never commit it, and revoke it immediately from Settings → API keys if it leaks. Keys expire automatically after 30 days.

Manage your MCP connection

Your MCP connection is managed from app.delpha.ai → Settings → MCP:

  • Connected clients — every client that has connected to the server (via OAuth or an API key) is listed with its name and last-seen time. Disconnect removes an OAuth client's connection; disconnecting a key-based client also revokes the API key behind it. Verify checks a fresh connection so you can confirm your setup end to end.

  • MCP access (team admins) — a team-wide switch that turns MCP off for both authentication methods. Changes apply within about a minute.

  • API keys — created and revoked from Settings → API keys; each key's last-used time is shown there.

Usage & credits

Every tool call draws from your team's Delpha credit balance — the same metering as calling the Delpha API directly, and new teams start with free credits. When the balance reaches zero, tool calls return a payment-required error until the team is topped up. Track your balance and history at Settings → Billing and Settings → Usage.

Tools

The MCP server exposes 16 tools, grouped by workflow below. Every tool maps to a Delpha API endpoint — click API reference on any row to see the full request/response schema on the existing API page.

Find & Validate

MCP tool
Objective
Description
Live lookup
API reference

findAndValidateEmail

Recommend / Validate

Find, validate & qualify email

Yes

email

findAndValidateLegalID

Recommend / Validate

Find & validate legal ID

Yes

legal-id

findAndValidateLinkedin

Recommend / Validate

Find & validate LinkedIn URL

Yes

linkedin

findAndValidateName

Validate

Find & validate person name

Yes

name

findAndValidatePhone

Validate

Find & validate phone number

Yes

phone

findAndValidateUltimateParent

Recommend / Validate

Find & validate ultimate parent

Yes

ultimate-parent

findAndValidateWebsite

Recommend / Validate

Find & validate website

Yes

website

LinkedIn enrichment

MCP tool
Objective
Description
Live lookup
API reference

submitLinkedinImport

Enrich

Submit LinkedIn import job

Yes

linkedin-import

Result polling

MCP tool
Objective
Description
Live lookup
API reference

getEmailResult

Recommend / Validate

Get email validation result

No

email

getLegalIDResult

Recommend / Validate

Get legal ID validation result

No

legal-id

getLinkedinImportResult

Enrich

Get LinkedIn import result

No

linkedin-import

getLinkedinResult

Recommend / Validate

Get LinkedIn validation result

No

linkedin

getNameResult

Validate

Get name validation result

No

name

getPhoneResult

Validate

Get phone validation result

No

phone

getUltimateParentResult

Recommend / Validate

Get ultimate-parent result

No

ultimate-parent

getWebsiteResult

Recommend / Validate

Get website validation result

No

website

Live lookup flags tools that trigger an external lookup against third-party data sources (equivalent to MCP's openWorldHint=true). All tools are read-only and safe to retry — re-submitting a job mints a fresh job_id with no side effects.

Tool behavior

Most Delpha tools follow an asynchronous submit → poll pattern:

  1. The agent calls a findAndValidate* tool with the input data. The server returns a job_id immediately.

  2. The agent calls the paired get*Result tool with that job_id to fetch the result. While the job is still running, the result tool returns status_code=202 and the agent retries; on completion it returns status_code=200 with the full result envelope.

Example pair: findAndValidateEmail → getEmailResult. Typical end-to-end latency is a few seconds.

Every result envelope shares the same shape: { message, status, status_code, result, process_time }. The result object is entity-specific — see the linked API page for each tool for the exact fields and scoring semantics.

Feedback

We're actively adding tools and refining descriptions based on how agents actually use them. If you have feedback, hit a rough edge, or want to see a new capability, email us at support.api@delpha.io.

Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the ask query parameter:

The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

We're actively adding tools and refining descriptions based on how agents actually use them. If you have feedback, hit a rough edge, or want to see a new capability, email us at support.api@delpha.io.

PreviousCompany

Last updated

Was this helpful?