GETTING CONNECTED
Your packages.
Your runtime.
Bring your workspace’s definitions and answers into Claude, ChatGPT or Codex. ForkOps keeps HubSpot and your quota sheet read-only.
Connect your runtime
Read-only sourcesChoose the client you use, follow its setup steps, then return to your package.
Choose the workspace
Sign in with your ForkOps account and choose a workspace when your runtime connects. Each connection can access only that workspace. Naming another workspace in a prompt does not change its access.
Sign in with ForkOps
Your runtime opens ForkOps sign-in. Choose your workspace and approve access. Tokens are issued and renewed privately by the client.
Never paste credentials into a prompt or configuration file. This page never retrieves, displays or copies your tokens. Manage or revoke connections from Connected apps.
This public address is safe to copy. Use the access method described for your client below.
Codex4 steps
Connect once with your ForkOps account. Codex handles access and renewal privately.
Add the hosted ForkOps connection from a terminal with Codex installed.
codex mcp add forkops --url https://mcp.forkops.ai/mcpStart sign-in. Register the client automatically, sign in to ForkOps, choose your workspace and approve the connection.
codex mcp login forkops --oauth-client-registration dcrStart a fresh Codex session and inspect /mcp, then make the test request.
codexCheck that ForkOps is connected, then ask: Using ForkOps, read quota_pacing@v1 and pipeline_coverage@v1 with get_context. Call get_pacing and get_coverage_vs_stlq for those exact versions and compare their results with the web app. Use the same workspace, quarter and snapshot date, and the same scope for pacing. A definition alone does not verify metric results.
Return to your package here. You can revoke the connection from ForkOps → Connected apps. Never copy access codes or tokens into a prompt or configuration file.
Claude Code4 steps
Use Claude Code’s browser sign-in flow with your ForkOps account.
Add ForkOps as an HTTP server. No private request header is needed.
claude mcp add --transport http --scope user forkops https://mcp.forkops.ai/mcpSign in through your browser. Select the intended ForkOps workspace and approve access.
claude mcp login forkopsYou can also open /mcp in Claude Code and choose Authenticate for ForkOps.
Start a fresh Claude session, enable ForkOps and make the test request.
claudeCheck that ForkOps is connected, then ask: Using ForkOps, read quota_pacing@v1 and pipeline_coverage@v1 with get_context. Call get_pacing and get_coverage_vs_stlq for those exact versions and compare their results with the web app. Use the same workspace, quarter and snapshot date, and the same scope for pacing. A definition alone does not verify metric results.
Return to your package after connecting. Revoke access from ForkOps → Connected apps whenever you need to disconnect.
Claude custom connector4 steps
Use the hosted connection in Claude on the web or Desktop with OAuth sign-in.
Open Customize → Connectors → Add → Add custom connector. Name it ForkOps and paste the hosted MCP endpoint above.
Continue to the authentication review, choose Sign in now, and select Register automatically for the OAuth client. Sign in with your ForkOps account, choose your workspace and allow the connection.
Client labels vary by Claude version. Use automatic registration (DCR), rather than a published client identity. No manually supplied client secret or Authorization header is needed.
Finish adding the connector, enable it for a fresh conversation and make the test request.
Check that ForkOps is connected, then ask: Using ForkOps, read quota_pacing@v1 and pipeline_coverage@v1 with get_context. Call get_pacing and get_coverage_vs_stlq for those exact versions and compare their results with the web app. Use the same workspace, quarter and snapshot date, and the same scope for pacing. A definition alone does not verify metric results.
Return to your package and open its prepared request. Use Connected apps here to revoke the grant.
ChatGPT4 steps
Add ForkOps as a custom MCP server using OAuth with automatic client registration.
Open Plugins → Add → Add custom MCP server, and paste the hosted MCP endpoint above. Availability and labels depend on your ChatGPT plan and workspace settings.
Choose OAuth with DCR, create the plugin and install it. Complete ForkOps sign-in, choose the intended workspace and approve access. Do not enter a shared bearer token.
Enable ForkOps in a fresh conversation using its @ mention, then make the test request.
Check that ForkOps is connected, then ask: Using ForkOps, read quota_pacing@v1 and pipeline_coverage@v1 with get_context. Call get_pacing and get_coverage_vs_stlq for those exact versions and compare their results with the web app. Use the same workspace, quarter and snapshot date, and the same scope for pacing. A definition alone does not verify metric results.
Return to your package here. Revoke access from Connected apps to stop this installation’s access and refreshes.
Claude Desktop (stdio)4 steps
Administrator-only local development and eval setup. Ordinary workspace access uses hosted OAuth above.
Prepare a trusted checkout and Python 3.12+ environment. Your administrator must provision the local database and intended workspace; do not distribute database credentials.
Create a private environment file outside the checkout containing DATABASE_URL, FORKOPS_TEAM_ID and FORKOPS_ENV=development. Keep its mode 600 and never include source or seed keys.
In Desktop’s developer settings, add this local server with the correct absolute paths.
{ "mcpServers": { "forkops-local": { "command": "/absolute/path/to/python", "args": [ "-m", "forkops_mcp", "--transport", "stdio", "--env-file", "/absolute/private/forkops-mcp.env" ], "env": { "PYTHONPATH": "/absolute/path/forkops/apps/mcp/src:/absolute/path/forkops" } } } }Restart Desktop, enable the local server, and make the test request.
Check that ForkOps is connected, then ask: Using ForkOps, read quota_pacing@v1 and pipeline_coverage@v1 with get_context. Call get_pacing and get_coverage_vs_stlq for those exact versions and compare their results with the web app. Use the same workspace, quarter and snapshot date, and the same scope for pacing. A definition alone does not verify metric results.
Check the connection
Connected apps — review or revoke access
A 401 response means sign-in is needed, access expired, or the connection was revoked. Reconnect through your runtime and select your workspace. Never paste a token or authorization code into support messages.
The official packages need get_context, get_pacing and get_coverage_vs_stlq. If a tool is missing or cannot return results, ask your administrator to check the service and its snapshots. Don’t substitute another workspace’s connector.
Compare both packages with the web app using the same workspace, quarter and snapshot date. Pacing also needs the same scope. Keep seeded demo history labeled and preserve unavailable results instead of treating them as zero.
After connecting, return to your package and use its Open in action. Keep the package name, version, and snapshot in the prepared prompt.