Connecting your own MCP servers
Agile Chat supports the Model Context Protocol (MCP). This lets you connect services that are not part of Agile as well.
Agile Chat supports the Model Context Protocol (MCP). This lets you connect services that are not part of Agile as well.
Requirements
- The service provides an MCP endpoint over HTTPS (Streamable HTTP).
- Addresses in internal networks (such as 192.168.x.x or localhost) are blocked for security reasons.
Connecting
- Connectors → Add your own.
- Enter a name and address, for example
https://lager.beispiel.de/mcp. - Agile Chat checks which sign-in method the service offers:
- OAuth: You are redirected to the service’s sign-in dialogue.
- Access token: Enter the token the service gives you.
- No sign-in: for public services.
- Once connected, you will see the list of tools.
Controlling tools
For each tool, choose Always allow, Ask or Off. Tools that the service marks as “read-only” run without asking. Use Refresh to reload the tool list when the service has new tools.
Data protection
For your own connectors, you conclude the agreement with the respective provider yourself. Agile Chat only transmits to the service what the AI needs for the tool call. Your credentials are stored encrypted.
War dieser Artikel hilfreich?