shebang-mcp

One MCP server and CLI for hosting pages, sharing files, making short links, running a Postgres database, and managing API keys — all through a single shb_… key, for accounts on shebang.pro.

Quickstart

Claude Code:

claude mcp add shebang -- npx -y github:New-Kringster/shebang-mcp
npx -y github:New-Kringster/shebang-mcp login

Any other stdio-based MCP harness, add this server entry:

{
  "mcpServers": {
    "shebang": {
      "command": "npx",
      "args": ["-y", "github:New-Kringster/shebang-mcp"]
    }
  }
}

then run npx -y github:New-Kringster/shebang-mcp login once from a terminal on the same machine (or set SHEBANG_API_KEY directly — see Env vars).

npm registry publish is planned but not live yet — install via the GitHub shorthand above until then.

Related MCP server: Modular MCP Server

The login flow

login starts a device-authorization flow against the shebang platform:

1. The CLI calls the platform, gets back a short code and a verify URL, and prints both — then tries to open your browser to that URL automatically.

2. In the browser, you sign in to your shebang.pro account (if not already) and see a page showing the device name and the same code the terminal printed — check they match, then click Approve (or Deny).

3. The CLI has been polling in the background; once approved, it writes the issued key to ~/.config/shebang/credentials.json (mode 0600) and prints the key's prefix.

From then on, every harness on that machine that runs this server picks the key up automatically — no per-project configuration.

$ npx -y github:New-Kringster/shebang-mcp login

  Confirm this code in your browser:

    x 7 w y 6 x 3 a

  https://dash.shebang.pro/authorize-agent?code=x7wy6x3a

Opening your browser… (if nothing opens, visit the URL above)
Waiting for approval....
Logged in. Key: shb_examplexxxxxxxx… (master)
Saved to ~/.config/shebang/credentials.json

Your agent can now use shebang.

shebang-mcp status shows the current key's prefix and tier; shebang-mcp logout deletes the local credentials file (it does not revoke the key — see below).

Key tiers

• Master — what login mints. Full authority over the account: every app, plus minting and revoking other keys. One master key per login.

• App — scoped to a subset of page, serve, link, base. Mint one for a sub-agent via the key_create_app tool so it only gets the access it needs; the plaintext key is shown exactly once in the response.

A key cannot revoke itself while it's the one authenticating the call — revoke a key from a different key (usually the master that minted it, via the key_revoke tool) or from the shebang.pro dashboard's account page. shebang-mcp logout only forgets the key locally; it prints this same reminder.

Tool reference

Pages (sherpage)

Files (sherserve)

Short links (sherlink)

Databases (sherbase)

Keys (master-only)

OAuth (master-only)

Env vars

The platform

The MCP server and CLI in this repo are a client only — no secrets, no server code, nothing that talks to a database directly. The platform itself (accounts, keys, pages, files, links, databases, OAuth) is operated at shebang.pro; an account there is required to use this client.

License

MIT — see LICENSE.