MCP

resolve ai supports integrations with various mcp servers (both remote hosted or self hosted) as part of the multi agent architecture, we have an mcpagent that dynamically discovers the tools/apis it has access to from the mcpserver and uses them when investigating an alert for root causing or answering a question in chat hosting for mcp servers mcp servers have to be remotely hosted to integrate with resolve ai provider hosting some observability platforms or data source platforms host mcps and expose a url to connect to examples linear mcp, atlassian mcp self hosting if the mcp server exists on github, your team can self host an mcp server in your environment to connect to resolve ai authentication for mcp servers mcp support different forms of authentication oauth we support oauth only for publicly accessible mcp integrations even self hosted mcps need to have a public endpoint to use oauth authentication create a service account to use the integration data will be accessible to everyone using resolve ai in the organization token we support bearer token based authentication for mcp servers integrating with resolve ai publicly accessible mcps log in to resolve ai and connect from the integrations page https //app0 resolve ai/integrations/mcpintegration https //app0 resolve ai/integrations/mcpintegration self hosted in vpc install the resolve satellite https //docs resolve ai/resolve satellite , then configure the mcpintegration in satellite values yaml file integrations mcpintegration type mcpintegration create true connection mcpserverurl \<string> # mcp server url authmethod \<enum> # authentication method token \<string> # api token for token based authentication (optional) customauthdata headername \<string> headervalue \<string> authschema \<string> example mcp grafana with kubernetes secret integrations mcpintegration type mcpintegration create true secretname grafana k8s secret name # k8s secret name connection mcpserverurl http //mcp grafana default svc cluster local 8000/sse customauthdata headername authorization # header name in http header authschema $ token # json path to token value in secret in grafana k8s secret