"How to deploy my app on Vercel" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
kad.dev puts the apps you make with Claude on the web. You say what you want. Claude builds it and puts it online at its own address. You do not need to know how servers work. Your app gets its own web address. It stays private until you choose to share it. You can also use a domain name you own, like www.yourname.com. It can have a database that remembers what people enter, such as sign-ups, orders and notes, and storage for the photos and files your visitors upload. A Google sign-in lock lets in anyone with a Google account, or only the people you name. For a simple site, a change shows in a private preview within seconds, before it goes live. Every change you publish is saved as its own version, with its own private address. If something goes wrong, go back to an earlier one. If something breaks, Claude can read the error message, so it can be fixed in the same conversation. Access: you sign in with your kad.dev account and choose what Claude may do. Claude can always look at your apps. Changing or publishing them is a separate permission. Claude only sees your own projects. You can remove access at any time from your kad.dev account. Hosted in Europe. Requirements: a kad.dev account.
Writes your daily standup from GitLab or GitHub merge request state: what's ready, blocked or waiting on your review, and why a pipeline is red, read from the failing job log. OAuth sign-in, no API keys; can post the note to Slack, Discord or Google Chat on a schedule.
Deploy static sites on Hostsmith - give it a file, get a live HTTPS URL. EU/US residency.
Publishes what an AI made — a page, a markdown or PDF doc, or a whole site — to a live HTTPS link. Runs locally over stdio from the @drop2run/mcp npm package, or hosted at https://mcp.dropto.run/mcp for chats that connect by URL.
Cloud iPhones and Macs with Xcode for AI agents: build, run and test iOS apps, use the screen.
Deploy apps from GitHub, read build/runtime logs, and manage your app's users from your AI agent.
Deploy apps built with AI tools (Lovable, Bolt, Cursor, Claude) straight from GitHub. Put an app online, check its status, read deploy logs and set environment variables, all in plain English. Signs in with GitHub; free for up to 3 apps.
AI agent monitoring: alerts when your agents fail, stall or need you
Deploy and run your projects on Pethost, your own hosting.
Manage your Cycle infrastructure from any AI assistant. Deploy and reconfigure containers, VMs, and full stacks; create environments; provision servers and manage clusters; handle DNS records, scoped variables, image sources, and volumes. Troubleshoot with logs, metrics, telemetry, and instance console commands. Authenticates via OAuth with read, write, and exec scopes. Tools outside your granted scopes are hidden, and every change is previewed before you confirm it.
Agentic AI quality engineering: run, debug and triage tests on real browsers and devices
Deploy apps, databases and previews to your own servers. Run Ployz Cloud from your agent.
Publish a client-side app with Cloche and share it with a link.
Deploy your project to a live HTTPS URL from your AI tool; read logs, set variables, resize apps.
Deploy a built website from your coding agent and share one client review link.
Deploy JavaScript Functions and static sites, read logs, and roll back on wawesome.
Deploy full-stack apps with databases, storage, backups, logs, scaling, and rollback. 74 MCP tools.
Deploy static sites from AI agents: deploy_site publishes files and returns a live URL in seconds.
Give an agent a place to put large output. Build logs and reports get a stable versioned URL.
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.
