nope-marketplace

Name: nope-marketplace
Author: n-o-p-e

byn-o-p-e· 1 MCP server

Stars

How to install nope-marketplace?

n-o-p-e/nope-marketplace

$git clone https://github.com/n-o-p-e/nope-marketplace

Installs into the current project.

›Prefer a prompt? Paste this to your agent

Install & use

Install nope-marketplace by running `git clone https://github.com/n-o-p-e/nope-marketplace`, then use it for the current task and follow its documentation at https://github.com/n-o-p-e/nope-marketplace.

Files · 1

View on GitHub

README.md

1	# Studio N.O.P.E. Claude Marketplace
2	We are Not Of Planet Earth
3
4	![Claude Code × Google Search & Cloud — open-source integration for AI, SEO, and infrastructure](assets/banner.png)
5
6	## About Studio N.O.P.E.
7
8	Creative Solution Engineers using AI's infinite possibilities to help humans realise their dreams.
9
10	We're [@tijsluitse](https://github.com/tijsluitse) and [@basfijneman](https://github.com/basfijneman) — two guys who believe the best tools are the ones that get out of your way. We built this marketplace because setup shouldn't require clicking through a dozen consoles and copy-pasting from stale docs. It should be one command, some sensible defaults, done — with tools you can read, fork, and shape.
11
12	We made this open source because we think everybody deserves useful tools, not just the people who can afford them. When you can automate the boring parts without friction, you ship more of what actually matters. Open source means the community can shape this into exactly what they need.
13
14	Want to work with us? We help teams build smarter workflows with AI-powered tooling, Shopify development, and creative engineering. Reach out at [info@studionope.nl](mailto:info@studionope.nl) or visit [studionope.nl](https://studionope.nl).
15
16	## Plugins
17
18	All plugins drive a real Chrome browser through [chrome-devtools-mcp](https://github.com/ChromeDevTools/chrome-devtools-mcp) — they click, type, and screenshot the actual dashboards so you don't have to. They never handle your credentials; you sign in once in Chrome and the plugins take it from there.
19
20	### [gcp-setup](plugins/gcp-setup) — Google Cloud Console, automated
21
22	Setting up a GCP project means clicking through a dozen consoles: create project, enable APIs, make service accounts, grant IAM roles, link billing, configure OAuth, deploy to Cloud Run. This plugin does all of that for you.
23
24	- Auto-detects what you need — Scans your codebase (dependencies, config, env vars, CI files) to figure out which GCP services your project requires. Only asks about what it can't determine itself.
25	- Plans before acting — Presents every step upfront, flags which ones need manual input (sign-in, billing, 2FA), then drives Chrome through the console step by step.
26	- Writes a summary — Drops a `.gcp-setup.md` in your project with project ID, enabled APIs, service account emails, and follow-up notes. Future runs read this to avoid duplicate work.
27
28	Good for: spinning up a new project from scratch, adding Cloud Run + Secret Manager to an existing app, creating CI/CD service accounts with GitHub Actions keys, or anything else that normally involves tab-switching between six GCP pages.
29
30	### [search-console](plugins/search-console) — GSC audits and fixes
31
32	Reads every report in Google Search Console that actually matters, returns a prioritised fix list, and helps you implement fixes for common structured data issues on any stack.
33
34	- Full audit — Walks through Indexing, Sitemaps, Shopping, Core Web Vitals, and Security. Drills into each issue to get the exact affected URLs, not just counts.
35	- Prioritised report — P0 → P3 list with root causes, fixes, and verification steps. Manual actions and security issues always surface as P0.
36	- Structured data fixes — When GSC flags missing fields like `priceValidUntil`, `aggregateRating`, or `availability`, finds where your JSON-LD is emitted (CMS template, framework component, SEO plugin, custom SSR), adds the fields, and verifies with the Rich Results Test before triggering GSC validation.
37
38	Good for: diagnosing why pages aren't ranking, catching sitemap/indexing gaps before they hurt traffic, fixing merchant listing errors, or just understanding what's actually happening in GSC without clicking through 15 reports.
39
40	### [cloudflare-connect](plugins/cloudflare-connect) — Subdomains wired to Railway, Vercel, and more
41
42	Pointing a subdomain at a hosting platform means jumping between three tabs and copy-pasting CNAME targets. This plugin drives both sides — the platform's custom-domain form AND the Cloudflare DNS editor — end-to-end.
43
44	- Platform-first flow — Opens Railway (or Vercel) first, attaches the subdomain, reads the CNAME target the platform reveals. Then opens Cloudflare and adds the DNS record with the captured target. No copy-paste.
45	- TXT verification handled — When Vercel asks for a `_vercel` TXT challenge, the plugin adds it automatically, waits for verification, then continues with the CNAME.
46	- Safe defaults — Defaults to DNS-only (grey cloud) because Railway and Vercel issue their own Let's Encrypt certs. Won't silently overwrite existing DNS records — always prompts.
47	- Writes a summary — Drops a `.cloudflare-setup.md` in your project with links to both dashboards and the live URL.
48
49	Good for: wiring a new subdomain to a Railway service, attaching a custom domain to a Vercel project, or any time you'd otherwise be alt-tabbing between Cloudflare and a deploy dashboard with a CNAME in your clipboard.
50
51	### [gt

6 picks

Type

Install nope-marketplace by running `git clone https://github.com/n-o-p-e/nope-marketplace`, then use it for the current task and follow its documentation at https://github.com/n-o-p-e/nope-marketplace.

nope-marketplace

How to install nope-marketplace?

Related

nope-marketplace

How to install nope-marketplace?

Related