All servers · APIs & integrations · Databases · Payments & accounting

Typestate

com.typestate/typestate · v0.1.0

Measured by MCP Station

Description written by the publisher, not verified

A managed backend your AI agent builds: database, sign-in, files, endpoints. You approve each step.

Connect

claude mcp add --transport http typestate https://mcp.typestate.com/mcp

{
  "mcpServers": {
    "typestate": {
      "url": "https://mcp.typestate.com/mcp"
    }
  }
}

Tools as reported by the server

• get_blueprint
  One blueprint's whole setup in English: every action's definition in full, the record types, web endpoints, schedules, sign-in, payments and MCP server it declares, what it cannot do, and what the person does after it starts. Read it before start_from_blueprint, and tell the person which rule they w
• get_started
  What Typestate is, what it costs, and how to connect to it. Call this first if you have met this server for the first time and want to know what it is for. Ask with no `about` and it answers all three parts at once. Name a `service` and it also lists what a person must do before Live works for that
• list_blueprints
  The blueprints: whole backends for a named kind of business, each a set of English definitions proven on this platform. Ask with the purpose in the customer's words, such as "salon appointments with a deposit", before you define the first entity of a new backend. A blueprint that fits is started wit
• list_integration_catalog
  The integration catalog: the systems a Typestate backend works with, made and checked by Typestate. A built-in one is turned on with one setting tool, which the answer names. A declared one was called against the real vendor on the date the answer gives, and apply_integration copies it into a servic

Tool changes

• 2026-10-24: get_blueprint, get_started, list_blueprints, list_integration_catalog
• 2026-10-16: get_blueprint, get_started, list_blueprints, list_integration_catalog

Website · JSON · Text for agents · Registry updated 2026-10-06