# shebang > One account for five hosting services (sherlock, sherpage, sherserve, sherlink, sherbase), one API, and one MCP server. ## Start - [shebang docs](https://docs.shebang.pro/): What shebang is, its five services, one API, one MCP server, and where to start. ## Getting started - [Getting started](https://docs.shebang.pro/getting-started): The five-minute path from creating an account to your first MCP tool call. - [Create an account](https://docs.shebang.pro/getting-started/create-an-account): Sign up for shebang with an email, a password, and a handle — or continue with Google or GitHub. - [Activation](https://docs.shebang.pro/getting-started/activation): shebang is invitation only — how to activate your account and what still works before you do. - [Projects](https://docs.shebang.pro/getting-started/projects): Every account starts with a default project; create more to separate keys, databases, files, links, and pages. - [Your first key](https://docs.shebang.pro/getting-started/your-first-key): Mint a master key from the dashboard, or a scoped app key for a sub-agent. - [Install the MCP server](https://docs.shebang.pro/getting-started/install-the-mcp): Add shebang to Claude Code or any stdio MCP harness with npx -y shebang-mcp. - [Device login](https://docs.shebang.pro/getting-started/device-flow-login): The RFC 8628 device-authorization flow behind the `login` command, endpoint by endpoint. - [Hosted MCP](https://docs.shebang.pro/getting-started/hosted-mcp-oauth): Call shebang's MCP server directly over HTTPS, with OAuth instead of a saved key. ## Concepts - [Concepts](https://docs.shebang.pro/concepts): The vocabulary every other shebang doc assumes — projects, keys, public ids, and access modes. - [Projects and scoping](https://docs.shebang.pro/concepts/projects-and-scoping): How the calling key's home project, and the optional project argument, decide what a call can reach. - [Keys](https://docs.shebang.pro/concepts/keys): Master vs. app tiers, the apps scope subset, and why a key can't revoke itself. - [Public ids and urls](https://docs.shebang.pro/concepts/public-ids-and-urls): How p., f., and sl. addresses are built, and why they never change. - [Access modes](https://docs.shebang.pro/concepts/access-modes): Private, password, allow-list, and public — the four levels every page, file, and link enforces. - [Rate limits and quotas](https://docs.shebang.pro/concepts/rate-limits-and-quotas): Email's 10-per-day cap, and the device-login flow's polling backoff. ## sherlock - [sherlock](https://docs.shebang.pro/sherlock): shebang's identity provider — one account for the dashboard, the API, and every app you build on it. - [Sign-in methods](https://docs.shebang.pro/sherlock/sign-in-methods): Password, one-time email code, Google, GitHub, and two-factor — the ways sherlock authenticates you. - [Sign in with sherlock (redirect)](https://docs.shebang.pro/sherlock/sign-in-with-sherlock-by-redirect): The full OAuth 2.1 / OIDC flow for letting another app authenticate against a shebang account. - [Account management](https://docs.shebang.pro/sherlock/account-management): The dashboard account page — connected apps, sign-in methods, keys, sessions, and deleting your account. - [Handles](https://docs.shebang.pro/sherlock/handles): The @handle every account has — where it's used today, and where it used to appear in urls. ## sherpage - [sherpage](https://docs.shebang.pro/sherpage): Publish a bundle of static files and get back a permanent, direct url — no build step, no deploy pipeline. - [Publishing](https://docs.shebang.pro/sherpage/publishing): The bundle shape sherpage_publish expects, and the tools that update, archive, and delete a page afterward. - [The p. url](https://docs.shebang.pro/sherpage/the-p-url): p.shebang.pro/ — how a page's address is built, and what changed for older accounts. - [Blogs](https://docs.shebang.pro/sherpage/blogs): Write a simple reader-mode blog in Markdown from the dashboard, with a logo, a name, a links page, and images. - [sherpage tools](https://docs.shebang.pro/sherpage/tools): The seven sherpage_* MCP tools, with their real argument shapes. - [Examples](https://docs.shebang.pro/sherpage/examples): A minimal single-file publish, and where to go for a full branded deck or document. ## sherserve - [sherserve](https://docs.shebang.pro/sherserve): Upload a file and get back a permanent, direct url — images, video, audio, documents, and archives. - [Uploading](https://docs.shebang.pro/sherserve/uploading): store_upload_file vs. store_upload_content — a local path against stdio, and bytes directly against hosted MCP. - [Content types and limits](https://docs.shebang.pro/sherserve/content-types-and-limits): The accepted file types, the size caps at every layer, and how a bad upload fails. - [The f. url](https://docs.shebang.pro/sherserve/the-f-url): f.shebang.pro/ — how an uploaded file's address is built, and what changed for older accounts. - [Unlock flow](https://docs.shebang.pro/sherserve/unlock-flow): What a visitor sees for a password- or allow-list-gated file, and how the unlock is remembered. - [sherserve tools](https://docs.shebang.pro/sherserve/tools): The five store_* MCP tools, with their real argument shapes. ## sherlink - [sherlink](https://docs.shebang.pro/sherlink): The single short-link and access-policy layer behind every sherpage page and sherserve object. - [Short links and aliases](https://docs.shebang.pro/sherlink/short-links-and-aliases): Implicit creation on publish/upload, custom vanity aliases, and why deleting a link deletes more than a url. - [Access](https://docs.shebang.pro/sherlink/access): How the four access modes apply through sherlink, plus the sherlink-specific fields on top. - [The sl. url](https://docs.shebang.pro/sherlink/the-sl-url): sl.shebang.pro/ — resolved by resource id, and unaffected by the public-id change. - [sherlink tools](https://docs.shebang.pro/sherlink/tools): The five link_* MCP tools, with their real argument shapes. ## sherbase - [sherbase](https://docs.shebang.pro/sherbase): A real Postgres database per slug, connection strings for direct SQL, and a Supabase-shaped Data API for the apps you build on top of it. - [Databases](https://docs.shebang.pro/sherbase/databases): base_create_database, base_list_databases, base_drop_database, and what a slug actually provisions. - [Connection strings](https://docs.shebang.pro/sherbase/connection-strings): The session and transaction pooler connection strings sherbase returns, TLS verification, and the libpq < 16 fallback. - [The Data API](https://docs.shebang.pro/sherbase/the-data-api): The PostgREST-based Data API at api.shebang.pro/db/, publishable vs. secret keys, and sherlock as the auth provider behind it. - [supabase-js examples](https://docs.shebang.pro/sherbase/supabase-js-examples): Two working sign-in paths against a sherbase database's Data API — embedded email/OTP, and the sherlock redirect flow. - [Reload schema and rotate secret](https://docs.shebang.pro/sherbase/reload-schema-and-rotate-secret): base_reload_schema refreshes the Data API's schema cache after DDL run outside base_run_sql; base_rotate_secret replaces the secret key immediately. - [Enable on older databases](https://docs.shebang.pro/sherbase/enable-on-older-databases): base_enable_api turns on the Data API for a database created before it existed, in the same response shape as base_create_database. - [Limits](https://docs.shebang.pro/sherbase/limits): What's actually enforced today on base_run_sql and the pooler — one statement per call, a character cap, and transaction-mode's prepared-statement restriction. ## API reference - [API reference](https://docs.shebang.pro/api): Authentication, the 401 challenge, the api.shebang.pro rewrite, and the handful of endpoints that don't belong to one service. - [platform](https://docs.shebang.pro/api/platform): The v1 reference for projects, keys, OAuth clients, and outbound email. - [sherpage](https://docs.shebang.pro/api/sherpage): The v1 reference for publishing and managing pages. - [sherserve](https://docs.shebang.pro/api/sherserve): The v1 reference for uploading and managing files. - [sherlink](https://docs.shebang.pro/api/sherlink): The v1 reference for short links and access policy. - [sherbase](https://docs.shebang.pro/api/sherbase): The v1 reference for provisioning and managing databases. - [agent-login](https://docs.shebang.pro/api/agent-login): The v1 reference for the RFC 8628 device-authorization flow behind shebang-mcp login. ## MCP - [MCP server](https://docs.shebang.pro/mcp): Install shebang-mcp, what login/status/logout do, and where to find every tool. - [Tools reference](https://docs.shebang.pro/mcp/tools-reference): Every shebang-mcp tool, grouped by service, with its real arguments and which ones require confirm. - [Hosted MCP](https://docs.shebang.pro/mcp/hosted-mcp): Call shebang's MCP server over HTTPS, with either an shb_ key or sherlock OAuth, and what's different from the local server. - [Troubleshooting](https://docs.shebang.pro/mcp/troubleshooting): The errors shebang-mcp tools actually raise, and what to do about each one. ## Guides - [Sign in with sherlock](https://docs.shebang.pro/guides/sign-in-with-sherlock): A complete, runnable Express app doing the OAuth 2.1 authorization-code flow end to end — login, callback, id_token, the Data API, and refresh. - [The postcard walkthrough](https://docs.shebang.pro/guides/the-postcard-walkthrough): Building a small third-party app end to end on the public platform -- sign-in, a database with RLS, a scoped key, an image upload, and a published page. - [Publish a presentation](https://docs.shebang.pro/guides/publish-a-presentation): Turning a branded HTML deliverable into a live, shareable sherpage url -- the multi-file bundle shape sherpage_publish expects. ## Reference - [Error codes](https://docs.shebang.pro/reference/error-codes): Every error string the platform API, the agent-login flow, the OAuth decision endpoint, and the sherbase Data API gateway can return, by HTTP status and route. - [Limits](https://docs.shebang.pro/reference/limits): Every numeric cap on the platform in one table -- email, device login, sherpage bundles, sherserve uploads, the unlock flow, and sherbase's SQL and pooler limits. - [Changelog](https://docs.shebang.pro/reference/changelog): Release notes for the shebang platform and the shebang-mcp package, newest first. - [Glossary](https://docs.shebang.pro/reference/glossary): One-paragraph definitions for the terms used across these docs -- project, key, scope, grant, public id, access mode, and the five services.