Fulcra Context MCP Server

Name: Fulcra Context MCP Server
Author: fulcradynamics

@fulcradynamics

Fulcra Context MCP Server について

This MCP server lets you access your Fulcra Context history -- health data, locations, and more - from your favorite LLM frontend or agentic framework.

#python #health #productivity

基本情報

カテゴリ

その他

トランスポート

stdio

公開者

fulcradynamics

投稿者

Brandon Creighton

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "fulcra_context": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.fulcradynamics.com/mcp"
      ]
    }
  }
}

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Fulcra Context MCP Server?

An MCP server that provides tools and resources to call the Fulcra API using fulcra-api. It enables AI assistants to access your Fulcra Context data. Intended for developers who want to run the server locally, explore the code, or contribute.

How to use Fulcra Context MCP Server?

Use the public instance at https://mcp.fulcradynamics.com/mcp for quick setup, or run the server locally. The server switches between stdio transport (when run alone or with FULCRA_ENVIRONMENT=stdio) and Streamable HTTP transport otherwise.

Key features of Fulcra Context MCP Server

Provides tools and resources to access Fulcra API
Supports both stdio and Streamable HTTP transports
Handles OAuth2 callback without leaking tokens to clients
Manages its own OAuth2 service between MCP clients
Public hosted instance available for quick start

Use cases of Fulcra Context MCP Server

Build AI assistants that query and act on Fulcra Context data
Integrate Fulcra data into MCP‑compatible tools (e.g., Claude Desktop)
Run a local MCP server for development or debugging
Contribute to or extend the open‑source server

FAQ from Fulcra Context MCP Server

What is the public server URL?

The public instance runs at https://mcp.fulcradynamics.com/mcp.

How does OAuth2 authentication work?

The server handles the OAuth2 callback and maintains a mapping table so tokens are never leaked to MCP clients. It runs its own OAuth2 service between MCP clients.