MCP server: use your online forms from AI agents

In short

Address: https://www.form-provider.com/mcp (or /mcp on your own eForms server), MCP over Streamable HTTP.
Sign-in: through phone.codeb.io with two permissions, "fill in forms" and "submit forms"; revoke any time in "Your agents".
Safety: AI apps act at most as "user", submissions are sealed by the server and never signed with your key.

Connecting an AI app

In your AI app, add an MCP server (often called a connector or custom integration) with the address https://www.form-provider.com/mcp, or https://<your server>/mcp for your own eForms server.
The app opens the sign-in of phone.codeb.io. Sign in with your CodeB account.
The consent page names the form server ("CodeB eForms – www.form-provider.com") and two permissions: fill in forms and submit forms. Tick what the app may do and allow it.
Ask the app, for example: "Which forms are there?", "Fill in the contact form with these details and give me the link", or "Check these values against the order form".

Tools for developers that let you enter a token can also send the access token of a configured sign-in server in the header Authorization: Bearer …, exactly as for the REST API.

Sign-in and permissions

Fill in forms (scope forms): list forms, read fields, check values, fill the PDF as a draft, create prefilled links.
Submit forms (scope forms_submit): in addition, submit forms and create e-invoices. Both send e-mails.
Your forms, your role: the form server receives your e-mail address and account name, so the forms of your group and your role apply. An AI app acts at most with the role "user", never as administrator.
Only for this server: the app receives tokens for this form server's MCP address only. They are not valid for other servers or for the REST API.
Revoke at any time: remove the app in "Your agents" at phone.codeb.io. The form server checks every token with the sign-in server and refuses it within 30 seconds.

Tools

What the AI app can do. Each tool calls the REST API of the same server with your sign-in, so the same checks apply.

Tool	What it does	Permission
`whoami`	Shows the account the form server sees: user name, role, group, sign-in server.	fill in forms
`list_forms`	Lists the forms you may use, optionally filtered by a search text.	fill in forms
`get_form`	One form with its input fields (name, type, label, required, options, check rule) and a JSON Schema of the values.	fill in forms
`validate_form`	Checks values against the fields and rules; nothing is filled or sent.	fill in forms
`fill_form`	Fills the form and returns the PDF as a draft; nothing is submitted, no e-mail.	fill in forms
`create_prefilled_link`	A link that opens the web form with the values filled in, so you check and submit it in the browser.	fill in forms
`submit_form`	Submits the form: sealed PDF, e-mails to you and the form owner. Cannot be undone.	submit forms
`create_einvoice`	ZUGFeRD / Factur-X or XRechnung e-invoice from structured data; "preview" returns the PDF only, "submit" processes and e-mails it.	submit forms (preview: fill in forms)

What stays with you

Nothing is sent without you: submit_form and create_einvoice are marked as tools that send, and the app is told to ask you first. With only "fill in forms" the app cannot send anything; it gives you a prefilled link and you submit yourself.
Sealed, not signed in your name: forms submitted through an AI app are sealed by the server. They are never signed with your own key; that needs you in the browser or in CodeB Wallet.
Same rules as everywhere: field checks, rate limits, the daily submission limit and the logging of the REST API apply unchanged.
Your data: the form server keeps no conversation; it receives only the tool calls and their values. What the AI app stores is up to its provider.

On your own eForms server

The MCP server is part of every CodeB eForms Server, hosted or in your own data centre. On the settings page (group REST API) you find "MCP server for AI agents" (on by default), "MCP sign-in server for AI apps" and "Public MCP address".

For the sign-in through phone.codeb.io, Aloaha registers the exact address of your MCP server (for example https://forms.example.com/mcp) on request (info@aloaha.com); then enter https://phone.codeb.io/mcp-auth as MCP sign-in server. Until then, apps connect with a bearer token.

Technology

Protocol: MCP over Streamable HTTP, JSON-RPC 2.0, JSON answers, no sessions; protocol versions 2025-06-18, 2025-03-26 and 2024-11-05.
Authorization: protected resource metadata (RFC 9728) at /.well-known/oauth-protected-resource/mcp names the authorization server https://phone.codeb.io/mcp-auth; tokens are issued for this exact resource (RFC 8707) and checked by token introspection (RFC 7662), cached at most 30 seconds.
Testing: the MCP Inspector (npx @modelcontextprotocol/inspector) connects to the address and runs the sign-in. With a token:

curl -X POST https://www.form-provider.com/mcp \
  -H "Authorization: Bearer <access token>" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Questions and answers

Which AI apps can use the forms?

Apps that support remote MCP servers over Streamable HTTP with OAuth sign-in, or that let you enter a bearer token. Add https://www.form-provider.com/mcp (or the address of your own eForms server) as MCP server or connector.

Can the AI submit a form without asking me?

The form server marks submit_form and create_einvoice as tools that send and tells the app to ask you first; whether it asks is up to the app. To be sure, allow only "fill in forms": then the app prepares the form and gives you a prefilled link, and you submit it yourself.

Is a form submitted by an AI app signed with my key?

No. Forms submitted through an AI app are sealed by the server. A signature with your own key needs you in the browser or in CodeB Wallet.

How do I stop an app?

Remove it in "Your agents" at phone.codeb.io. The form server refuses its token within 30 seconds.

Is this the MCP server of phone.codeb.io?

No. phone.codeb.io has its own MCP server for signing requests, age checks and meetings. Both use the same sign-in, and an app can be connected to both.

Last updated: 27 October 2026