{"slug": "new-foxglove-integrations-oauth-apps-and-mcp-connections", "title": "New Foxglove Integrations: OAuth apps and MCP connections", "summary": "Foxglove launched external MCP services and OAuth applications, letting its agent read from and write to tools such as Linear, Jira, GitHub and Slack, and letting developers build apps that call the Foxglove API on a user's behalf with only the access that user grants. Organization admins control which MCP services are allowed under Settings → Integrations → Allowed MCP services, while members connect their own accounts; in Slack, @Foxglove uses only read-only tools because Slack has no approval step, and on Enterprise plans service changes and account connections appear in Audit logs. A Cloud MCP server, which will let users interact with Foxglove's tools from AI clients such as Claude or ChatGPT without running Foxglove locally, is coming soon.", "body_md": "# New Foxglove Integrations: OAuth apps and MCP connections\n\nBuild applications on top of Foxglove with OAuth, and let Foxglove's agent work in the tools your team already uses through external MCP services.\n\nRobotics data does not live in one tool. A regression shows up in a recording, the bug gets tracked in Linear or Jira, the fix lands in GitHub, the discussion happens in Slack, and the training data feeds an ML pipeline your team built in-house. Every handoff between those tools is a place where context gets lost, and someone has to copy a link, a timestamp, or a screenshot by hand.\n\nAlongside [Automations](https://foxglove.dev/blog/how-we-built-foxglove-automations-and-what-comes-next) and [Datasets](https://foxglove.dev/blog/introducing-foxglove-datasets), we are launching new features that make Foxglove a platform other tools can build on and connect to:\n\n- [**External MCP services**](https://docs.foxglove.dev/docs/agents/external-mcp) let Foxglove’s agent read from and write to other products, like your issue tracker or code host, from the agent sidebar, Slack and Automations.\n- [**OAuth applications**](https://docs.foxglove.dev/docs/oauth) let you build apps that call the Foxglove API on behalf of a user, with that user’s approval and only the access they grant.\n- **Coming soon: Cloud MCP server** will let you interact with Foxglove’s tools from your AI client of choice, such as Claude or ChatGPT, without running Foxglove locally.\n\nTogether they cover both directions: other tools reaching into Foxglove, and Foxglove’s agent reaching out to other tools.\n\n## Connect Foxglove’s agent to external services\n\nConnections to external MCP services let Foxglove’s agent connect to other products through the Model Context Protocol, so it can bring information in from those products and send results back.\n\nThat means the agent can look up the Linear issue a recording relates to while you investigate, or post a summary of its findings to your issue tracker when it’s done, without you switching tabs.\n\n### How it works\n\n- **Admins choose the services.** An organization admin decides which external services the agent may use under**Settings → Integrations → Allowed MCP services** . Foxglove includes presets for common tools, and admins can add any other MCP server with a public HTTPS URL.\n- **Members connect their own accounts.** Each person connects their account under**Settings → Connected accounts** , usually through OAuth with the provider. The agent then acts with that person’s access on the external service and never gains more.\n- **One switch to turn it off.** Admins can turn off all MCP services at once without deleting anything or disconnecting anyone. On Enterprise plans, service changes and account connections appear in Audit logs.\n\n### Where the agent can use it\n\n**Agent sidebar.** In the app, the agent uses your connected accounts. Tools a service marks as read-only run right away. Anything that creates, changes, or deletes data pauses and asks for your approval first, just like any other change the agent makes.\n\n**Slack.** Mention @Foxglove in Slack, and it can read from your connected services and answer in the thread, for example, pulling up the issue linked to a failed run. Because Slack has no approval step, @Foxglove only uses read-only tools there.\n\n**Automations.** This is where External MCP does the most work. An automation can now finish its job outside Foxglove: watch new recordings for a failure mode, then file an issue with the findings and screenshots, or check a related ticket before deciding what to flag. For each automation, the owner chooses whether each service is off, read-only, or allowed to use all tools, and the run uses the owner’s connected account. Read the [Automations launch post](https://foxglove.dev/blog/how-we-built-foxglove-automations-and-what-comes-next) for more on what automations can do.\n\n### Designed with guardrails\n\nGiving an agent access to other systems should be a deliberate choice. Admins control which services are allowed, each person controls their own account, write actions require approval in the sidebar, and automations need explicit opt-in per service before they can write anything. Text that comes back from an external service is treated as data, not as instructions to the agent.\n\n## Build on top of Foxglove: OAuth apps\n\nUntil now, connecting another tool to Foxglove meant creating an API key and pasting it somewhere. API keys work well for scripts and services, but they are the wrong fit for an application that many people use, because the key doesn’t know which person is acting and can do more than any single user needs.\n\nFoxglove is now an OAuth 2.0 authorization server. If you are building an internal tool, a labeling app or a training pipeline that works with Foxglove data, you can register it as an OAuth application. Each user signs in with Foxglove, sees what the application is asking for, and approves it. The application then calls the Foxglove API as that user.\n\n### How it works\n\n- **Register an app.** An organization admin creates an application under**Settings → Integrations → OAuth applications** , with a name, developer, description, and redirect URIs. These are what users see on the consent screen.\n- **Request only what you need.** Applications request scopes that map to Foxglove API capabilities, such as`recordings.list` ,`data.stream` ,`datasets.list` or`episodes.create` . Users see these in plain language before they approve.\n- **Stay within the user’s permissions.** A token can never do more than the person who approved it. A request needs the capability in both the token’s scopes and the user’s role, including their project access.\n- **Standard flow, short-lived tokens.** Foxglove uses the authorization code flow with PKCE. Access tokens last one hour, and refresh tokens rotate on every use and expire after 30 days.\n\n### Built-in controls for admins and users\n\nRegistered applications are private to your organization, so only your members can approve them. Users can review and revoke the apps they’ve authorized under **Settings → Connected accounts**. Admins can see every authorized application and revoke one for the whole organization at once under **Settings → Integrations → Authorized applications**. Applications can’t request scopes that create or manage credentials, such as device tokens or site tokens.\n\n### What you can build\n\nScopes cover recordings, data streaming and search, devices, events, sessions, layouts, custom properties, and the new Datasets, Episodes and Automations APIs. A few examples of what teams can do with them:\n\n- An internal labeling tool that pulls episodes from a Foxglove dataset, then writes labels back as custom properties, with every change attributed to the person who made it.\n- A training pipeline that streams curated datasets from Foxglove into your own infrastructure, using the access of the engineer who set it up.\n- A partner product, such as a model training or evaluation service, that lets its users connect their Foxglove account in a few clicks instead of handling API keys.\n\n## Coming soon: Cloud MCP server\n\nIn August, we [introduced agentic workflows in Foxglove](https://foxglove.dev/blog/foxglove-goes-agentic), including an MCP server built into the desktop application that lets agents you already use, like Claude or Cursor, control Foxglove. We’ll soon be extending this functionality to the web, so you can point your MCP client at a public URL and get secure access to Foxglove’s tools without running the app locally.\n\n## Get started\n\n- Register an OAuth application: [OAuth docs](https://docs.foxglove.dev/docs/oauth)\n- Connect external services to the agent: [External MCP docs](https://docs.foxglove.dev/docs/agents/external-mcp)", "url": "https://wpnews.pro/news/new-foxglove-integrations-oauth-apps-and-mcp-connections", "canonical_source": "https://foxglove.dev/blog/new-foxglove-integrations-oauth-apps-and-mcp-connections", "published_at": "2026-11-17 16:00:00+00:00", "updated_at": "2026-11-17 19:58:43.430002+00:00", "lang": "en", "topics": ["ai-agents", "agent-protocols", "robotics", "developer-tools", "ai-tools"], "entities": ["Foxglove", "Model Context Protocol", "Linear", "Jira", "GitHub", "Slack", "Claude", "ChatGPT"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/new-foxglove-integrations-oauth-apps-and-mcp-connections", "markdown": "https://wpnews.pro/news/new-foxglove-integrations-oauth-apps-and-mcp-connections.md", "text": "https://wpnews.pro/news/new-foxglove-integrations-oauth-apps-and-mcp-connections.txt", "jsonld": "https://wpnews.pro/news/new-foxglove-integrations-oauth-apps-and-mcp-connections.jsonld"}}