Fulcra Context MCP

What fulcradynamics/fulcra-context-mcp MCP server does

The fulcradynamics/fulcra-context-mcp MCP server gives an MCP client access to data held in Fulcra Context through the Fulcra API. Its tools are aimed at personal health, biometric, activity, and contextual data rather than general-purpose database access.

Available data includes time-series metrics such as health measurements, raw metric samples, workouts, sleep-stage-derived cycles, user-recorded annotations, location samples, and general account metadata. The available metrics and annotation definitions should be discovered through the catalog tools before requesting values.

How it works

The server uses the fulcra-api Python library to call Fulcra's API. OAuth2 is used for user consent. The server handles the OAuth callback and keeps exchanged tokens on the server side instead of passing them to MCP clients.

A public deployment is available at https://mcp.fulcradynamics.com/mcp. For local use, the process can communicate with an MCP client through stdio. When it is not configured for stdio, the README states that it uses Streamable HTTP for remote operation.

Most time-based tools require ISO 8601 timestamps that include a time zone. Results also include time zones, so clients should convert them to the user's local time zone when that information is available. Metric time-series queries can specify sampling intervals, null replacement, and selected calculations. Location queries can optionally filter nearby samples or request reverse geocoding.

Setup and configuration

The fulcradynamics/fulcra-context-mcp MCP server can be added to Claude Desktop with uvx:

{
  "mcpServers": {
    "fulcra_context": {
      "command": "uvx",
      "args": ["fulcra-context-mcp@latest"]
    }
  }
}

For a hosted connection, configure an OAuth2-capable MCP client to use the public Fulcra endpoint. The repository is intended for local operation, inspecting the implementation, and contributing. Setting FULCRA_ENVIRONMENT=stdio selects local stdio behavior; the README also describes stdio as the default when the server runs on its own.

Tools and capabilities

• annotations_catalog lists defined annotations and supplies IDs and types for later queries.
• get_annotations retrieves annotation values and metadata within a time range.
• get_metrics_catalog lists metrics usable with time-series and sample queries.
• get_metric_time_series returns sampled values for one metric, with optional calculations such as mean, minimum, maximum, deltas, and rolling means.
• get_metric_samples returns raw samples that intersect the requested interval.
• get_workouts returns workouts recorded during a specified period.
• get_sleep_cycles derives sleep cycles from sleep-stage samples and supports gap, stage, and range options.
• get_location_at_time finds a location near a requested time, with configurable lookup behavior.
• get_location_time_series returns location points over a period, with optional distance filtering and reverse geocoding.
• get_user_info returns account context such as time zone, calendar IDs, and other metadata.

Limitations and notes

Access depends on OAuth2 consent and the data available in the user's Fulcra account. Missing metric intervals may be returned as NA unless null replacement is requested. Sleep cycles are derived from raw sleep data, so their results depend on the available samples and selected gap rules.

The fulcradynamics/fulcra-context-mcp MCP server does not document a built-in data export, storage, or analysis layer beyond the listed MCP tools. Clients should provide valid time zones for temporal requests and should use the catalog tools before requesting metrics or annotations by name or ID.