Use your Fulcra secure context lake to collaborate with other agents, read and write data, and more
com.fulcradynamics/context MCP Server
The com.fulcradynamics/context MCP server provides an interface to collect Apple Health data from wearables through the Context app, and then query that data via MCP. Its purpose is to enable external systems to retrieve Apple Health information using the MCP protocol.
🛠️ Key Features
Collect Apple Health data from wearables through the Context app
Query Apple Health data via MCP
🚀 Use Cases
Retrieving wearable-derived Apple Health data for downstream processing
Integrating Context app health data access into MCP-compatible tooling
⚡ Developer Benefits
Standard MCP access pattern for querying Apple Health data
Keeps health data retrieval aligned with Context app sourcing
⚠️ Limitations
Source data is specific to Apple Health and the Context app
Details such as available tools, supported endpoints, or query scope are not provided
fulcra-context-mcp: An MCP server to access your Fulcra Context data
This is an MCP server that provides tools and resources to call the Fulcra API using fulcra-api.
There is a public instance of this server running at https://mcp.fulcradynamics.com/mcp. The OpenAI plugin connects to https://mcp.fulcradynamics.com/openai/mcp, which serves the same tools except get_location, get_sleep, get_workouts and get_time_series. Claude's connector and plugin connect to https://mcp.fulcradynamics.com/claude/mcp: the /mcp tools without those four, with the contact panels always offered. See https://docs.fulcradynamics.com/ to get started quickly. This repo is primarily for users who need to run the server locally, want to see under the hood, or want to help contribute.
When run on its own (or when FULCRA_ENVIRONMENT is set to stdio), it acts as a local MCP server using the stdio transport. Otherwise, it acts as a remote server using the Streamable HTTP transport. It handles the OAuth2 callback, but doesn't leak the exchanged tokens to MCP clients. Instead, it maintains a mapping table and runs its own OAuth2 service between MCP clients.
Set OPENAI_APPS_CHALLENGE to the OpenAI plugin portal's domain verification token to serve it at /.well-known/openai-apps-challenge; unset, that path returns 404.
Remote Connection using Proxy
There is a public instance of this server running at https://mcp.fulcradynamics.com/. Point your OAuth2-capable MCP clients at that.
MCP discovery provides the current tool schemas and descriptions. Contact and
metadata tools include:
open_agent_contacts: open Agents I Know, optionally targeting an exact peer
user ID or discovered multiparty thread ID. Opening is read-only; rendering
requires a host with MCP Apps support.
update_data_type: update an owned active v1 Event/Metric type's name or
description with user authorization and independent readback. It does not
change schemas, records or shares; uncertain writes require reconciliation.
accept_agent_invitation on /mcp: with the user's authorization, create or
reuse an empty response channel, share it narrowly with the exact inviter and
post the supplied first introduction. Inspect uncertain outcomes read-only;
saved attempts never automatically send/share again.
match_agent_invitations on /mcp: complete user-prepared invitations using
first-message codes and actual incoming-share owners, not message claims.
create_agent_invitation: create an owned single-person channel and secure
persisted invitation code, optionally sharing only that outbox with a supplied
exact recipient ID. No message is sent. On /mcp, the result also includes full
invitation_text and an explicit delivery next step; skills are optional.
Reconcile errors before another call; do not fall back to generic creation.
See the invitation workflow and host-capability boundary.
/openai/mcp keeps its existing plugin contract and invitation UI.
App-only implementation tools are not part of the public model-facing reference.
Debugging / Developer Tools
Local MCP variants and secure tunnels: run the standard, OpenAI, or Claude server over stdio with local test credentials; includes exact tunnel profile commands.
Agents I Know MCP App: UI behavior and testing. The HTML ships with this server, not a separate plugin server.
Every MCP client is different, but many abbreviate tool and parameter descriptions for summaries. To avoid confusing client models, keep the initial descriptions short (full description in one line, around 80 characters).
While developing locally, the scripts/simulate_tools.py script simulates what this might look like to an MCP client:
code
FULCRA_ENVIRONMENT=stdio uv run python scripts/simulate_tools.py --command "uv run fulcra-context-mcp"