Custom apps and MCP
Use Add your own app when the service you need has an API or MCP server but no listed connection card. A custom connection belongs to you; adding it does not publish its access to your company.
Prepare the connection
Get the service's official website or API address and, when needed, a credential with the permissions appropriate to your task. For an MCP server, use the endpoint supplied by its operator. Check what information and actions that server exposes before authorizing it.
The address must use public HTTPS. Private network, local and internal addresses are not accepted by this connection form. A service requiring a different network or authentication arrangement may need another supported setup.
Add the app
- Open Connections and choose Add your own app.
- Enter an App name.
- Supply the Website or API address so Milo knows which service to use.
- Enter the API key or access token, if required, in its dedicated field.
- Choose Add app, then test a small read from a known record.
Do not place credentials in an ordinary chat message. A saved connection is not proof that every API action works: the service may require additional scopes, a particular API plan or an authentication flow this setup does not supply.
Make the first task specific
Use the app I just connected to find the named project. Report its current status with a source link. Do not change records or send messages.
If the key is refused or expires, add the same app name again with the replacement key. Re-adding the same named app updates its connection. Removing the app stops future access through that entry; it does not undo provider actions already completed.
A custom connection is distinct from a provider officially listed in the connection directory. Availability of a generic API path should not be treated as a promise of a managed connector for every service.