Browser tools for your AI client
Your AI.
Your browser.
Your control.
Connect the AI you use to the pages you choose. Read content, fill forms and complete browser workflows from one local bridge.
Chrome & Edge Windows x64 MCP-compatible client
0.2.0 · Release candidate. Windows downloads are available on GitHub Releases. No AI model or subscription is included.
A connection you choose
Local bridge.
Clear boundaries.
Your AI client brings the model. ToolBraid gives it tools for the browser pages you permit.
- Selected page
Grant access to a specific site. Page content can contain private information.
- Windows companion
Native messaging and an authenticated local pipe connect the browser to your client.
- Your AI client
Tool results go to your chosen client. If it uses a cloud model, that provider may receive the data.
Enable once. Know what that means.
After you accept direct control, your connected AI can act without repeated ToolBraid prompts, including submitting forms. The companion also exposes local file, desktop and job tools.
Pause control blocks new extension commands. It cannot undo actions already sent or guarantee that running jobs stop. Read the data-handling details.
X direct control
From a draft
to an action.
Prepare posts and replies, then publish, like, repost or quote through page-bound tools.
Once control is enabled on X, verified X actions run without another ToolBraid confirmation. Exact page and target checks remain active. Your AI client can still apply its own approval rules.
- Post
- Reply
- Like
- Repost
- Quote
The interface shown uses an offline X test page. These tests do not certify live X account behavior; site layouts can change.

Get connected
One extension.
One companion.
Your AI.
You need Windows x64, Chrome or Edge, and an AI client that supports MCP. No experimental WebMCP flag, separate Node.js installation or source checkout is required.
Install the Windows companion
Extract the complete Windows ZIP and run
Install.cmdas your normal Windows user, not as administrator. Close an existing ToolBraid connection before installing or updating.Add the matching extension
For release-candidate testing, use the browser's Load unpacked control to select the included
extensionfolder. Store-installed editions need their actual store extension ID in the companion configuration.Connect your AI client
Use the generated
%LOCALAPPDATA%\ToolBraid\public\mcp-client.json. Codex users can optionally runConfigure-Codex.cmd, which backs up and updates the ToolBraid entry in their client configuration.Choose a page and enable control
Open the side panel, read the disclosure, select its checkbox and choose Enable on this site. Accept the browser's site-access request. Use Connect this site to grant another origin.
Keep control visible
Advanced screenshot, accessibility and file-attachment tools have a separate optional permission. Use Pause control whenever you want to block new commands. Your enabled or paused choice survives a browser restart.
Before you connect
Is the AI included?
No. ToolBraid connects an MCP-compatible AI client you configure. Any AI account, subscription, API usage or local model is separate.
Does local transport mean all my data stays local?
No. The browser and Windows companion communicate locally, but tool results go to your AI client. Its cloud provider can receive those results. Optional media analysis also uses an endpoint you configure.
How do I update or remove it?
Close the browser connection before updating. Extract the new complete Windows package and run its installer; authentication configuration and local data are preserved. To uninstall, close the connection and run %LOCALAPPDATA%\ToolBraid\public\uninstall.ps1, then remove the extension in your browser. The companion uninstaller keeps settings, tokens, backups and data, which you can remove separately when no longer needed.
How do I get support?
Use the private feedback form for feedback, support or privacy questions. No account is required, and your email is optional unless you want a reply. Never include API keys, authentication tokens, private page contents or personal documents in a support report.