MCP FOR AI AGENTS

Connect Novasend to Codex, Claude, Cursor, VS Code, and any MCP-compatible client.

Connect Novasend to your AI agent. It finds the right endpoints, prepares your requests, and cites the sources behind its answers.

The MCP covers this site's French and English content and stays synchronized with the published pages.

Server address

The MCP is available at:

https://docs.novasend.app/mcp

Add it as novasendMcp in your client to find the Novasend tools easily.

Configure your agent

Every client connects to the same address.

Codex

codex mcp add novasendMcp \
  --url https://docs.novasend.app/mcp

Then verify the registration:

codex mcp get novasendMcp

Claude Code

claude mcp add --scope user --transport http \
  novasendMcp https://docs.novasend.app/mcp

--scope user makes the MCP available in all your Claude Code projects.

Cursor

In ~/.cursor/mcp.json:

{
  "mcpServers": {
    "novasendMcp": {
      "url": "https://docs.novasend.app/mcp"
    }
  }
}

Reload the Cursor window after saving the configuration.

VS Code

In .vscode/mcp.json:

{
  "servers": {
    "novasendMcp": {
      "type": "http",
      "url": "https://docs.novasend.app/mcp"
    }
  }
}

Claude Desktop and other MCP clients

Add https://docs.novasend.app/mcp as a remote MCP server. No authentication header, token, or secret is required.

Verify the connection

Verify the connection:

curl -sS -X POST https://docs.novasend.app/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

The response must contain four tools. If the request succeeds but your agent exposes no tool, reload the client so it reconnects to the server.

Usage examples

Simply describe what you want to integrate.

Integrate payments

Integrate Novasend payments into my application.

Integrate transfers

Integrate Novasend transfers into my application.

Handle refunds

Handle Novasend refunds.

Secure webhooks

Secure Novasend webhooks.

Guided prompts

The server publishes two MCP prompts:

Prompt	Purpose
`prepare_api_integration`	Find and prepare the right integration for a business goal.
`review_webhook_implementation`	Review webhook code against the available Novasend rules.

Clients that expose MCP prompts as slash commands generally display names close to:

/mcp__novasendMcp__prepare_api_integration
/mcp__novasendMcp__review_webhook_implementation

The exact visual command depends on the client. The canonical MCP prompt names remain prepare_api_integration and review_webhook_implementation.

Available tools

Area	Tool	Purpose
Discovery	`list_docs`	Inventory pages by collection and language.
Search	`search_docs`	Rank results and return an excerpt with its source path.
Reading	`read_doc`	Open a complete page or one section identified by its heading.
API	`get_api_operation`	Find an operation from its HTTP method and path.

Every tool is declared read-only and non-destructive in the MCP protocol.

MCP scope

The server knows:

Novasend APIs and technical guides;
Business Guide workflows;
French and English content;
endpoints, fields, examples, and rules published on this site.

It does not inspect a merchant account, read transactions, or send requests to the Novasend API. API keys remain under the control of your application and its execution environment.