"Automating web browser searches using Chrome" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
Fetch any public web page through managed proxies, with optional JS rendering and extraction rules.
Give your AI agent persistent, governed memory for every project. At task start it recalls the approved decisions, conventions, risks and architecture (semantic search, ranked by importance); at close it proposes what was learned as typed memories that you review and approve — governance, not a notes dump. Agents propose, humans govern: edits go back to pending and deletion is human-only by design. Connect Claude Code, Cursor, Claude Desktop or any MCP client in two minutes with just your API key — hosted (nothing to install) or locally via `uvx solucortex-mcp`. Built by SoluAI and dogfooded daily: SoluCortex is developed using its own living memory.
AETumi MCP - Three.js/WebGL 3D web scenes, components & templates you own the source of.
Web animation accessibility MCP: GSAP, static CSS checks, prefers-reduced-motion, WCAG 2.2.2/2.3.3.
SEO and AI-search audit for websites, built for Uzbekistan (Uzbek and Russian sites). Checks on-page SEO, technical health (HTTPS, TLS 1.3, HSTS, HTTP/2-3, robots.txt, sitemap, broken links), AI-search readiness (GEO/AEO), speed and Core Web Vitals, content and social tags, and returns concrete fixes plus AI recommendations for title, description and H1 based on real search demand in Uzbekistan. Start an audit with start_audit, then fetch the result with get_audit.
Retasc is a work queue for AI coding agents that Claude Code, Codex, Cursor and other MCP clients pull from when you have several agents to coordinate. Two agents can never hold the same issue. A claim is one server transaction. `next_issue` claims the highest effective-priority issue that is unblocked and unclaimed. When the CLI sees a dirty worktree or a commit from the last 24 hours on an unclaimed issue's branch, Retasc holds it out of dispatch for 60 minutes so a second agent does not start the same work. A claim replaces the hold. Two of your agents try to file the same bug. Retasc refuses a create that looks like open work and names the look-alikes. The check uses issue IDs mentioned in the new title or body and rare words shared with open issue titles in the project. The agent comments on or claims the existing issue, or re-files naming the issues it read. Blocked work is never handed out. Every issue an agent creates must declare what it is blocked by, or state in one line why it depends on nothing. Closing a blocker frees its dependents. A chore blocking an urgent feature jumps the queue. You get a message on Slack, Discord, Telegram or email when your issue's last open blocker closes. Rate limits, closed laptops and stalled sessions can stop your agent. The Retasc CLI renews each 30-minute lease every 10 minutes without involving the model. When renewals stop, the issue returns to the queue in its owner's lane. That person's next agent, on any runtime, resumes from the checkpoint of what's done, what's next and the gotchas. If nobody returns for 7 days, it rejoins the shared pool. Work waiting for review jumps the queue. Retasc requires a note naming the branch, PR or commit unless the agent already left a checkpoint. A different person's agent gets the note. Whoever sent the work to review cannot claim or accept its review. Review ranks at least High immediately, Urgent at 21.6 hours and above everything after 24 hours. GitHub and GitLab issues reach Retasc through verified webhooks. No agent gets a synced issue until a member approves its exact text. A source edit voids the approval. The Dash lists every agent, its runtime, the issue it holds and the minutes left on its lease. `npx @retasc/cli@latest bind` wires MCP for Claude Code, Codex, Cursor, OpenCode, Gemini CLI, Grok and Pi. Your folder gets an agent key after browser approval if you're signed out. Start or restart your agent there to pull work. Billing is per action, with no seats. Members are free and unlimited. A new org gets $10 of usage at signup, no card.
OPX is a buyer-side routing layer for x402 machine commerce. Before an agent pays a downstream provider, OPX ranks currently tested x402 services using recent paid performance evidence including success rate, latency, price, freshness and task fit, then returns the best provider plus independent fallbacks. Each routing decision costs $0.002 USDC on Base.
Narrated demo and tutorial videos of your web app, from a guide or your coding agent.
Fleet entry point: 22 hosted MCP servers, 160 tools, 110 free. Searches 138 agent skills.
Compress, convert and resize images, and scan web pages for every image they load.
Remote MCP that evaluates one public HTTPS URL for WebMCP readiness: intent, tools observed, what to add, what never to expose.
Search real-world UI & UX design references for mobile apps, web apps, and websites with Mobbin.
Official MCP server providing AI assistants with direct access to Stimulsoft Reports & Dashboards developer documentation. Enables semantic search across FAQ, Programming Manual, Server Manual, User Manual, and Server/Cloud API references across all Stimulsoft platforms (.NET, WPF, Avalonia, WEB, Blazor, Angular, React, JS, PHP, Java, Python).
Micro-settled web content extraction and JSON schema validation utilities for AI agents and MCP clients, backed by the Bristlecone Logic API engine.
mumo is a remote MCP server for multi-model deliberation. Your agent sends a question to models from different labs — Claude, GPT, Gemini, Grok, DeepSeek, Kimi, and more — and gets back their full responses plus typed cross-model reactions. The participating models react to each other directly and explain, in their own words, what they agree with, challenge, or want to explore further. Agents can run a deliberation with `create_deliberation`, wait for results with `wait_for_round`, and steer follow-up rounds with `append_round` using structured signals like KEEP, EXPLORE, CHALLENGE, CORE, and SHIFT. Built for architecture, plan/spec review, strategy, and pre-launch pressure tests. Free tier available. API key required.
**Can AI actually read your page?** ChatGPT, Perplexity, Claude and Google's AI Overviews fetch pages very differently from your browser — no JavaScript, tight timeouts, and a robots.txt rulebook of their own. Lekta fetches a URL exactly the way they do and grades what survives, **A+ to F**. This is the technical half of **AEO** (answer engine optimization) and **GEO** (generative engine optimization): before a model can cite you, it has to be able to fetch you, parse you, and find one sentence worth quoting. **The loop this server was built for:** `Audit https://mysite.com/pricing with Lekta, apply the fixes it lists, audit it again, and show me the difference.` Your agent gets a graded verdict, a ranked fix plan with the exact markup to paste, and a diff that proves the change landed. Repeat until A+. **Four layers, 100 points:** **Access** 25 — do the ~17 AI crawler tokens get past robots.txt? **Indexability** 25 — how much content survives without JavaScript? **Answerability** 30 — is there a single quotable sentence an engine can lift? **Recency** 20 — can a model tell when this page was last true? **What this is not:** a rank tracker. Lekta will not tell you how often ChatGPT mentions your brand. It tells you whether your page can be read and quoted when it does — the part you can actually fix. **No black box.** Every finding cites its basis — an RFC, a vendor doc, or a dated measurement we ran. The engine is versioned with a public changelog: a score never moves without a published shift table. **Tools:** `lekta_audit` (fresh fetch) · `lekta_report` (cached read) · `lekta_fix_plan` (ranked, paste-ready) · `lekta_diff` (before/after) · `lekta_my_sites` Listing tools is open. Tool calls need a free key from lekta.dev/en/panel/api — send `Authorization: Bearer lekta_…` or `x-api-key`. Cached reads, fix plans and diffs cost nothing; only fresh fetches count against the daily limit. **Topics:** AEO · GEO · AI SEO · LLM SEO · answer engine optimization · generative engine optimization · AI crawler access (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) · JavaScript-free indexability · structured data · content freshness
Publish in seconds, get the audience, start monetization, get all analytics — without leaving your agent. Playgama MCP is a remote MCP server for game developers. Point Codex, Claude Code, Cursor or VS Code at it and your agent works inside your Playgama developer cabinet: it creates a game and fills in the form, uploads a build and polls until the engine analysis is done, uploads covers in the exact sizes the form requires, edits the in-app catalog and leaderboards, gets a QA Tool link, and publishes a sandbox — a public link anyone can play, with no moderation step. It can also bring the first players to that sandbox through Playgama DSP, with the first run per game free. 22 tools, 11 of them read-only; every write is annotated as destructive so your client asks first. Submitting to moderation, deleting and payouts are deliberately left out: the agent prepares everything, a human presses the button. Authentication is OAuth 2.1 with dynamic client registration — there is no token to copy. The client opens a browser on first use, and connected agents are listed and revocable in the cabinet. After the link is live the game takes its first players from the Playgama network, and Playgama DSP can send more the same day (beta). Once it clears the session threshold you can switch on advertising — Playgama Ad serves rewarded, interstitial and banner formats through one JS SDK (access by request). Playgama Wrap turns the same game into a standalone site on your own domain with player accounts, in-game purchases and indexable SEO pages (early access), and Playgama Bridge SDK gives one API for ads, leaderboards, payments and platform SDKs when you publish across platforms. Playtime, retention and revenue reports are in the developer dashboard, and payouts start at 100 USD. Product page: https://playgama.com/mcp/ Docs: https://wiki.playgama.com/playgama/mcp Tools reference: https://wiki.playgama.com/playgama/mcp/tools Connected agents: https://developer.playgama.com/mcp
Create, edit, preview, and deploy full-stack web apps to a live URL from any MCP client.
Parametric 3D CAD for AI agents. Claude Code, Cursor or any MCP client can build and edit real OwlCAD projects: primitives, booleans, and generators for gears, threads and Gridfinity. Check a part for printability and interference, then export STL, 3MF, OBJ or STEP. Output is an editable model with named millimetre dimensions, not a mesh, so you can open it in the browser and change any value afterwards. Sign in with OAuth or an access token. Requires OwlCAD Pro.
Build, inspect, edit, publish, and manage websites and web apps with Kleap. Connect through OAuth—no API key or secret to paste.
