Skip to main content
This guide explains what the iDenfy MCP server is, how to install it, and how to use it when you work with iDenfy.

​
What Is MCP

Model Context Protocol is an open standard that lets AI assistants connect to external tools and data sources. The iDenfy MCP server gives your AI assistant access to this documentation. Once it is connected, the assistant can search the docs and read full pages while it answers your questions or writes code.
The iDenfy MCP server is read-only. It only serves public documentation. It does not have access to your API keys, dashboard, or verification data.

​
Works with Every iDenfy Product

The MCP server covers the full iDenfy documentation, so you can use it for any product in our platform: You can ask your AI assistant a question about any of these areas and it will search the right pages for you.

​
What You Can Do with It

Search the docs

Ask questions in plain language. The assistant searches every guide and API reference for you.

Read full pages

Get the full content of a page by its path when a short snippet is not enough.

Write integration code

Ask the assistant to draft KYC, KYB, or webhook code based on the current docs.

Debug your setup

Look up error codes, webhook fields, or parameter names without leaving your editor.

​
Available Tools

The iDenfy MCP server has two tools:
ToolWhat it does
search_idenfy_documentationSearches the docs and returns page titles, paths, and short snippets.
get_page_idenfy_documentationReturns the full content of a page by its path, for example kyc/generate-token.
The usual flow is simple: search first to find the right page, then read the full page if you need more detail.

​
Install the MCP Server

You do not need to install anything on your computer. The iDenfy MCP server runs online. You only need to add the server URL to your AI assistant.
Server URL: https://documentation.idenfy.com/mcp

​
Claude Desktop

Open the Claude Desktop configuration file claude_desktop_config.json and add the server: 
{
  "mcpServers": {
    "idenfy-docs": {
      "url": "https://documentation.idenfy.com/mcp"
    }
  }
}
Restart Claude Desktop. The iDenfy tools will show up in the tool list.

​
Claude Code

Run this command in your Claude Code terminal: 
claude mcp add idenfy-docs https://documentation.idenfy.com/mcp
If you want to share the setup with your team, add it to .mcp.json in your project root: 
{
  "mcpServers": {
    "idenfy-docs": {
      "url": "https://documentation.idenfy.com/mcp"
    }
  }
}

​
Cursor

In Cursor, open Settings > MCP > Add new MCP server and paste the server URL. The server will be ready to use in every workspace.

​
ChatGPT

Custom connectors are available on ChatGPT Pro, Business, Enterprise, and Edu plans.
  1. Open Settings > Connectors in ChatGPT.
  2. Click Add custom connector.
  3. Set the name to iDenfy Docs and the MCP server URL to https://documentation.idenfy.com/mcp. Leave authentication set to None.
  4. Save the connector.
  5. In a new chat, open the tools menu and turn on the iDenfy Docs connector.
On Business or Enterprise workspaces, a workspace admin may need to allow custom connectors before you can add one.

​
Google Gemini

You can connect the iDenfy MCP server to Gemini through the Gemini CLI or Gemini Code Assist. Open your Gemini settings file (for example ~/.gemini/settings.json) and add the server: 
{
  "mcpServers": {
    "idenfy-docs": {
      "url": "https://documentation.idenfy.com/mcp"
    }
  }
}
Restart Gemini. The iDenfy tools will show up in the tool list.

​
Perplexity

Perplexity supports MCP servers through Connectors in the Perplexity desktop app and the Comet browser.
  1. Open Settings > Connectors in Perplexity.
  2. Click Add connector and choose Custom MCP server.
  3. Set the name to iDenfy Docs and the URL to https://documentation.idenfy.com/mcp.
  4. Save the connector and turn it on for the spaces where you want to use it.

​
Other Clients

Any tool that supports MCP can connect to the iDenfy server with the same URL. This includes Zed, Windsurf, the VS Code MCP extension, and custom agents. Check your tool’s documentation for the exact steps.

​
How to Use It

After you connect the server, you just talk to your assistant in plain language. You do not need to call the tools yourself. The assistant decides when to search the docs or read a full page.

​
Find Information in the Docs

How does iDenfy liveness detection work, and which parameters control it?
The assistant searches the docs, reads the right page, and tells you about active and passive liveness with the correct parameter names.

​
Generate Integration Code

Write a Python script that creates a KYC session with name and date of birth
matching, and checks the webhook signature.
The assistant uses the Create Verification Session and Callback Signing pages, so the code uses the right endpoint, the right fields, and the correct HMAC check.

​
Debug a Failing Webhook

My webhook handler returns 403 for every iDenfy request. What are the common
reasons for a signature mismatch?
The assistant opens the troubleshooting section of the callback signing page and explains raw body handling, hex encoding, and proxy issues.

​
Answer Compliance Questions

Which documents does iDenfy support for Lithuanian citizens, and what are the
NFC requirements for eIDAS high assurance?
The assistant searches the supported documents reference and the eIDAS guide and gives you one answer with the right sources.

​
Best Practices

The more detail you give, the better the search result. Instead of “How do I create a session?”, ask “How do I create a KYC session with restricted countries and a custom callback URL?”.
Ask the assistant to include the page path or link in the answer. This way you can open the source and check the answer yourself.
In an IDE like Claude Code or Cursor, let the assistant read both the iDenfy docs and your project. The code it writes will match your existing style instead of being generic.
The iDenfy MCP server does not return credentials or customer data. Keep it that way on your side: do not paste your API key or secret into the chat. Use environment variables in the code instead.
A full page uses more of the assistant’s memory than a search snippet. Let the assistant search first, and only read the full page if the snippet is not enough.
MCP reduces guesses because the assistant reads the real docs, but you should still review the code. Check signature verification, raw body handling, and how credentials are stored before you deploy.

​
Example: Build a KYC Integration from Scratch

You can build a full KYC integration in one conversation with your assistant:
1

Ask for the flow

“Explain the iDenfy KYC flow from session creation to webhook result.” The assistant describes the three steps: create a session, send the user to the UI or SDK, and handle the webhook result.
2

Create the session

“Write the Node.js code that creates a session with data matching and returns redirectUrl.” The code uses the current endpoint and field names.
3

Handle the webhook

“Add an Express handler that checks the Idenfy-Signature header against the raw body.” The code follows the pattern from the callback signing page.
4

Clean up the parameters

“Which of these parameters are already set in the dashboard by default?” The assistant checks the Create Verification Session parameter list and removes the ones you do not need.
The result is a working draft based on the current docs, not old training data.

​
Privacy and Scope

  • The MCP server only serves content from documentation.idenfy.com.
  • It does not have access to your dashboard, sessions, API keys, or customer data.
  • Your prompts and the doc content go through your AI assistant provider (for example Anthropic, OpenAI, Google, or Perplexity). Check your provider’s data policy before you share sensitive information.

​
Feedback

If a search returns old or wrong results, or if a page is missing content you need, contact support@idenfy.com. Share the prompt you used and the page you expected to find.