Browser Use
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Description from the maker (original English)
Manage structured website content in Garchi CMS through MCP.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://garchi.co.uk/mcp-oauthRun this in your terminal
claude mcp add --transport http garchi-cms https://garchi.co.uk/mcp-oauthPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"garchi-cms": {
"url": "https://garchi.co.uk/mcp-oauth"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"garchi-cms": {
"type": "http",
"url": "https://garchi.co.uk/mcp-oauth"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://garchi.co.uk/mcp-oauthMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified against the domain garchi.co.uk (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (3.0.0) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Garchi CMS for AI agents
Build and manage structured websites and applications with Garchi CMS using AI agents, official starter kits and a production MCP integration.
Build with your preferred framework and AI coding agent while Garchi provides the structured content backend. The application is written once; the business keeps managing content afterwards without routine changes to application code.
Garchi CMS is a hosted headless CMS by LumenHarbor Digital Solutions Limited. Content is organised as:
Your app fetches this over the REST API or the Node/PHP SDK and renders it. It does not replace your framework, database or hosting.
One installable integration with three parts.
MCP — the hosted Garchi MCP server, https://garchi.co.uk/mcp-oauth. This is how an agent reads and writes your live CMS: listing spaces, creating and editing pages and sections, managing data items, categories, metadata and assets.
Skills — instructions that teach an agent how to use Garchi correctly:
| Skill | Responsibility |
|---|---|
garchi-build-site | Orchestration: understand the goal, inspect the project, choose starter kit vs. integration, connect MCP, model the content, verify content stays editable without code changes. |
garchi-render-content | The application code: server-side client, page and section renderers, nested sections, data items, metadata, assets, preview mode. |
garchi-manage-content | Content operations over MCP: pages, sections, templates, items, categories, assets — including how to handle destructive actions safely. |
Starter kits — official project scaffolds for Next.js, Nuxt and Laravel, referenced (not copied) from skills/garchi-build-site/references/starter-kits.md.
The repository is packaged as an Agent Plugin (plugin.json + skills/ + mcp.json), with thin adapters for clients that use their own manifest format. The skills live in one place: update a skill and every supported agent gets the change.
Cursor loads Agent Plugins natively. While the plugin is under marketplace review, install it locally:
git clone https://github.com/lumenharbor/garchi-cms-skills.git ~/.cursor/plugins/local/garchi-cms
Then open Customize in the sidebar, find Garchi CMS, and authenticate the garchi MCP server when prompted.
Add this repository as a plugin marketplace, then install:
/plugin marketplace add lumenharbor/garchi-cms-skills
/plugin install garchi-cms@garchi-cms
Authorize the garchi MCP server with /mcp when prompted.
Add the repository as a plugin marketplace source:
codex plugin marketplace add lumenharbor/garchi-cms-skills
Then install Garchi CMS from the Plugins Directory in the ChatGPT desktop app and restart it.
If the bundled MCP server does not connect, add it to Codex directly and log in:
codex mcp login garchi
Failing that, add the server by hand in ~/.codex/config.toml:
[mcp_servers.garchi]
url = "https://garchi.co.uk/mcp-oauth"
Garchi CMS is registered as an MCP connector in ChatGPT: chatgpt.com/plugins/plugin_asdk_app_698da77dd2f48191ba19e15b0b188796. Enable it there to use the Garchi tools in ChatGPT. The plugin's .app.json points Codex and the ChatGPT desktop app at that same registered connector, so a local install reuses it rather than registering the server twice.
Clients that implement the Agent Plugins v1 specification — VS Code and others — read the root plugin.json, the skills/ directory and mcp.json directly. Point the client at this repository.
To install just the skills into any of the agents supported by the skills CLI:
npx skills@1.7.0 add lumenharbor/garchi-cms-skills
Configure the MCP server separately — see garchi.co.uk/mcp-docs for per-client instructions, including the bearer-token endpoint for clients without OAuth support.
Once installed, these work without naming the MCP server, the skills or the SDK:
| Framework | Repository | SDK |
|---|---|---|
| Next.js | garchi-next-starter-kit | @garchicms/garchi-node-sdk |
| Nuxt | garchi-nuxt-starter-kit | @garchicms/garchi-node-sdk |
| Laravel | garchi-laravel-starter-kit | garchicms/garchi-sdk-php |
Bootstrap any of them:
npx @lumenharbor/garchi-starter-kit@0.1.2 -k next
-k accepts next, nuxt or laravel.
Any other framework — SvelteKit, Astro, Django, Rails, React Native — integrates through the Node SDK, the PHP SDK or the REST API instead. There is no scaffold for those, but Garchi works the same way behind them.
https://garchi.co.uk/mcp-oauth. It advertises OAuth 2.1 protected-resource metadata (RFC 9728) with PKCE (S256) and dynamic client registration, so supported clients run the authorization flow themselves and store the tokens.mcp.json and .mcp.json entries carry a URL and nothing else.delete-section-tool and update-prop-template-tool — and garchi-manage-content requires an explicit, per-item confirmation before either runs, on top of your client's own tool approval prompts.GARCHI_API_KEY used by your app to read content is separate from MCP, is never exposed to the browser, and belongs in your own environment configuration — not in this repository.Agents can be wrong. Check the documentation when something does not behave as a skill describes.
MIT — see LICENSE.