factreason_component_spec — FactReason MCP Tool
factreason_component_spec
(factreason component spec) is one of 11 tools on the
FactReason
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call factreason_component_spec from your client
- Claude Code FactReason factreason_component_spec run in your project directory
- Claude Desktop FactReason factreason_component_spec ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor FactReason factreason_component_spec ~/.cursor/mcp.json
- VS Code FactReason factreason_component_spec .vscode/mcp.json
- Zed FactReason factreason_component_spec ~/.config/zed/settings.json
- Windsurf FactReason factreason_component_spec ~/.codeium/windsurf/mcp_config.json
- Cline FactReason factreason_component_spec ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI FactReason factreason_component_spec ~/.gemini/settings.json
- Grok FactReason factreason_component_spec .mcp.json (in your project root)
- ChatGPT FactReason factreason_component_spec Settings → Connectors → Advanced → Developer mode
- Claude.ai FactReason factreason_component_spec Settings → Connectors → Add custom connector
- LangChain FactReason factreason_component_spec pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http factreason https://www.factreason.com/mcp
Other tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.