Skip to main content

Add your own MCP server

With a custom MCP server, you connect AI-Public to a case management system, archive, data source, or other specialized service. First choose which transport fits the place of use.

Choose the right transport​

TransportWebMobileDesktopUse
Streamable HTTPYesYesYesRecommended for hosted servers
stdioNoNoYesLocal processes and desktop integrations
SSEExisting configurations onlyExisting configurations onlyYesDeprecated transport; choose Streamable HTTP for new servers

Requirements for Streamable HTTP​

Use the full public endpoint, including the MCP path, for example:

https://mcp.organization.nl/mcp

The endpoint must use HTTPS, be reachable via public DNS without redirects, and respond to a valid MCP initialize handshake. Usernames and passwords do not belong in the URL. Local addresses, private network addresses, and cloud metadata endpoints are blocked.

Add a server​

  1. Open Preferences → Tools.
  2. Choose Add tools or Add MCP server. You only see this button if you have MCP access.
  3. Review the available presets.
  4. Choose Add your own MCP server.
  5. Enter the name, full endpoint, and authentication method.
  6. Save the configuration and wait for the connection check.
  7. Enable the server for your default toolset.

An administrator can register a server for the entire environment via Administration → Tools → MCP.

Authentication and secrets​

AI-Public supports connector OAuth and static secrets. OAuth tokens, refresh tokens, API keys, and passwords are stored in server-only storage. A chat receives only the registered connectorId, never the secret configuration.

If the URL or authentication changes, the new configuration is checked again first. If that check fails, a previously approved configuration can remain active until the issue is resolved.

Tool permissions and information security​

Only make tools available that users actually need. An MCP server can offer both read and write actions. AI-Public filters discovered tools against a server-side allowlist and checks environment, owner, and role on every use. The organization remains responsible for appropriate scopes, logging, retention periods, and authorization in the source system.

Local desktop servers​

You install a local stdio server in the desktop app. Command, arguments, environment keys, and requested access are limited and shown before approval. Secrets are encrypted locally.

Troubleshooting​

  • Endpoint unreachable: check HTTPS, DNS, firewall, and the full /mcp path.
  • Reconnect required: renew OAuth consent or the stored secret.
  • Belongs to a different environment: register the connector again within the current environment.
  • No tools visible: check allowlist, role access, and active status.
  • Works only on desktop: the server probably uses stdio or a local address.

Development resources​

See also​

When editing, the registered server configuration is retrieved. The stored key remains hidden: leave the key field empty to keep it. If the URL or authentication method is different, reconnecting is required. An error in one MCP tool does not mean that all tools from that server are inaccessible.

On this page