Alpacacloud Mcp

io.github.MelgencerPublished by GitHub account Melgencerv1.4.2Updated Oct 25, 2026

Connect AI agents to Alpaca Cloud: Postgres, Auth, Storage, Sandboxes, and Workflows.

VerifiedStreamable HTTPWeb executableDatabasesCloud & Infrastructure

Overview

AI-generated overview

Connects an AI assistant to Alpaca Cloud projects, covering Postgres database, Auth, Storage, Sandboxes and Workflows tools.

What you can do
Work with a project's Postgres database, authentication and storage through the project service key tools. Run and manage sandboxes, optionally with outbound network access and a chosen base image. Use account-wide Sandboxes and Workflows tools when a personal access token is supplied. Point the server at a project URL and account API base to target a specific Alpaca Cloud project.
When to use it
Useful when you build or operate an Alpaca Cloud project and want an assistant to work with its database, auth, storage, sandboxes or workflows directly instead of switching to the dashboard.
Requirements
Runs as a remote endpoint or as a local npm package over stdio. Requires ALPACACLOUD_URL (project URL) and the secret ALPACACLOUD_SERVICE_KEY; account-wide tools need the secret ALPACACLOUD_ACCOUNT_TOKEN. Optional settings include ALPACACLOUD_API_URL, ALPACACLOUD_SANDBOX_NETWORK and ALPACACLOUD_SANDBOX_TEMPLATE.
Before you install
The service key and account token are secrets that grant access to project data and account-wide resources; keep them out of shared configs. Tools can act on database, auth and storage, so writes or deletions may be possible. Sandboxes can be allowed outbound network access, which widens what code running there can reach.

Installation

In SourceWeft

  1. Open Alpacacloud Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Melgencer%2Falpacacloud-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "alpacacloud": {
      "type": "http",
      "url": "https://mcp.alpaca-cloud.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.4.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.