Skip to content
Novadesko Documentation
Guide Demo
English
Open the app

MCP connector overview

What the official Novadesko connector for Claude, ChatGPT and Gemini does, its address, compatible clients and how a connection works.

Updated on 23/10/2026 Edit this page Open in the full documentation

Novadesko publishes an official MCP (Model Context Protocol) server. It lets an AI assistant read a Novadesko company's data and prepare actions (quotes, invoices, customers, reminders...), always with the user's explicit consent. The same tools and rules also power Nova AI, the assistant built into Novadesko.

Server address

Official address to paste into your AI client: https://mcp.novadesko.com.

  • https://mcp.novadesko.com/mcp is also accepted.
  • The former address https://web.novadesko.com/mcp keeps working for existing connections.
  • The same access token is valid on all three addresses.

HTTP transport: JSON-RPC 2.0 messages sent with POST. Accepted protocol versions: 2025-06-18, 2025-03-26, 2024-11-05. The mcp.novadesko.com domain only serves MCP and OAuth: the rest of the application is not exposed there.

Compatible clients

ClientStatusNote
Claude (claude.ai, desktop app, mobile app)availableCustom connector; depends on your Claude plan
Claude Codeavailableclaude mcp add --transport http
ChatGPTavailableDeveloper mode connectors
Gemini CLIavailablegemini mcp add --transport http
Gemini EnterpriseGoogle previewClient ID created in Novadesko by the administrator
Consumer Gemini appnot available in BelgiumAnnounced by Google only in the US, personal accounts with a paid plan

Any other MCP client that supports OAuth 2.1 with dynamic registration can connect. Its connections appear in Novadesko on the Integrations, Claude page so they stay revocable.

How a connection works

  1. The client calls https://mcp.novadesko.com without a token: 401 response with a WWW-Authenticate header pointing to the OAuth metadata.
  2. The client reads the metadata, registers itself (dynamic registration) and opens the Novadesko authorization page.
  3. The user signs in to Novadesko if needed, picks one company and the permissions granted, then clicks Authorize.
  4. The client exchanges the code for an access token (PKCE S256) and calls initialize then tools/list.
  5. Reads run directly. Any write or send goes through a prepare_* tool that returns a preview and a confirmation token, then through confirm_action once the user agrees.
Novadesko authorization screen
The authorization screen (in French): one company, Read, Create and edit, Send emails and SMS permissions.

What the server does not expose

  • no document sending over Peppol (Peppol sending stays manual in Novadesko);
  • no access to files, the system, the database or the Novadesko admin;
  • no company other than the one chosen at authorization;
  • no account deletion or password change.
Note

The company always comes from the OAuth connection, never from arguments. Parameters shop_id, company_id, user_id and similar are silently removed.

See also