"Computer Aided Design" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
Your own always-on cloud computer for AI agents: managed OpenClaw, or Claude Code and Codex.
Your own cloud computer run by an AI agent: signed-in browser, its own email, files, long jobs.
ScanSing reads printed sheet music. Give Claude a PDF or a photo of a score and it gets back MusicXML, the format MuseScore, Sibelius, Finale and Dorico open. It is the recogniser inside the ScanSing app for choir singers, offered as a connector. Once a score is recognised, Claude can answer questions about it without recognising it again: - what the key, time signature, tempo and length are, and each part's range, clefs and lyrics; - one voice on its own, for example just the alto line of a choir piece; - the score or a part moved to another key, with notes respelled for the new key signature; - a MIDI file, one track per part, to listen to or rehearse with; - a short-lived download link to open the result in a browser or notation app. It handles PDFs up to 40 pages and PNG, JPEG, HEIC, TIFF and WebP images, can recognise selected pages of a long PDF, and can split a songbook into one MusicXML per piece. A file can be given as a web link or a small image; in Claude Code, a file on your computer is sent through a one-time upload link. Recognition spends pages from your ScanSing plan, so it is the only tool that is not read-only. Everything else works on the stored result and is free. The first connection with a new email comes with 20 free pages; paid plans start at $9 a month for 300 pages. Scores and results are deleted about an hour after recognition and are never used for training.
Use your Mac, Windows or Linux computer from ChatGPT, Claude or Codex: files, commands, documents.
Run protein folding, docking, design and sequence analysis tools, and read their results.
MCP facade over the Nebelus Construction API. ~48 tools give full agent build parity: create/update/probe agents, edit graphs, attach knowledge and vector stores, wire connectors, set governance policies and locked guardrails, enable grounding-trace, and read deployment wiring. Purpose-built for regulated industries: data residency is enforced per region (EU / GCC-KSA), with PII controls and an audit trail. Agents are created as drafts — no deploy tool is exposed over MCP by design; publishing happens in the Nebelus console.
API documentation drifts away from the running service, so consumers integrate against a contract nobody keeps. Routebase keeps API design, testing, mocking and documentation on one living source of truth, and this MCP server exposes that workspace to AI agents. Agents can design endpoints, write and run test suites, manage mock servers and publish documentation, always under the permissions of the connected Routebase account.
