Log inSubmit server
Ambient Context MCP logo

Ambient Context MCP

Privacy-gated Windows context and event data exposed to AI clients through authenticated MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Ambient Context MCP

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
http://127.0.0.1:37690/mcp

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Overview

Ambient Context MCP MCP server exposes privacy-gated Windows context through a local Streamable HTTP MCP endpoint. It reports presence, battery state, foreground application category, power events, system load, and long-work detection without sending data outside the machine. Use it when an AI client needs local Windows state or events, with medium- and high-sensitivity data explicitly enabled in the tray settings. The server listens on 127.0.0.1:37690 and requires a Bearer token.

Use cases

  • Check whether the user is present before starting an agent workflow
  • Read the active foreground application category when adapting assistance
  • Poll local power and return events for context-aware actions
  • Diagnose why sensitive context values are filtered

Key features

  • Local Windows presence and system context
  • Foreground application category reporting
  • Battery and power event access
  • Privacy classification and opt-in controls
  • Streamable HTTP MCP endpoint with Bearer authentication
  • Event schema and policy diagnostics

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

6/6 checks healthy over the last 40d

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars3Stargazers on the source repository.
Last commit1mo agoMost recent push to the default branch.

How Ambient Context MCP works

What Ambient Context MCP does

Ambient Context MCP MCP server publishes selected Windows system context to MCP-compatible AI clients. Available information includes presence status, battery details, foreground application type, power-related events, system load, and indicators of extended work sessions. The application runs as a tray process and keeps its MCP service on the local machine.

The design separates context by privacy sensitivity. Data classified as medium or high sensitivity is disabled unless the user explicitly enables it in the sending settings. No external data transmission is described; the service binds only to 127.0.0.1. A local snapshot can also be retained for debugging, and event history is stored only when persistence is enabled.

How it works

The application exposes a Streamable HTTP MCP endpoint at http://127.0.0.1:37690/mcp. Clients authenticate with the Bearer token configured by the tray application. A single tray-resident process owns the local context state, while MCPB installation can connect to an already running process instead of starting another one.

Ambient Context MCP MCP server provides four tools:

  • ambient_context_get_states returns the current context snapshot, including supported presence, battery, and foreground application categories.
  • ambient_context_poll_events retrieves unread events after a client-specific cursor, such as a user returning or AC power being connected.
  • ambient_context_describe_events documents event payload schemas, sensitivity levels, descriptions, and example values without returning live event data.
  • ambient_context_get_policy explains sensitivity classifications and whether each value is currently permitted for output, helping diagnose filtered results without exposing the underlying data.

Setup and configuration

Windows 10 version 2004 or later is required. Framework-dependent distributions require the x64 .NET 8 and ASP.NET Core 8 runtimes. Windows App Runtime 1.8 x64 is also required; the application directs users to its download page if it is missing at first launch.

For Claude Desktop, download the .mcpb release from the repository and install it through the Extensions settings. After installation, Claude Desktop can spawn the tray process when needed. For Claude Code or another HTTP-capable client, extract the Windows x64 archive, run ambient-mcp.exe, enable the context categories that may be shared, and copy the client configuration from the tray menu. The resulting configuration uses the local MCP URL and an Authorization header containing the token.

User settings are stored under %LOCALAPPDATA%\\AmbientContextMcp\\settings.json. The same directory may contain a local snapshot, optional events.jsonl history, and discovery information for the active MCP process.

Limitations and notes

This is a Windows-only application and does not provide a remote service. The endpoint is local, so an AI client must run on the same Windows machine or otherwise have access to that loopback endpoint. Output depends on the enabled privacy policy: a tool may omit a value when its sensitivity is not allowed. Use ambient_context_get_policy to inspect the reason rather than assuming the value is unavailable from Windows.

Ambient Context MCP MCP server is distributed under the MIT license. The documented release paths are a Claude Desktop MCPB bundle and a Windows x64 archive; building from source uses the provided .NET solution and PowerShell release script.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Ambient Context MCP

Ambient Context MCP is an MCP server that connects AI clients to local Windows context, including presence, battery state, foreground application type, system load, and power events. Its main tools retrieve current states, poll unread events, describe event schemas, and explain privacy policies. It runs locally through authenticated Streamable HTTP.

Install the `.mcpb` release through Claude Desktop Extensions, or run `ambient-mcp.exe` from the Windows x64 archive for Claude Code and other clients. Then enable allowed context categories in the tray settings and configure the client with the local MCP URL and Bearer token.

Yes, Ambient Context MCP supports Claude Desktop through its MCPB bundle. Download the release bundle, install it from Claude Desktop’s Extensions settings, and the application can start or reuse the tray process that provides the local MCP tools.

Sensitive context is disabled by default when classified as medium or high. Users must explicitly opt in through the tray application’s sending settings. The policy diagnostic tool reports sensitivity and output eligibility without returning the protected data itself.

Ambient Context MCP requires Windows 10 version 2004 or later. The framework-dependent distribution also needs the x64 .NET 8 and ASP.NET Core 8 runtimes, plus Windows App Runtime 1.8 x64.

Related MCP servers

All in OS Automation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAmbient Context MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/ambient-context-mcp?style=directory)](https://allmcps.com/mcp/ambient-context-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/ambient-context-mcp"><img src="https://allmcps.com/api/badge/ambient-context-mcp?style=directory" alt="Ambient Context MCP on AllMCPs" /></a>