- Internal APIs and custom business systems
- Proprietary tools specific to your MSP
- Third-party services not yet in the built-in integration catalog
How to connect an MCP server
Enter the server URL
Paste the full URL of your MCP server endpoint (e.g.
https://tools.yourcompany.com/mcp).Complete authentication
Rallied.ai probes the server to detect what authentication it requires:
- OAuth
- Bearer token
- No authentication
If the server uses OAuth, you are redirected to an authorization flow. Complete the authorization in your browser. The token is stored securely and passed to the server at runtime.
Tools are synced automatically
Rallied.ai fetches the tool list from your MCP server and adds all discovered tools to the agent’s catalog. Default policies are seeded automatically based on each tool’s name and description. The server shows as connected and the agent can start using the tools immediately.
Authentication types
| Type | How it works |
|---|---|
| OAuth (PKCE) | Rallied.ai initiates an OAuth PKCE authorization flow. You complete the login in your browser. The token is refreshed automatically. |
| Bearer token | You provide a static token. It is stored securely and sent in the Authorization: Bearer header on every request. |
| None | No authentication is required. The server accepts requests directly. |
Managing tools from MCP servers
Tools from custom MCP servers appear in the agent’s tool catalog alongside built-in integration tools. You manage their policies the same way:- Open the MCP server’s detail page from MSP Settings → Integrations
- Find the tool by name (MCP tools are prefixed with
mcp:<server-name>:) - Set the permission to Auto, Approval needed, or Disabled
get, list, search, fetch) are seeded with auto by default. Tools that look like write operations (create, update, delete, send) are seeded with approval needed by default. You can override any of these defaults.