Overview
This section provides an overview of the Documentation Assistant, including features, benefits, and privacy and security information. The Nuvei Documentation Assistant is exposed as a public Model Context Protocol (MCP) server at: https://mcp.nuvei.com/sse
About the Documentation Assistant
The Nuvei Documentation Assistant is an AI-powered tool that helps you find answers about Nuvei’s payment platform directly inside the AI coding assistant you already use.
You can connect this MCP server to your AI-powered agent (for example: GitHub Copilot, Claude Code, Cursor, Windsurf, and so on). Once connected, you can ask questions or give directives in natural language and obtain accurate, up-to-date answers sourced from Nuvei’s official documentation.
Typical prompts:
- “How do I integrate Nuvei’s payment SDK?”
- “Show me how to process a credit card payment.”
- “What parameters does the payment API accept?”
- “How do I handle webhook notifications?”
- “Give me an example of a 3D Secure transaction.”
Features
- Instant answers – No more searching manually through long documentation pages. Ask a question and get a clear, focused answer in seconds.
- Source citations – Every answer includes links to Nuvei’s official documentation so you can verify information and dive deeper when needed.
- Always up to date – The Documentation Assistant uses the latest Nuvei docs, so you’re always working with current information.
- Context-aware help – The Documentation Assistant understands payment terminology and common integration flows, and can help with (for example):
- API integration steps
- Code examples
- Best practices
- Troubleshooting common issues
- SDK usage patterns
Benefits
This section outlines key benefits of using the Documentation Assistant.
- Save time – Find answers in seconds instead of searching through documentation manually.
- Reduce errors – Answers are grounded in Nuvei’s official docs, helping you implement features correctly.
- Learn faster – Explanations and examples help you understand payment concepts and Nuvei-specific flows quickly.
- Build confidently – You always have quick access to best practices, working examples, and verified information.
Privacy and Security
This section provides information about privacy and security in relation to the Documentation Assistant.
- Secure queries – Your questions are processed securely. The MCP server is read-only over HTTPS and only serves documentation content.
- No payment data required – You should never send real card data, credentials, or other sensitive information within your prompts. Use test data or describe the issue in abstract terms.
- No sensitive data stored – Nuvei does not store payment data or sensitive personal information from your prompts. Prompt content may be used in an aggregated/anonymized way to improve answer quality and documentation coverage.
- Enterprise-grade standards – The Documentation Assistant is built to align with Nuvei’s existing security and compliance standards. It is a safe, read-only companion to your integration work.
The Nuvei Documentation Assistant gives your existing AI coding tools deep knowledge of Nuvei’s platform. Connect the MCP server once and your agent becomes a Nuvei-aware copilot that helps you integrate faster, with fewer errors, and with much less time spent hunting through docs.
How It Works – High-level Flow
- Confirm that your AI agent (such as Copilot, Claude, Cursor, Windsurf, and so on) supports the Model Context Protocol (MCP).
- Configure your AI agent to use the Nuvei MCP server at https://mcp.nuvei.com/sse.
- When you ask Nuvei-related questions, the agent calls the MCP server, which:
- Searches Nuvei documentation.
- Returns relevant sections and metadata.
- The AI agent uses the context to generate an answer, with links to the documents.
Getting Started – Connecting the MCP Server
The following are examples of configurations for popular environments and can be considered as templates. Paths and user-interfaces may vary between versions and setups.
1 – Generic MCP Configuration Pattern
Most MCP-compatible tools use a JSON configuration that appears typically as:
{
"nuvei-docs": {
"url": "
",
"type": "sse"
}
}
- The
key namevalue (nuvei-docs) is used by your AI agent to refer to the server. - The
urlvalue is Nuvei’s public MCP endpoint. - The
typevalue is the transport. For this server, usesseunless your client explicitly requires a different value.
2 – Example for VS Code with an MCP-enabled Agent (for example, GitHub Copilot, Claude)
If your VS Code setup supports MCP via an mcp.json file, you can add Nuvei as follows:
a. Create or edit .vscode/mcp.json in your workspace:
{
"servers": {
"nuvei-docs": {
"url": "https://mcp.nuvei.com/sse",
"type": "sse"
}
}
}
b. then:
- Reload VS Code.
- Open your AI chat (such as Copilot Chat, Claude extension, and so on).
- Ask a Nuvei question (for example, “How do I process a credit card payment with Nuvei?”).
c. Depending on your agent, you might need to:
- Select the Nuvei tools from a user-interface list
or - Mention the tool explicitly (for example, ‘@nuvei’ or by enabling the “nuvei-docs” server in settings).
3 – Example for Cursor
Cursor uses a global MCP config file, typically at ~/.cursor/mcp.json.
a. Add the Nuvei server:
{
"mcpServers": {
"nuvei-docs": {
"url": "https://mcp.nuvei.com/sse",
"type": "sse"
}
}
}
b. Restart Cursor.
c. Open the chat or agent panel and ask a Nuvei-related question. Cursor uses the nuvei-docs MCP server behind the scenes to pull in documentation context.
4 – Example for Claude Desktop or Claude Code
Claude typically uses a claude_desktop_config.json file (location varies by operating system) with an mcpServers section.
a. Add the following:
{
"mcpServers": {
"nuvei-docs": {
"url": "
",
"type": "sse"
}
}
}
b. Save.
c. Restart Claude Desktop or the Claude Code plugin.
d. Ask Nuvei questions in the chat (for example: “What parameters does the Nuvei payment API accept?”).
5 – Example for Windsurf
Windsurf usually exposes the MCP configuration via a graphic user-interface and/or an underlying mcp_config.json.
a. In the raw config, add the following:
{
"mcpServers": {
"nuvei-docs": {
"url": "https://mcp.nuvei.com/sse",
"type": "sse"
}
}
}
b. Reload Windsurf.
c. Use the Windsurf AI agent (such a Cascade) to ask Nuvei questions.
6 – For Other MCP-compatible Tools
If you are using any other MCP-compatible tool (such as a custom internal agent), do the following:
- In the MCP-compatible tool, refer to MCP-configuration documentation about how to add an MCP server.
- Add a server entry using the following parameters and values:
- Name:
nuvei-docs url: https://mcp.nuvei.com/ssetype(transport):sseor whichever remote transport the client expects; if the client does not support SSE directly, refer to the client documentation for more information).
- Name:
- For the agent to pick up the new server, restart or reload the agent.
- Any Nuvei-related question your agent sends to the nuvei-docs server are answered using Nuvei documentation.
Using the Documentation Assistant
After your MCP server is configured and your agent recognizes nuvei-docs, the workflow is as follows:
- Open your AI chat panel in your IDE/agent.
- Ask a question or provide a directive in natural language, for example:
- “How do I integrate Nuvei’s payment SDK in Node.js?”
- “Show me how to process a credit card payment with Nuvei.”
- “What parameters does the Nuvei payment API accept?”
- “How do I handle webhook notifications for Nuvei?”
- The agent does the following:
- Calls the Nuvei MCP server.
- Retrieves relevant documentation sections.
- Generates an answer and usually includes inline explanations and documentation links.
Example Prompts
The following are examples of prompts you can use:
Integration
- “How do I initialize the Nuvei payment form?”
- “What’s the process for tokenizing a credit card?”
- “Show me how to implement Apple Pay with Nuvei.”
Troubleshooting
- “Why is my payment failing with error code 1001?”
- “How do I test payments in sandbox mode?”
- “What should I do if a webhook isn’t received?”
API Reference
- “What are the required fields for a payment request?”
- “How do I refund a transaction?”
- “Which response codes should I handle for declines?”