"Google Assistant" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
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.
Host apps in the EU from your assistant: App Store, Docker, GitHub, code without GitHub, databases.
Uptime monitoring from your AI assistant: what is down, Incidents, and your Monitors.
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.
Ship a new Android app from chat. AI runs Google Play Console listings, screenshots, releases, uplo…
Rudow's mcp server lets your AI assistant — Claude, Cursor, Windsurf, VS Code and others — query your Rudow projects directly: logs, metrics, incidents and semantic search.
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.
Deploy and run apps in your own AWS, Google Cloud, Azure or DigitalOcean account from any AI agent.
Deploy applications to Cloud Run
The 9apes MCP server lets an AI assistant read the GitHub Actions data 9apes already collects for your organization: runs, jobs, steps, and their durations. Ask it why a build got slower, which jobs take the longest, or how this week compares with last week. It is read-only. It cannot start, cancel, or change jobs, runners, billing, or account settings.
Inspect and control your Northflank projects, services, jobs, and builds from your AI assistant.
Manage Laravel Forge servers, sites, and deployments from your AI assistant.
Deploy and host the apps your AI assistant builds — a real server, database, and shareable URL.
Build, test and deploy full-stack apps from your AI assistant. Automo Build is an AI app builder: describe an app in plain language and its agents write the code, test it, security-scan it and deploy it, with database, backend and hosting built in. You own the code. Create projects, prompt builder agents, review changes and ship from Claude, Cursor or any MCP client. Free plan at automo.build.
Manage platform201 projects, environments, blueprints and deployment graphs from your AI assistant.
Ship apps for iPhone, iPad, Mac, Apple TV, Vision Pro and Android to the App Store and Google Play
Operate GitHub from your AI assistant: repos, PRs, issues, Actions. Previews and read-only mode.
AI-agent operations for App Store Connect and Google Play, with approval before live publishing.