Most connection problems come down to a few common causes: an incomplete URL, a login step that did not finish, or a missing prerequisite. This guide walks through them in the order worth checking.
Start Here
When you first connect, a browser window opens for you to log in to Fulcra. The connection is not complete until you finish that login and authenticate.
If your agent or assistant seems connected but cannot read your data, the login step may not have completed. Try connecting again and watch for the browser window. Finish the login fully, then close the tab and return to your agent.
Check the MCP server URL
Check the MCP server URL
If you are connecting through MCP and it is not working, check the URL first. The correct address is:
https://mcp.fulcradynamics.com/
One thing that is expected: if you open this URL directly in a browser, you will see an authorization warning. That is normal and not a sign anything is broken. The URL is meant to be used by your MCP client, not visited directly.
If you use a client that only supports stdio
If you use a client that only supports stdio
Some assistants only support a connection type called stdio. If yours does, it needs a small proxy to reach the Fulcra server. A common one is mcp-remote. Here is an example configuration for Claude Desktop:
{ "mcpServers": { "fulcra_context": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.fulcradynamics.com/mcp" ] } } }
If the proxy connection proves unreliable, you can run the Fulcra MCP server locally instead, which some people find more stable:
{ "mcpServers": { "fulcra_context": { "command": "uvx", "args": [ "fulcra-context-mcp@latest" ] } } }
If you are using the CLI
If you are using the CLI
If you are connecting through the CLI rather than MCP, the most common blocker is a missing prerequisite. The CLI runs through uv, so uv needs to be installed first. If the command does not run, confirm uv is in place and try again. You can find install instructions in the official uv documentation.
After that, the same login rule applies: the first run opens a browser window to authenticate, and the connection is not ready until you finish that step.
Still stuck?
If you have checked the URL, finished the login, and confirmed your prerequisites are installed, send us the details at [email protected] or reach out on Discord. Let us know which assistant or agent you are connecting and what you see when it fails, and we will take it from there.