MCP App Store
by KeenEthics
Piezas icon

Piezas MCP Server for Claude and ChatGPT

By Piezas.ai

Overview

Piezas lets business teams build their own apps with Claude: a client portal, a booking system, an intake form, a CRM. Piezas provides the capabilities every business app needs, including sign-in, records, documents, workflows, email and secure hosting, so there are no servers, databases or security to manage. How it works: 1. Describe the app you need. Claude asks one question at a time and writes the plan with you. 2. Claude builds the app on Piezas, in Code in the Claude desktop app or in Claude Code in the terminal. 3. Claude publishes it to its own secure address. Before anything goes live, Piezas checks the app's tests and quality scan, and asks you only for the decisions that are yours to make. In a chat on claude.ai, Claude plans the app with you, checks what Piezas supports and creates the app in your account. Building and publishing continue in the desktop app. With the Piezas connector, Claude can: - Set up a new project with the Piezas rules and starting files. - Create apps, and the keys they use, in your Piezas account. - Check what Piezas supports today, so plans stay realistic. - Publish a finished app. - List your apps and show their details. Claude asks before it creates or publishes anything. Deleting an app stays with you, in the Piezas console.

How to connect

  1. Claude: Open the Piezas listing in the Claude connectors directory and choose Connect. Claude listing Piezas exposes 10 tools here.
  2. ChatGPT: Open the Piezas listing in the ChatGPT app directory and choose Connect. ChatGPT listing Piezas exposes 11 tools here.

Tools

piezas_app_info

ChatGPT
Reports one Piezas app's name, slug and id. On an agent-token connection that is the token's own app and app_id may be omitted; on a signed-in session pass the app's id as app_id (see piezas_list_apps).

piezas_capabilities

ChatGPT
Returns the list of what Piezas can do today, as JSON: the sign-in methods, the integrations (for using a provider's data, never for sign-in), hosting and its limits, records, documents, workflows and notifications (transactional only). Check it BEFORE telling the owner something is possible. If it is not listed as available, tell them Piezas doesn't support it yet; do not build it yourself.

piezas_check_plan

ChatGPT
Checks an app's plan — the text of SPEC.md — with the same check npx piezas spec check runs, and says whether the plan is complete; if it is not, it lists what is missing in plain words. Call it when the interview with the owner seems done, BEFORE writing a new app's code, and again after each fix until it says the plan is complete. Pass the whole SPEC.md text as spec (at most 200 KB). A pure text check: nothing is stored, logged or sent anywhere.

piezas_contract

ChatGPT
Returns the Piezas platform rules: what the application owns versus what Piezas owns, the security rules for API keys, the spec-first and mock-first build order, the scenario-testing mandate, and which Piezas service covers which capability. Call this BEFORE designing or generating application code for a project that uses Piezas. It is also served in TOPIC SLICES: pass topic to get just the rules for the step you are on ("core" first, then "entities", "users", "integrations", "calendar", "documents", "deploy", "testing", or "patterns" as you reach each one) instead of re-reading the whole document. With no topic you get the full contract — the same one npx piezas init writes into a local project, delivered here for editors and agents that cannot run the CLI.

piezas_create_api_key

ChatGPT
Mints an API key for one app and returns its plaintext value ONCE — Piezas stores only a hash and can never show it again. This is the credential the application puts in its .env as PIEZAS_API_KEY. On an agent-token connection the key is for the token's own app; on a signed-in session name the app with app_id.

piezas_create_app

ChatGPT
Creates a new app in the signed-in user's Piezas account and returns its name, slug, id and the address it will have once deployed. Available on a signed-in Piezas session (OAuth); only the account's owners and admins may create apps. Ask the user for the app's name first. Deleting an app is not possible from here — that is done by a person in the Piezas console.

piezas_deploy

ChatGPT
Publishes a built app to Piezas hosting at its public address. Needs the project's FILES: pass the built output as a gzipped tar, base64-encoded (server.js at the top for a Node server such as Next.js .next/standalone; index.html at the top for a static site). So it works only in a client that has the project files (a desktop coding app or agent) — a web chat cannot deploy; tell the user to deploy from one of those. Never ask the owner about the Report a problem button: the app keeps its setting (a first deploy turns it on). The AI fixes first; the owner is asked once, for what only they can answer: one pause, remembered per item. Run the quality scan (on by default in a Piezas project) and its fixes, then piezas test last, after the final build, and put .piezas/test-attestation.json, .piezas/quality-attestation.json, .piezas/test-decisions.json and the owner's records (.piezas/owner-approvals.json or .piezas/state.json) and .piezas/deploy-link.json, as the project has them, at the top of the artifact (.piezas/ is removed before the app goes live). While checks fail, have no check yet or the scan found something, the deploy stops for YOU (up to three rounds) and the owner reads one progress line; never ask them whether to keep fixing. What is left after that (parts that still fail, parts that couldn't be checked, a rewritten check, the scan's leftovers, a homemade copy of the Piezas toolkit, a local database, or a key or sign-in secret visible in browser code) is ONE pause with one answer; what the owner already answered for exactly that item (the Piezas checks record it) is not asked again. Only the owner can confirm a pause ("deploy anyway"). The setting NAMES the app reads (never values) come with the owner's records (the CLI keeps them); a required one the live app lacks joins the pause by name; never ask the owner whether the settings are set. With the scan off, or no owner records in the build, the result says so. .env files are never uploaded.

piezas_deploy_instructions

ChatGPT
Returns the exact ordered steps to build, sign in the Piezas CLI, and deploy the project to Piezas hosting as one app. This server is REMOTE and cannot see or package the user's files, so it returns steps for YOU to run locally in the project directory — it deploys nothing itself. Name the app with app_id on a signed-in session.

piezas_init

ChatGPT
Sets up a Piezas-backed app in the user's project: returns the platform contract, the spec-first workflow, and an ordered directive to write them locally and run spec mode BEFORE any application code. It writes the contract and spec-mode files npx piezas init writes, not the rest of init (the guardrails, the SDK install, the test setup). Call it FIRST when the user wants to build something on Piezas. This server is REMOTE and cannot write files, so it returns the files' content for YOU to create in the project directory.

piezas_list_apps

ChatGPT
Lists the Piezas apps the signed-in user's account can reach — name, slug and id for each. Available only on a Piezas OAuth user session; an agent-token connection is bound to one app and uses piezas_app_info instead; pass an app's id as app_id to the app tools. It takes no arguments: the tenant comes from the session and Piezas decides server-side which apps this account may see. At most 50 are listed, and the result says so when the account has more. Call it to tell the user which apps exist before they choose one to build against.

piezas_whoami

ChatGPT
Shows which Piezas account this connection is signed in to: the person's email, their organization, their role, and whether the connection covers every app the account can reach or one app. Use it when the user asks who or which account they are connected as, or to confirm the connection works before acting.

piezas_app_info

Claude

piezas_capabilities

Claude

piezas_contract

Claude

piezas_create_api_key

Claude

piezas_create_app

Claude

piezas_deploy

Claude

piezas_deploy_instructions

Claude

piezas_init

Claude

piezas_list_apps

Claude

piezas_whoami

Claude

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/piezas"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/piezas)