Skip to main content

HERE MCP server overview

The HERE MCP server turns Enterprise Browser (EB) and its apps into Model Context Protocol tools. Any MCP-compatible AI agent or orchestration layer can call them to read from and act on a user's HERE browser.

Use the MCP server when you want an agent to:

  • Find and launch apps and supertabs, with optional FDC3 context
  • Read or broadcast context on color channels
  • See what the user is looking at in Enterprise Browser
  • Raise an FDC3 intent so an app opens or comes into focus with context
  • Send the user a desktop notification

Every tool uses the same endpoint and authentication.

Guides​

GuideToolsPurpose
App and supertab toolslist-apps, list-supertabs, launch-app, open-supertab, create-supertab, get-channel-contexts, get-channel-memberships, broadcast-context, list-open-supertabs, get-focused-contentFind and launch content, work with color channels, and check what's open on the desktop
Intent toolslist-intent-handlers, raise-intentFind FDC3 intents and raise them on the user's desktop
get-browser-contextget-browser-contextRead text and markdown from web content the user has open
send-notificationsend-notificationSend a desktop notification to a user or group

Connecting​

Endpoint​

POST https://<your-here-host>/here/api/v1/mcp
GET  https://<your-here-host>/here/api/v1/mcp

The server uses the MCP Streamable HTTP transport with JSON responses enabled. It's stateless per request, so there's no session to set up and no long-lived connection to keep open.

Authentication​

Send a bearer token from your identity provider (IdP) with every request:

Authorization: Bearer <jwt>
Content-Type: application/json

The HERE gateway checks the token's issuer, audience, and signature against your IdP's JWKS, and uses the token's subject claim as the acting user. If that user doesn't exist in HERE yet, HERE creates them from the token's identity claims.

HERE supports Microsoft Entra ID. If you use a different IdP, contact HERE support before you start building.

Client configuration example​

Most MCP clients require only a URL and headers:

{
  "mcpServers": {
    "here": {
      "url": "https://your-here-host/here/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer ${HERE_TOKEN}"
      }
    }
  }
}

Once you're connected, call tools/list to see which tools your organization has enabled. Tools behind a disabled feature flag aren't listed.

Reference​

Table of Contents