Alpacacloud MCP is listed as active in the registry but did not answer our last check. 27 installs a week from npm.
Connect AI agents to Alpaca Cloud: Postgres, Auth, Storage, Sandboxes, and Workflows.
The linked repository no longer exists on GitHub — it was deleted or made private.
Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.
claude mcp add alpacacloud-mcp --transport http https://mcp.alpaca-cloud.com/mcp
{
"mcpServers": {
"alpacacloud-mcp": {
"url": "https://mcp.alpaca-cloud.com/mcp"
}
}
}
[mcp_servers.alpacacloud-mcp]
url = "https://mcp.alpaca-cloud.com/mcp"
{
"mcpServers": {
"alpacacloud-mcp": {
"url": "https://mcp.alpaca-cloud.com/mcp"
}
}
}
{
"mcpServers": {
"alpacacloud-mcp": {
"url": "https://mcp.alpaca-cloud.com/mcp"
}
}
}
This one needs environment variables set before it will start:
ALPACACLOUD_URL (Your project URL, e.g. https://<project>.alpaca-cloud.com), ALPACACLOUD_SERVICE_KEY (Project service_role key (Database/Auth/Storage tools)), ALPACACLOUD_ACCOUNT_TOKEN (Personal access token (alp_pat_…) — unlocks account-wide Sandboxes + Workflows tools), ALPACACLOUD_API_URL (Account API base (default https://api.alpaca-cloud.com)), ALPACACLOUD_SANDBOX_TEMPLATE (Default sandbox image: python | node | base (default python)), ALPACACLOUD_SANDBOX_NETWORK (true to allow outbound network in sandboxes (default false)).
The author declared them in the registry entry; get the values from the project itself.
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.alpaca-cloud.com/mcp | streamable-http | answering | 8001 ms | 4 min ago |
Connect to your PostgreSQL database to query data and schemas.
Talk to Claude and get a live web app deployed to a real URL, with Postgres, storage and cron.
x402 pay-per-call infra for agents: $0.03 image generation, Postgres, auth, storage, functions.
Build and publish web apps from your AI client: live preview, Postgres, storage, public URL.
Fail-closed, read-only PostgreSQL and MongoDB access for AI agents over MCP.
Connect your AI agent to anything — APIs, databases, and agents; read and write, auto-discovered.
Manage HepCloud (Turkish cloud) servers and managed PostgreSQL from your AI assistant. OAuth 2.1.
PostgreSQL MCP server with 203 tools, connection pooling, HTTP/SSE, OAuth 2.1, and tool filtering
Answers built from our own checks of this server.