MCP & Integrations
WindOp works alone, but it gets much more capable when connected to your other tools.
MCP servers
The Model Context Protocol lets WindOp use tools provided by other programs. Manage them in SettingsTools.
- Add a server (local command or remote), then enable or disable it individually.
- Import existing configs from other MCP clients such as Claude Code or Codex.
- Tool catalog: turn any built-in tool on or off.
- WindOp can also act as an MCP server so other clients can use its tools (
manage_windop_mcp_server).
Claude Code & Codex
If you have a Claude or ChatGPT plan, enable Show Claude Code models or Show Codex models in Settings to pick them from the model switcher.
- Usage counts against your subscription limits; per-message cost is shown as “Subscription”.
- Let it use WindOp's tools optionally gives those agents the same tools OpenRouter models get.
Browser Link
Browser Link lets WindOp control tabs and pages in your real browser with any tool-capable model.
Choose a browser
In Settings, pick the installed browser to connect.
Install the extension
Load the extension from the folder WindOp shows you.
Pair
Open Browser Link from the extensions toolbar, confirm consent, and click Connect. If automatic pairing fails, use the manual code.
Heads up
The pairing code grants browser-wide control — keep it private. Only one profile can be paired at a time; private tabs are excluded, and page content is sent to the model you selected.Web search & reading
Choose your search provider and how pages are read in SettingsWeb Tools:
| Reader | Best for |
|---|---|
| Readability (local) | Articles, docs, and blogs — fast and private |
| Jina Reader | JavaScript-heavy sites and SPAs |
| Basic fetch | Simple fallback when others fail |
Doc Library
SettingsDoc Library builds a local knowledge base: crawl documentation sites, index them, and let the agent search them semantically — handy for frameworks you use daily.
What's next
Something missing or out of date? Tell us on the community page.