---
title: shebang docs
description: What shebang is, its five services, one API, one MCP server, and where to start.
---

# shebang

shebang is one account for five small hosting services, reachable either
through a single REST API or a single MCP server — no separate signup, no
separate key, per service.

## One identity

Every account signs in once, through sherlock (shebang's own identity
provider), and that one identity — and one API key — reaches every
service below. Sign in with a password, a one-time email code, or an
OAuth provider; use the same account whether you're clicking around
`dash.shebang.pro` or calling the API from a script.

## Five services

- **sherlock** — accounts, sign-in, and OAuth 2.1 identity provider for
  your own apps.
- **sherpage** — publish static pages and small sites, served at a short
  `p.shebang.pro` URL.
- **sherserve** — upload and serve files and objects, served at a short
  `f.shebang.pro` URL, with password/allow-list/public access control.
- **sherlink** — short links and aliases for anything the platform hosts,
  served at `sl.shebang.pro`.
- **sherbase** — a real Postgres database per project, with a
  PostgREST-based Data API and sherlock-backed row-level security.

## One API, one MCP

Every service above is also a set of HTTP routes under
`https://api.shebang.pro` and a set of tools in one MCP server
(`shebang-mcp`) — the same operations either way. The API and the MCP
server both authenticate with the same `shb_…` API key, or with a
sherlock OAuth access token.

## Who this is for

Anyone who wants a page, a file, a short link, or a database online
without standing up separate infrastructure for each — by hand from the
dashboard, from a script against the API, or from an AI agent through the
MCP server.

## Get started

- [Getting started](/getting-started) — the five-minute path: create
  an account, make a project, mint your first key, and install the MCP
  server.
- [Concepts](/concepts) — the vocabulary every other page assumes:
  projects, keys, public ids, access modes.
- [API reference](/api) — every HTTP route, by service.
- [MCP](/mcp) — install, tool reference, and hosted MCP over HTTP.