This repo is your public entry point for Brivvy AI integrations. You get MCP server metadata, install steps, client connection profiles, and release
Connect Ai to Claude, Cursor or any other MCP client and it stops being a tab you switch to. This repo is your public entry point for Brivvy AI integrations. You get MCP server metadata, install steps, client connection profiles, and release notes. The ai mcp server is what makes that connection.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Area — ToolVoices — list_voicesTemplates — list_templatesCursor — Connect once, then finish OAuth in the browser when the client asks you toClaude — Claude reads .well-known metadata and walks you through consentAmong 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. Ai's toolset — Area, Voices, Templates and 2 more — is a fair guide to whether it matches your workflow. It is maintained by brivvyhq; 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 |
|---|---|
| Area | Tool |
| Voices | list_voices |
| Templates | list_templates |
| Cursor | Connect once, then finish OAuth in the browser when the client asks you to. |
| Claude | Claude reads .well-known metadata and walks you through consent. |
{
"mcpServers": {
"Brivvy": {
"url": "https://mcp.brivvy.io"
}
}
}Configuration as documented by the project. Restart the client after saving.
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.