Fulcra — Claude Code MCP server: Fulcra Context for your agent
An MCP server that hands your agent tools for the Fulcra Context API. Useful when project context lives in Fulcra.
claude mcp add --transport http context https://mcp.fulcradynamics.com/mcpWhat Fulcra does
The server sits on top of the fulcra-api Python package and exposes tools plus resources that call Fulcra. It can run as a local stdio process or as a remote Streamable HTTP endpoint. A public instance is already up at https://mcp.fulcradynamics.com/mcp, so an OAuth2-capable MCP client is all you need to reach it.
OAuth2 is handled inside the server. It catches the callback itself and keeps exchanged tokens away from MCP clients, routing traffic through its own authorization service with a mapping table underneath.
Model-facing tools include open_agent_contacts, which opens Agents I Know, optionally aimed at an exact peer user ID or a discovered multiparty thread ID. Opening is read-only and rendering needs a host with MCP Apps support. Another is update_data_type: it renames or re-describes an owned active v1 Event/Metric type after user authorization, then reads it back independently. Schemas, records and shares stay untouched; a write you are unsure about needs reconciliation. For local runs, uvx is the shortest path.
What it helps with
- list known agents and jump to a specific thread
- read Fulcra Context data from inside the agent
- rename or re-describe an owned Event/Metric type
- connect Fulcra to a client without handling tokens by hand
- run the server locally while working on it
Example prompts for the agent
- Connect to Fulcra and list the agents I know
- Open
open_agent_contactsfor that user and show the thread - Update the description on my active metric type and read it back
How to install Fulcra
1Platform CLI: remote server
claude mcp add --transport http context https://mcp.fulcradynamics.com/mcp2Platform CLI
claude mcp add fulcra -- uvx fulcra-context-mcpuvx runs the command named after the package; if the README names another one, use uvx --from fulcra-context-mcp <command>
1Platform CLI: remote server
codex mcp add fulcra --url https://mcp.fulcradynamics.com/mcp2Platform CLI
codex mcp add fulcra -- uvx fulcra-context-mcpuvx runs the command named after the package; if the README names another one, use uvx --from fulcra-context-mcp <command>
Config file
{
"mcpServers": {
"fulcra": {
"url": "https://mcp.fulcradynamics.com/mcp"
}
}
}{
"mcpServers": {
"fulcra": {
"command": "uvx",
"args": [
"fulcra-context-mcp"
]
}
}
}uvx runs the command named after the package; if the README names another one, use uvx --from fulcra-context-mcp <command>
Config file
{
"servers": {
"fulcra": {
"type": "http",
"url": "https://mcp.fulcradynamics.com/mcp"
}
}
}{
"servers": {
"fulcra": {
"type": "stdio",
"command": "uvx",
"args": [
"fulcra-context-mcp"
]
}
}
}uvx runs the command named after the package; if the README names another one, use uvx --from fulcra-context-mcp <command>
1Platform CLI: remote server
gemini mcp add -t http fulcra https://mcp.fulcradynamics.com/mcp2Platform CLI
gemini mcp add fulcra uvx fulcra-context-mcpuvx runs the command named after the package; if the README names another one, use uvx --from fulcra-context-mcp <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Fulcra
How do I install Fulcra in Claude Code?
For the remote server: claude mcp add --transport http fulcra https://mcp.fulcradynamics.com/mcp. For a local process: claude mcp add fulcra -- uvx fulcra-context-mcp.
What does Fulcra do?
It gives the model tools and resources that call the Fulcra API: reading and writing context data, agent contacts, and Event/Metric types.
Do I need my own OAuth2 app?
Any OAuth2-capable client works with the public instance. The server handles the callback on its side and does not pass tokens to clients.
