
manybases/mcp
Developer toolsこのページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。 原文を見る
The Manybases MCP server — your AI agent creates and runs a backend (database, auth, files, functions, a site). Published on npm as @manybases/mcp.
概要
The Manybases MCP server: your AI agent creates and runs a backend — database, auth for your app's users, file storage, server-side functions and a site — without you opening a browser. , over stdio. You need and a Manybases (ak_…). Create the key in your dashboard, under (dash.manybases.com/account) — it is shown once. Then add the server to your MCP client's configuration (Claude Desktop, Cursor, Claude Code…): The server refuses to start without MANYBASES_API_KEY, and says so. The same tools are served at https://mcp.manybases.com: add it as a custom connector (or a remote HTTP server) and approve the consent window that opens on your dashboard — nothing to copy. See Connect an agent. An account has at most . Installing the remote connector : the server keeps running, but every tool answers 401. To come back, revoke the connector's key on and generate a new one.
README
以下は原文 README の抜粋です。原文を見る。
@manybases/mcp
The Manybases MCP server: your AI agent creates and runs a backend — database, auth for your app’s users, file storage, server-side functions and a site — without you opening a browser. 38 tools, over stdio.
Install
You need Node 22 or later and a Manybases account key (ak_…). Create the key in your
dashboard, under Account → Generate my account key
(dash.manybases.com/account) — it is shown once.
Then add the server to your MCP client’s configuration (Claude Desktop, Cursor, Claude Code…):
{
"mcpServers": {
"manybases": {
"command": "npx",
"args": ["-y", "@manybases/mcp"],
"env": { "MANYBASES_API_KEY": "" }
}
}
}
The server refuses to start without MANYBASES_API_KEY, and says so.
Prefer no key at all? Use the remote connector
The same tools are served at https://mcp.manybases.com: add it as a custom connector (or a remote
HTTP server) and approve the consent window that opens on your dashboard — nothing to copy.
See Connect an agent.
One agent at a time
An account has at most one live agent key. Installing the remote connector revokes the key
this server uses: the server keeps running, but every tool answers 401. To come back, revoke
the connector’s key on Account and generate a new one.
Variables
| Variable | Required | Meaning |
|---|---|---|
MANYBASES_API_KEY |
yes | Your account key, ak_… |
MANYBASES_ACCOUNT_SESSION |
no | Your dashboard session token, to lend the agent your authority for a working session (it lives about an hour) |
MANYBASES_API_URL |
no | The management plane; default https://api.manybases.com. It sets only the management plane |
MANYBASES_DATA_API_URL |
no | Forces the data plane onto one address, for local development |
What an agent cannot do alone
A few gestures always ask for a signed-in human: setting the app URL, deleting a project or a
user, issuing a reset link, creating a secret key (sk_), and destructive SQL. Without
MANYBASES_ACCOUNT_SESSION those tools answer 428 or 403 — a correct refusal, not an outage.
See The human boundary.
If it does not start
npxnot found, or the wrong Node. Desktop apps do not read your shell’sPATH. Put the absolute path ofnpxincommand(which npxprints it).- Windows. If your client cannot start
npxdirectly, use"command": "cmd", "args": ["/c", "npx", "-y", "@manybases/mcp"]. - Check it by hand. Send it an
initialize, then atools/list: it answers with the tools.
Links
- Documentation: docs.manybases.com — the tools, one page each: MCP tools
- Releases are published by CI from github.com/Manybases/mcp;
インストール
npx -y @manybases/mcp設定
{
"mcpServers": {
"manybases": {
"command": "npx",
"args": ["-y", "@manybases/mcp"],
"env": { "MANYBASES_API_KEY": "<your ak_ key>" }
}
}
}