STACK

run.getstackPublished by getstack.runOfficial publisherv2.0.0Updated Nov 20, 2026

One account for your AI agents: email, phone, payments, post and more. One bill, one off switch.

VerifiedStreamable HTTPWeb executableFinanceCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

STACK gives AI agents one account to email, call, pay, send post, hire people and get things made, with one bill and one off switch.

What you can do
  • Send email and make phone calls on the account's behalf
  • Make payments and manage spending under one bill
  • Send physical post and commission work from people or makers
  • Apply account-level controls, limits and approvals to what agents may do
  • Verify signed records offline and build against the published specifications and SDKs
When to use it
Use it when you want agents to take real-world actions such as messaging, paying or ordering on your behalf, and you want those actions tied to a single account with central billing and a way to switch them off.
Requirements
A remote MCP endpoint reached over streamable HTTP with OAuth sign-in; a STACK account is required. The repository's own build tooling needs Node 22 or later and pnpm, but that is only for self-hosting or building on the specs.
Before you install
Agents can spend money, send messages and post, hire people and order goods, so actions have real financial and reputational consequences. Access is granted through OAuth to an account that holds billing; review limits, held actions and approvals before enabling it. Memory and the network's server side are hosted only and not exported.

Installation

In SourceWeft

  1. Open STACK in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/run.getstack%2Fstack/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "stack": {
      "type": "http",
      "url": "https://mcp.getstack.run/mcp"
    }
  }
}

README

STACK

STACK is one account that lets your AI agents email, call, pay, send post, hire people and get things made, with one bill and one off switch.

This repository holds the parts of STACK you can read, build on and run, in layers under different licences:

  • The written specifications, the conformance kit, the command line, the verifier for signed records and the examples are under the Apache License 2.0.
  • The TypeScript and Python SDKs are under the MIT License.
  • The engine, the software that runs STACK on your own servers (the API, the worker, the MCP server and the packaging to run them), is source-available under the Fair Core License. Each version turns into the Apache License 2.0 two years after it is published (see spec/LICENSING.md).

What is here

  • spec: The written specifications, their JSON Schemas, the conformance kit and its fixtures. Licence: Apache-2.0.
  • packages/sdk: The TypeScript SDK. Licence: MIT.
  • sdk-python: The Python SDK. Licence: MIT.
  • packages/cli: The command-line client. Licence: Apache-2.0.
  • packages/verifier: The offline verifier for signed records. Licence: Apache-2.0.
  • examples/control-socket: The example decision server. Licence: Apache-2.0.
  • tsconfig.base.json, turbo.json, .dockerignore, .prettierrc, tooling/build-stamp.mjs, tooling/build-stamp.d.mts, pnpm-workspace.yaml: The build scaffold the packages above share. Licence: Apache-2.0.
  • apps/api, apps/worker, apps/mcp-server, packages/shared, packages/vault, packages/dropoff, packages/mcp-server, deploy, docs/self-managed, .github/workflows/engine-images.yml, scripts/licence-dev.mjs: The engine, under the Fair Core License: the rail (passports, Missions, proxy, model gateway, MCP server, connections, drop-offs, agent-to-agent), the pattern detectors with their built-in rules, the controls (policy engine, limits, held actions, reviews, approvals, the control socket), the record, the worker, and the self-managed packaging. STACK's hosted business (accounts and their pieces, billing, the skills marketplace and the Console glue) is not part of this repository; the engine reaches none of it except through the seams it declares (see docs/self-managed/README.md). Memory (the knowledge graph and its engine) is hosted only: it is part of the account, and the engine app is not exported. The STACK network's server side (installs, countersignatures, cross-company revocation, the detection and classify services, licence revocation) is STACK's paid hosted layer and is not exported either: the engine keeps only the client that calls it with a licence key. Licence: FCL-1.0-ALv2.
  • scripts/generate-spec.mjs, scripts/generate-spec-identity.mjs, scripts/generate-spec-interfaces.mjs, scripts/generate-spec.test.mjs, scripts/lib/rest-api-spec.mjs, scripts/lib/route-scope-hook.mjs, scripts/rest-api-spec.test.mjs: Tooling that needs the engine to run: the generator of the specification's schemas and tool catalog. Licence: Apache-2.0.

Licences differ by folder. LICENSE at the root lists them and each folder carries its own LICENSE; the full texts are in LICENSES/. What each licence means for you is in spec/LICENSING.md.

Start here

  • Build an implementation of a specification. Read spec/: the Passport, the control socket protocol, the provider interface, the record format and the MCP tool catalog. Run the conformance kit against what you build.

  • Verify a signed record offline, without trusting STACK:

    bash
    npx @getstackrun/verify pack.json
  • Write your own control server, the server that decides what your agents may do: start from examples/control-socket.

  • Use the SDKs and the command line: packages/sdk, sdk-python, packages/cli.

Building

Node 22 or later and pnpm (the version pinned in package.json) are required.

bash
pnpm installpnpm buildpnpm test

Contributing and security

Read CONTRIBUTING.md first: contributions need a signed contributor licence agreement. Report a vulnerability as SECURITY.md describes, never in a public issue. Everyone taking part is expected to follow the code of conduct. The name and logo are covered by the trademark policy.

Repository: https://github.com/getstack-run/stack

Source: README.md at commit d680da1

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v2.0.0LatestNov 20, 2026

Score

75% 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
  • Auth declaredRequired10 pts
  • 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
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Getstack integrations