Adding a Custom 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 the transport that fits the place of use.
Choose the Right Transport
| Transport | Web | Mobile | Desktop | Usage |
|---|---|---|---|---|
| Streamable HTTP | Yes | Yes | Yes | Recommended for hosted servers |
| stdio | No | No | Yes | Local processes and desktop integrations |
| SSE | Existing configurations only | Existing configurations only | Yes | Deprecated 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.com/mcp
The endpoint must use HTTPS, be reachable via public DNS without redirects, and respond with a valid MCP initialize handshake. Usernames and passwords should not be included in the URL. Local addresses, private network addresses, and cloud metadata endpoints are blocked.
Adding a Server
- Open Preferences → Tools.
- Choose Add Tools or Add MCP Server.
- Review the available presets.
- Select Add a Custom MCP Server.
- Enter the name, full endpoint, and authentication method.
- Save the configuration and wait for the connection check.
- Enable the server for your default toolset.
An administrator can register a server for the entire environment via Admin → 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 only receives the registered connectorId, never the secret configuration.
If the URL or authentication changes, the new configuration is first re-checked. If that check fails, a previously approved configuration can remain active until the issue is resolved.
Tool Permissions and Information Security
Only enable tools that users truly 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 each 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 not reachable: check HTTPS, DNS, firewall, and the full
/mcppath. - Reconnection required: renew OAuth consent or the stored secret.
- Belongs to another environment: re-register the connector within the current environment.
- No tools visible: check allowlist, role access, and active status.
- Works only on desktop: the server likely uses stdio or a local address.
