Skip to main content
Use the remote Streamable HTTP endpoint:
Complete browser account and execution setup first. Factorize requires OAuth authorization, owner membership and tenant-bound scopes. A JSON configuration from one client is not a universal MCP configuration.

​
Codex

Current Codex supports Streamable HTTP and OAuth. Add this client-specific TOML to ~/.codex/config.toml:
Run codex mcp login factorize, then use /mcp in Codex to verify the connection. See the official Codex MCP documentation for configuration and OAuth support.

​
Claude Code

Add the remote server:
Start Claude Code, enter /mcp, choose Factorize and authenticate when prompted. See the official Claude Code MCP documentation for HTTP transport, OAuth and configuration scope.

​
Authorize in the browser

The client opens Factorize authorization in your browser. Sign in with your verified Factorize email/password and approve the requested scopes. For the full workflow, grant flows:read, flows:write, runs:read, and runs:write. Read-only access cannot create or invoke jobs. Return to your client after consent. Consent lists 12 permissions, including runs:write for renaming runs. Run write grants also retain invocation and cancellation access for compatibility. Write does not imply read. If you need to create an account or verify your email, finish those steps and restart client authorization; do not assume the signup screen will automatically resume the original request. No Linear or execution token belongs in the MCP client. Ask “List my Factorize jobs.” The agent should call list_jobs({}). An empty items list is a successful connection to a workspace with no jobs. Next ask it to list execution integrations and follow the first-job walkthrough. Other clients must support remote Streamable HTTP and Factorize’s OAuth discovery/PKCE flow. Their UI and plan availability vary; consult their own documentation rather than pasting either configuration above.

​
Connection problems

For rejected consent, expired authorization, missing targets, scope errors and reconnection steps, see connection troubleshooting. Protocol implementers should use authentication and discovery.