Fulcra Context

This MCP server gives you access to Fulcra Context data via the Fulcra API, enabling secure OAuth2 handling and flexible connection options. You can run it locally in stdio mode or connect remotely over HTTP to a public MCP endpoint, depending on your needs and environment.

How to use

You can connect to Fulcra Context data using two MCP connection methods. Choose a remote HTTP connection for a centralized, hosted MCP endpoint, or run a local stdio MCP server for a self-contained setup that communicates directly with your tooling.

How to install

Prerequisites: you need Node.js and npm to run MCP commands via npx for the remote setup. If you prefer a local setup, you’ll also need a CLI tool such as uvx to run the stdio configuration.

# Remote setup uses npx to launch a remote MCP server
npx -y mcp-remote https://mcp.fulcradynamics.com/mcp

# Local setup uses uvx to run the stdio-based MCP server
uvx fulcra-context-mcp@latest

Additional content

Configuration options from the available connection methods are shown below. The remote endpoint requires you to point your MCP client to the public MCP URL, while the local setup starts a local MCP server that interfaces with your environment via stdio.

If you need debugging help, you can use the MCP Inspector alongside the mcp-remote tool to inspect interfaces and diagnose transport issues.

Available tools

MCP Inspector

A tool to inspect the MCP server’s endpoints, messages, and transport details to help debug configuration and connectivity.

mcp-remote

A tool to connect to a remote MCP server over HTTP, enabling usage of hosted MCP endpoints and centralized OAuth2 handling.