Skip to main content

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.

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

  • 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 (support@fulcradynamics.com).

Metadata

Release files for fulcra-context-mcp 1.19.12

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for fulcra-context-mcp 1.19.12
File Size Uploaded Provenance Actions
fulcra_context_mcp-1.19.12.tar.gz 467.0 kB Without provenance Details for fulcra_context_mcp-1.19.12.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for fulcra-context-mcp 1.19.12
File Interpreter ABI Platform Actions
fulcra_context_mcp-1.19.12-py3-none-any.whl Python 3 none any Details for fulcra_context_mcp-1.19.12-py3-none-any.whl

Total release size: 824.4 kB

Release files / fulcra_context_mcp-1.19.12.tar.gz

Download URL fulcra_context_mcp-1.19.12.tar.gz
Size 467.0 kB
Tags Source
SHA-256 checksum
How to use checksums
dd2c017b74977cbd5bdee2891c47d44b0896f9fce2322d0a65fb4f023dde8cf4
BLAKE2b-256 checksum
How to use checksums
35b67efbc23e6075942707dd0fabce8eaaba9acd9c54a224ad410a6fb2ce4f2d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / fulcra_context_mcp-1.19.12-py3-none-any.whl

Download URL fulcra_context_mcp-1.19.12-py3-none-any.whl
Size 357.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
611fffa1c8fd7b2ee7c0555e7d5d9814aec676d0663a59c62dcb9d137fe2304b
BLAKE2b-256 checksum
How to use checksums
2746e71d6b7ced9a54b58f7091e2d6c1ee74085e0b7d7408a9986fa30d4f4def
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for fulcra-context-mcp 1.19.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

1.19.12 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page