Let AI agents like ChatGPT & Claude use real-world local/remote tools you approve via browser extension + optional MCP server
🔗 MCP Link — Let AI Agents Use Your Tools MCP server exists for a simple reason — assistants are far more useful when they can act on 🔗 MCP Link — Let AI Agents Use Your Tools directly instead of describing what you should do. Let AI agents like ChatGPT & Claude use real-world local/remote tools you approve via browser extension + optional MCP server.
This project is engineered by a high-security software development professional with over 4 decades of experience in quality, stability, and long-term product survivability. To protect the integrity of the ecosystem for all users, we operate under a "visible source" model.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Once 🔗 MCP Link — Let AI Agents Use Your Tools is connected, these are the calls the assistant has available:
geolocation — Reveals your location using browser GPS or IPweather — Fetches local weather info using your locationadaptive_thinking — Helps agents reflect, revise, and plan actionscards — Draws random cards for agent decision-makingsqlite — Runs semantic and raw SQL queries on your datatts — Speaks text using your system's speakersstt — Transcribes audio from your microphonewhatsapp — Sends messages via your personal WhatsAppopenrouter — Proxies multiple AI models via user API keysai_chat — Enables agent-to-agent chat coordinationAmong the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. 🔗 MCP Link — Let AI Agents Use Your Tools's toolset — geolocation, weather, adaptive_thinking and 7 more — is a fair guide to whether it matches your workflow. It is maintained by AuraFriday; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| geolocation | Reveals your location using browser GPS or IP |
| weather | Fetches local weather info using your location |
| adaptive_thinking | Helps agents reflect, revise, and plan actions |
| cards | Draws random cards for agent decision-making |
| sqlite | Runs semantic and raw SQL queries on your data |
| tts | Speaks text using your system's speakers |
| stt | Transcribes audio from your microphone |
| Sends messages via your personal WhatsApp | |
| openrouter | Proxies multiple AI models via user API keys |
| ai_chat | Enables agent-to-agent chat coordination |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.