MCP server for e-signing with BankID – DealBuilder for AI agents

As businesses build AI agents and AI-based workflows into their own systems, the question also arises of how electronic signing can be connected to AI through MCP.

DealBuilder has an MCP server for electronic signatures and e-signing with BankID. With it, AI assistants and AI agents can create documents, send them for signing with BankID, track signing status and fetch fully signed documents, right from the conversation with the user.

The DealBuilder API and webhooks can also be used to connect document creation, electronic signing and document status to your own systems and AI-based workflows.

What is MCP

MCP stands for Model Context Protocol. It is an open standard that lets AI assistants and AI agents connect to external systems through defined tools.

Instead of only answering questions, the AI assistant can get access to actions in other systems. For example, it can fetch information, create a document or follow up a signing process.

MCP was created to standardise how this connection is set up. The actions themselves are still performed by the system the MCP server is connected to – for example through an API.

What DealBuilder MCP server can do

• Create quotes and agreements and send them for signing. The recipient signs with BankID themselves.
• Track signing status and fetch fully signed documents
• Look up the product catalogue by product code, name and price
• Read the full agreement: order lines with product code, discount and cost, salesperson, totals, custom fields, template name, event log, agreement text and terms
• Each user signs in themselves, and the permissions in DealBuilder control what the AI assistant can see and do: all agreements as an administrator, all agreements on the account, or only their own
• Separate keys for agents and automations without a browser, which can be restricted, for example to read-only
• Your business controls per user and per key who can create, send and change agreements
• Administrators can see who has connected

Can DealBuilder be used with AI today

Yes. DealBuilder MCP server connects AI assistants that support MCP, such as Claude and ChatGPT, to DealBuilder.

The DealBuilder API can also be connected directly to an AI solution. For businesses that already have an AI setup that can use APIs, the connection can be simple to establish. In one specific customer setup, DealBuilder was connected to the customer's existing AI setup in five minutes. How long it takes will vary with the solution and which functions are to be made available.

Among other things, an AI assistant can create documents, fetch information, check signing status and follow up signers. The user can then chat with an AI assistant that performs approved actions, instead of going through each step manually.

How the connection works in practice

An AI assistant connects to DealBuilder through the MCP server:

AI assistant → DealBuilder MCP server → DealBuilder

Systems that do not use MCP can connect directly to the DealBuilder API:

AI assistant → DealBuilder API → DealBuilder

The MCP server makes the actions in DealBuilder available as tools the AI assistant understands and can use.

Your business decides which actions the AI assistant gets access to. For example, manual approval can be required before a document is sent for signing.

Webhooks can then notify you when the document's status changes, so that the AI assistant or another system can follow up the process.

What an AI assistant can do with DealBuilder

With DealBuilder MCP server, you can ask for actions in plain language.

Examples of requests:

• “Find the latest document we have with customer X”
• “Which agreements are still waiting for signature”
• “Show all quotes that were sent this month”
• “Find all contracts signed by customer X”
• “Create a quote based on this template”
• “Add the customer as a signer”
• “Send the document for signing”
• “Send a reminder to the signer”
• “Which products and order lines are registered in the agreement with customer X”
• “Revoke the document that was sent by mistake”

What the AI assistant is allowed to do depends on the user's permissions in DealBuilder.

The AI assistant can also assess the agreement text itself, for example answer whether the contract is a standard agreement or contains special terms. The MCP server gives access to the full agreement, including the agreement text, terms and order lines.

DealBuilder API and webhooks

DealBuilder MCP server uses the DealBuilder API to perform the actions in DealBuilder. Businesses that want to build their own integrations can use the API directly.

Webhooks notify you when a document is sent, opened, signed or revoked.

See the API documentation and the webhook documentation.

Are API and MCP the same

No. An API and MCP solve different parts of the integration.

An API describes how other systems can send and receive data from DealBuilder. MCP describes how functions and data sources can be made available to AI assistants through a standardised interface.

The API performs the operation itself in DealBuilder. The MCP server makes selected operations available as tools the AI assistant can understand and use.

In short

DealBuilder has an MCP server for e-signing with BankID. It connects AI assistants to DealBuilder, so they can create, find, send and follow up documents through a conversation with the user.

Each user signs in themselves, and the permissions in DealBuilder control what the AI assistant can see and do.

The DealBuilder API and webhooks can also be used for your own integrations and AI-based workflows.