Dashboard · Screens
Integrations
The tools you connect to your account, one card each: MCP server — build and run your apps on Manybases from your AI tools — and GitHub — deploy each app from its GitHub repository, on every push to main. The GitHub card says Go to integration once a GitHub account is connected, and Configure GitHub otherwise.
MCP server#
Connect an agent in three steps: add the server to your AI tool, sign in, build a first app — documented in Connect an agent. The old address dash.manybases.com/mcp leads to this screen.
GitHub#
Connect GitHub so your agent can deploy each app from its own repository: every push to main goes live, and no key is stored anywhere. The screen has two steps.
1 · Connect GitHub. On GitHub, pick All repositories so your agent can deploy the repositories it creates, without you adding each one. Trade-off: your agent can then link any repository on that account — and anyone who can push to a linked repository can deploy its app. The app only reads which repositories exist — it never reads your code, writes a file, or touches your workflows.
The connection lands on a return page. GitHub sends you back, and Finish connecting completes it; if the app was just installed, one more authorization confirms which account you are; if GitHub shows several installations for the account you signed in with, pick the one to connect, and GitHub asks you to authorize again for it. "Your request was sent to the organization owners" means an organization requires approval — come back once it is approved. This can take a minute or two when GitHub is slow; do not reload the page. A return that does not match a connection started from this browser and account sends nothing.
2 · Deploy from GitHub. Once a GitHub account is connected, copy this prompt into your AI tool:
Create a GitHub repository for this app and push it. Then link it to the app's Manybases project and add the Manybases deploy workflow, so every push to main deploys the site.Your agent pushes with its own GitHub access — the Manybases app never writes to your repositories.
Connected accounts#
The list shows each connection: account, type (personal account or organization), when it was connected, and its state — Connected, or Removed on GitHub when the App was uninstalled there. Disconnect removes the installation from this account, and every repository link it carries goes with it. Sites already deployed keep serving; what stops is deploying again from those repositories. It does not uninstall the app on GitHub. Connect another account adds another account or organization — if the app is not installed there yet, install it on GitHub first.
Linking a repository to a project is your agent's gesture (link_repo); the project's Deployments tab shows the link and lets you unlink it. The whole flow, including what happens when the App is removed on GitHub, is in Deploy from GitHub.
