mcpField
F
Fulcra MCP Server

Fulcra MCP Server

Remote
fulcradynamics.comHealth10Updated 1d ago

About Fulcra MCP Server

Fulcra MCP Server connects MCP clients to personal Fulcra Context data through the Fulcra API. It is intended for users of health, location, and other context history, and supports both local stdio operation and remote HTTP access with OAuth token handling.

Key features

  1. 01Access Fulcra Context data through the API
  2. 02Local stdio and remote Streamable HTTP modes
  3. 03OAuth2 callback and token mediation
  4. 04Contact and metadata tools
  5. 05Public hosted instance

Use cases

  1. 01Query personal health and context history
  2. 02Connect an MCP client to a hosted Fulcra service
  3. 03Run a local server for development or contribution

MCP support

The server exposes Fulcra API-backed tools and resources to MCP clients. It can run locally over stdio or remotely over Streamable HTTP, and mediates OAuth2 tokens rather than passing exchanged tokens to clients.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.fulcradynamics.com/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Packages
pypifulcra-context-mcp1.19.3

Tools

Details

From the project README

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. 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.

Local Connection

Example Claude Desktop config using uvx:

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

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.

App-only implementation tools are not part of the public model-facing reference.

Debugging / Developer Tools
  • Agents I Know MCP App: run this checkout through a private development tunnel and test the ChatGPT sidebar UI. The HTML ships with this server, not a separate plugin server.

  • Both the MCP Inspector and mcp-remote tools can be useful in debugging.

Viewing Tools

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:

FULCRA_ENVIRONMENT=stdio uv run python scripts/simulate_tools.py --command "uv run fulcra-context-mcp"

Bugs / Feature Requests

Please feel free to reach out via the GitHub repo for this project or join our Discord to reach out directly. Email also works ([email protected]).

README image

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.