Enable clients centrally.
An organization chooses which coding agents may establish broker sessions.
← Back to Home
Coding Agents
Keep the coding flow. Retire the loose keys.
Enable Coding deployments for Claude Code, Cursor and Codex. Developers sign in through the local MCP broker; provider credentials stay server-side.
Local coding, brokered tool access01 / 04Connect the desktop
Your editor gains a controlled tool socket.
● ● ● workspace / agent
› Find the open issues
Available tools:issues.search
repository.read
repository.read
Local terminal
$ connect MCP broker → local broker connected → Fabriq session ready
MCP
Local MCP broker · coding assistant
A coding assistant connects through the local MCP broker to the configured Fabriq service.
A CLOSER LOOK
Give developers a session, not a standing key.
Claude Code, Cursor and Codex can work through the broker under the signed-in developer’s identity. Their reach stays tied to that person’s connections.
Broker session consoleSessions
| Developer | Client | Session | Provider key on laptop |
|---|---|---|---|
| Alex · Engineering | Claude Code | Open | Not required |
| Priya · Platform | Cursor | Open | Not required |
| Sam · Infrastructure | Codex | Revoked | Not required |
github.open_prcheckout / retry-fixBrokeredgithub.readpayments-core / outside accessRefuseddeploy.releaseproduction / no deploy scopeNot exposedSign in using existing identity.
OAuth sign-in establishes the session; a device-code flow supports headless environments.
Revoke at the right level.
Close a live developer session or disable the client for the organization to prevent new sessions and reconnects.
Control the session from the organization.
Enable the agents you approve.
Admins enable supported coding agents per organization. An agent that is not enabled cannot establish a session.
Sign in once.
OAuth sign-in, with device code flow for headless machines, replaces locally pasted provider keys.
See who is connected.
Live broker sessions show the developer who started them.
Revoke without a key hunt.
Disable an agent to prevent new sessions and reconnects. Revoke a developer’s live session to close what is already open.
Operational controls for engineering
What does the local machine hold?
In the brokered flow, local session authentication does not provide a raw provider credential. Tool credentials attach on Fabriq’s side.
Can the agent read a repository the developer cannot?
No. The coding agent acts through the developer’s connection and cannot expand the user’s repository access.
What appears in the activity record?
Calls retain the developer, agent, tool, action, timestamp and verdict in the shared audit trail.