HelpCode-ai/anythingmcp

Part of the October Challenge #997. Why PlentyONE (formerly plentymarkets) is one of the most widely used e-commerce ERPs among German online retailers: orders, items and variations, stock across warehouses, and customer contacts for shops and marketplaces such as Amazon, eBay and Otto. The catalog has JTL-Wawi, Xentral, weclapp and Billbee, but no plentymarkets (grep -ril plenty packages/backend/src/adapters finds nothing). With an adapter, a user could ask "which orders from yesterday are still in status 5?", "how much stock of SKU X is in the main warehouse?" or "show customer 1234's last orders". Self-hosted vs Cloud Self-hosted: available in Community and Business; no edition gating. Cloud (DEPLOYMENT_MODE=cloud): available. PlentyONE systems are public SaaS (https://p<PID>.my.plentysystems.com), so the SSRF guard allows them. On Cloud trial plans, installs count toward the connector limit (license-guard.service.ts:65). Who can use it: any role except VIEWER can install it (adapt

Part of the October Challenge #997. Why Qonto is one of Europe's largest business accounts for SMBs and freelancers, with large user bases in France, Italy, Germany and Spain. Its Business API covers transactions, client and supplier invoices, and quotes. With an adapter, a user could ask "which card payments over €500 last month have no receipt?", "list unpaid client invoices due this week" or "what came in from customer X?". The catalog has Revolut Business and Wise but no Qonto (ls packages/backend/src/adapters/*/ | grep -i qonto finds nothing). Self-hosted vs Cloud Self-hosted: available in Community and Business. Catalog adapters have no edition gating. Cloud (DEPLOYMENT_MODE=cloud): available. thirdparty.qonto.com is public, so the SSRF guard allows it. On Cloud trial plans, installs count toward the trial's connector limit (license-guard.service.ts:65). Who can use it: any role except VIEWER can install it (adapters.controller.ts:207). The connector and its encrypted authConf

Part of the October Challenge #997. Why An admin who sets up an MCP server for a team wants to hand it out without walking every colleague through a config file: put "Add to Cursor" and "Add to VS Code" badges in the team README, wiki or onboarding page, click, done. Both editors support one-click MCP install links, and many MCP servers on GitHub show such badges at the top of their README. What already exists: the MCP server page builds a Cursor deep link (cursor://anysphere.cursor-deeplink/mcp/install?…, mcp-server/[id]/page.tsx:337-340) and a VS Code deep link (vscode:mcp/install?…, :342-345), used by the "Open in Cursor" / "Open in VS Code" buttons in the Quick Connect modals (:440-457) and by "One-click add to VS Code" in the Copilot modal (:473). Custom-scheme links work when clicked inside the app, but not in a README: GitHub's Markdown sanitizer removes links that are not http(s), and most wikis do the same. What is missing is a "Share" section that produces copy-paste badg

Part of the October Challenge #997. Why AI assistants and coding agents increasingly look for an llms.txt file (the llmstxt.org proposal): a short Markdown index of a project's documentation with links, plus an optional llms-full.txt with the full text in one file. An agent asked "how do I add a SOAP connector to AnythingMCP?" can then read the right page instead of guessing. This repository has about 40 Markdown documents under docs/ (connectors, client integrations, deployment, operations, API reference, the tool definition format) but no llms.txt. The anythingmcp.com/llms.txt linked from README.md:268 belongs to the website and covers the site and its guides, not these docs. AGENTS.md tells coding agents how to work on the code; llms.txt is about using and operating the product. Self-hosted vs Cloud Self-hosted: no runtime change. The two files live in the repository and are read from GitHub. They are not copied into the Docker image (the runner stage copies only build output and s

Part of the October Challenge #997. Why The admin UI has ten sidebar entries, eight settings pages and, in a workspace in daily use, dozens of connectors and MCP servers. Reaching one connector means sidebar → Connectors → search → click. A ⌘K / Ctrl+K command palette (Linear, Vercel, GitHub and Grafana have one) lets keyboard users jump to any page, connector or MCP server, or run a common action, in a couple of keystrokes. Nothing like it exists in the frontend today: no palette component, no global keyboard shortcut. Self-hosted vs Cloud Self-hosted: enabled in Community and Business. Frontend only: no new endpoint, no ee/ code. Cloud (DEPLOYMENT_MODE=cloud): enabled. The palette lists the same entries as the sidebar and the settings navigation, with the same rules: "Single sign-on" is hidden on Cloud (selfHostedOnly, settings/layout.tsx:41-44). Connectors and servers come from the existing organization-scoped list endpoints, so only the current workspace's records appear,