Use the site's own tools.
Discover and execute native tools registered by compatible websites. ToolBraid binds each execution to the discovered page and frame.
“Discover this site's WebMCP tools and show me what they can do.”
Your assistant. Connected.
Browser tools.
Windows tools.
Your AI.
A WebMCP-enabled browser extension with optional agent chat. Use compatible sites' native tools and stay connected to your X community without losing focus on your projects. Chat in the panel or keep using your own MCP client.
Built-in chat uses your ChatGPT account through Codex: no API key or separate API billing. Other providers and local models use an external MCP client. ChatGPT is not required for those routes. Choose your AI and follow the setup guide.
- Windows x64
- Free download
- Apache 2.0
0.3.0 RC1 · Pre-release. Chrome and Edge unpacked downloads are available. The Edge Add-ons listing is not published yet. Release status.
Built by Maharajahu.
Support is optional. ToolBraid stays free to use.
What can you do with it?
From a request
to useful tools.
You tell your assistant what you need. ToolBraid gives it a way to inspect the page or perform the action, then returns the result.
Your ChatGPT account. Your agent.
A streaming conversation through official Codex App Server, with recent local history, selected-page sharing, visible activity, Stop and approval before changes. No API-key setup. Skip this chat if you prefer an external client.
“Read this page using its tools. Don't change anything.”
Stay connected. Keep building.
Inspect visible X replies and mentions with their original links. Let your agent suggest what needs attention, draft a response, or send exactly what you choose after approval.
“Who replied? Give me a catch-up and draft a short answer.”
Make sense of open pages.
Give your assistant page text, links and tab tools so it can summarize information or compare pages you allow.
“Read this page and summarize its main points.”
Less switching. More project time.
Optionally watch one X notifications or conversation tab while Edge is open. Get a local inbox and optional notifications for newly observed posts, without model calls or automatic replies.
“Watch this conversation while I work.”
Reach beyond the browser.
Use companion tools for selected local files, desktop accessibility and jobs. These are broader capabilities, not just page reads.
“Inspect the file I selected and help me work with it.”
Native WebMCP requires a compatible browser API and site. Other ToolBraid browser tools work independently. X checks cover rendered content, not a complete account archive or DMs. Example requests are not a guarantee of support for every website.
Inside ToolBraid
The actual interface.
High-resolution views of the public 0.3.0 interface, captured at 125% zoom and 3× pixel density with offline test data. Open either image to inspect the full-resolution text.
Agent chat
The recorded read-only chat exchange, re-rendered in the released interface. This image is not a new live account check.
View full resolution ↗X community
Catch-up controls, optional monitoring and two available X actions. Offline test data; no live X actions were performed.
View full resolution ↗Understand the connection
Local bridge.
Clear boundaries.
A local connection does not mean all AI processing stays on your computer. Know which client and provider you are connecting.
- Browser extension
Reads or acts on permitted pages. Chat only receives page tools when you choose to share the selected page.
- Windows companion
Native messaging connects the panel to Codex App Server. An authenticated local pipe also serves external MCP clients.
- Codex / your MCP client
OpenAI receives chat messages and shared page results. External MCP clients use their own providers; optional media analysis is separate from chat.
Enable deliberately.
Pause when needed.
The integrated chat asks before browser mutations and stays on its selected tab. External MCP clients retain the existing direct-control policy after opt-in, including form submission; their own approval rules may also apply.
Pause control blocks new extension commands and stops chat and monitoring. It cannot undo actions already sent or guarantee that existing companion jobs stop. Read the data-handling details.
Install once
One extension.
One companion.
Your choice of AI.
Windows x64 and Chrome or Edge. Node.js is bundled. Only the optional built-in chat requires Codex and ChatGPT sign-in. Other clients are configured separately. Ordinary browser tools need no experimental flags; native site WebMCP tools require browser API support.
Start here
Complete Windows package
Companion, bundled Node.js runtime, installer and matching extension in one ZIP.
Download for Windows0.3.0 RC1 · Windows x64 · SHA-256 checksums
Browser distribution
Edge first. Chrome by ZIP.
Edge Add-ons: the planned official store channel. Not published yet; RC testers can load the included extension unpacked.
Chrome: manual installation and updates through GitHub downloads. No Chrome Web Store release is planned.
All release assets, including extension-only ↗Extract and install the companion
Keep the complete ZIP in a permanent folder. Close an existing ToolBraid connection, then run
Install.cmdas your normal Windows user, not as administrator.Load the matching extension
Open your browser's extensions page, enable Developer mode and use Load unpacked to select the included
extensionfolder. Keep that folder on disk.Choose a page and enable control
Open the side panel, read the disclosure, select its checkbox and choose Enable on this site. Handle the browser's site-access request. Advanced tools have a separate optional permission.
Choose how you want to chat
Follow one of the three connection guides below. Built-in ChatGPT chat does not need a separate MCP configuration; external clients use the generated
mcp-client.json.
The ToolBraid launcher is currently unsigned. Windows may show an unknown-publisher warning. Do not disable security protections. Checksums identify downloaded bytes; they are not a publisher signature.
Choose your AI
The chat is optional.
The choice is yours.
Choose one route, not all three. Where you sign in and select a model depends on where you chat. ToolBraid does not transfer a subscription between providers.
1. Connect ChatGPT and choose a Codex model
- Install a current Codex CLI or Codex desktop app on this PC. Use your own ChatGPT account with Codex access; no subscription is bundled.
- In ToolBraid, open Your browser agent → Connection & model → Sign in with ChatGPT. Complete the official OpenAI login. A ChatGPT browser tab being signed in does not by itself sign in the local Codex runtime.
- Choose Connect to Codex, then select an offered Codex model or leave Account default. The available models and usage limits belong to your account.
- Turn on Share the selected connected page and its tools when you want page assistance. It starts off. Ask for the page title without clicks or submissions, and check the visible tool activity.
No Configure-Codex.cmd, separate MCP entry or API key is needed for this built-in route. If login fails, run codex login yourself, choose ChatGPT sign-in, then reconnect. Use the advanced executable field only if Codex cannot be found.
Review changes before approving. Stop cannot undo a browser action already sent. Clear chat removes the recent local copy, not provider records. OpenAI's subscription and API authentication guide.
2. Use your existing client or another supported subscription
- Choose a client that supports local stdio MCP servers. Sign in using that client's supported subscription route and select your model there. A cloud-only connector cannot directly start ToolBraid's Windows companion.
- Open the installer's generated
%LOCALAPPDATA%\ToolBraid\public\mcp-client.jsonlocally. It contains the executable and arguments for thetoolbraidserver. - Merge only
mcpServers.toolbraidinto the client's existingmcpServersconfiguration, or use its documented equivalent. Preserve other entries and the generated paths. Do not upload your installed configuration. - Reload the client's MCP connection. Confirm ToolBraid tools appear, then ask that client's chat to read your enabled test page's title.
Claude Code example: sign in to Claude Code with an eligible account, register the local server and inspect it with /mcp. Check your active account/billing route with /status. The PowerShell setup example uses your generated paths; see also the provider's authentication and MCP instructions.
Codex as an external client: optionally use the included Configure-Codex.cmd helper. This configures the Codex app/CLI, not ToolBraid's built-in chat.
Another subscription does not unlock another provider inside ToolBraid. External clients retain their own approvals and billing rules; the built-in chat's per-action approval UI does not apply to them. Claude Code pairing is documented, not end-to-end certified by this release.
3. Choose and run a local model with LM Studio
- Install current LM Studio. Download or import a compatible model with tool-use support that fits your RAM/VRAM. Load it in LM Studio's chat and choose its settings there.
- Open the Program sidebar → Install → Edit mcp.json. Merge the generated
mcpServers.toolbraidentry from your installedmcp-client.jsoninto the existingmcpServersobject; preserve other servers. - Save and enable the integration in that conversation. Keep ToolBraid connected to the intended browser page and use LM Studio's chat to request a read-only page-title check.
- Check that a real ToolBraid tool was called. If tools are visible but calls fail, check the model's tool-use support and available context. See the official LM Studio MCP setup and full local-model guide.
This route needs no ChatGPT account, Codex login or cloud model key. You do not need to expose an HTTP server or enable CORS for LM Studio's own chat to use a local MCP server.
Not a built-in local chat: ToolBraid 0.3.0 has no Ollama/LM Studio endpoint field. Ollama and other runtimes need an external client that supports both their tool calling and local stdio MCP. The LM Studio instructions are documentation-based, not end-to-end certification of that pairing or every local model.
Inference can stay local, but websites, submitted actions, other integrations and a separately configured cloud/media endpoint can still send data out. A local model is not a blanket offline guarantee. Read the data boundaries.
Setup help: for login or model errors, reconnect to Codex and check account access. If chat cannot see the page, check site access and page sharing. For external clients, check the MCP entry and enabled tools. Full troubleshooting guide. Never send passwords, login tokens or full installed configuration files in feedback.
Before you connect
Is the chat required?
No. You can leave built-in chat unused and connect your existing MCP client instead. ChatGPT and Codex are required only for the integrated chat, not for using ToolBraid through another client or a local model. Compare the three routes.
Does chat use my subscription or an API key?
The optional integrated chat uses ChatGPT sign-in through official Codex App Server and your account's Codex limits. It rejects API-key accounts; there is no separate API billing path for this chat. Other providers and local models are configured in an external client, not this panel. ToolBraid is free but includes no subscription. Follow the ChatGPT setup.
What does WebMCP enabled mean?
On compatible sites and browsers, ToolBraid can discover and execute site-registered native WebMCP tools. Availability depends on the browser's API and the site. Without it, ToolBraid's existing page extraction and MCP browser tools remain available; the fallback does not invent native site tools.
Will it automatically reply to my X community?
No. It can inspect rendered replies or mentions, help you prepare a catch-up and draft answers, and execute your requested replies with chat approval. Quiet monitoring is opt-in, needs a dedicated X tab and an open browser, and does not call a model or send replies. Desktop notifications omit message previews.
Which AI assistants can use it?
Use an AI client that supports MCP and configure the ToolBraid server. A Codex configuration helper is included. Other clients require manual setup; compatibility with every client has not been established. An ordinary chatbot website does not gain access just because the extension is installed.
Does it work on every website?
No universal compatibility is promised. Website layouts, browser permissions and client capabilities matter. X actions were checked against an offline fixture, not a live account. See the release notes for completed checks and known limits.
Does local transport mean all my data stays local?
No. The browser and companion communicate locally, but tool results go to your AI client. Its cloud provider may receive them. Optional media analysis also uses an endpoint you configure.
The companion is not connecting. What should I check?
Use the extension and companion from the same release and enable the intended site. External clients need the generated MCP configuration; built-in chat does not. For built-in chat, check Codex installation, ChatGPT sign-in and the page-sharing checkbox. The troubleshooting guide separates connection, login and model issues.
How do I update or remove it?
Updates are manual. Close the connection, install the new complete package and reload the matching unpacked extension. To remove it, run the installed companion uninstaller and remove the extension separately. The uninstaller preserves settings, tokens, backups and local data. Follow the update and removal instructions.
How do I send feedback?
Use the Feedback form for a bug, idea, support or privacy question. No account is required; your reply email is optional. Your message is not posted publicly. Never include passwords, tokens, private page contents or personal documents.