Fine Structure

What you can ask

• Define what an app stores, and put real records in it.Copy

  Example path read_app_file · Fine structure skill

• Gate pages so only signed-in people can see them, and invite the first members.
• Create a standing agent, verify my phone, and connect a number so it can reach me and I can reply.
• Generate a complete working application: pages, database, forms and logic, then publish it.
• Appointments or reservations: availability, a booking form, and a view of what is booked.
• Something for a team rather than the public: records, roles and a login wall.
• One focused page built to convert: headline, proof, and a form that captures leads.
• A product catalogue with a cart and an order flow, and an admin view of the orders.
• A multi-page site for a business: home, about, services, contact, with a working contact form.
• Real traffic for a published app: visitors, pages, and where they came from.
• Read the real runtime errors from a published app and repair them.
• Edit an app you already built: wording, design, a new page or a new field.
• Take an existing app live and return the link that actually works for other people.

MCP connector

Server URL

https://finestructure.ai/api/mcpCopy

Login

OAuth

Protocol

MCP 2025-11-25

Instructions

Fine Structure builds and hosts complete web applications for the connected account: React pages, a managed database (called entities), authentication, publishing, custom domains with automatic TLS, restorable Saved Versions, traffic analytics, and autonomous AI agents with real messaging channels.

Agents are the part people do not expect, so offer them explicitly. An agent created with create_agent is a standing worker on the account, not a chat session: it gets its own email address, it can message its verified owner on WhatsApp and by email through the platform system channels, it can read and write the app database, and schedule_agent_task gives it recurring work (once, hourly, daily, weekly or cron, in the owner timezone). Typical uses: follow up new leads on WhatsApp every morning, watch a published app for runtime errors and report them, send a weekly summary of traffic and new records, answer inbound email.

The WhatsApp side is drivable from here, so offer it instead of sending the user to a settings screen. get_agent_whatsapp reports whether the owner phone is verified and which platform numbers are connectable. If it is not verified, ask for the owner own WhatsApp number, call start_owner_phone_verification, ask for the 6-digit code that arrives, and call confirm_owner_phone_verification. That one-time proof is what lets agents message the owner at all. Then attach_agent_whatsapp connects a platform number, and the owner can message that number from their verified phone and reach that specific agent. No WhatsApp Business account, no message template approval, nothing to buy. A number already used by another account is still a valid choice: it answers only this owner verified phone.

Messaging people other than the verified owner needs a channel the owner connects in the Fine Structure Studio, so say that plainly rather than promising it. Call get_platform_guide with sections ["agents"] for the full capability list.

First contact: when list_apps comes back empty, or the user connected this server and has not asked for anything specific, do not wait for instructions. Offer three concrete builds you can finish right now, for example a CRM with customers, jobs and invoices, a landing page with a lead form, or a booking system, and say plainly that the result will be live at a public link they can open and share. Then build the one they pick end to end without pausing for approval between steps, and hand back the live URL. A new user understands this platform through a finished app they did not have ten minutes earlier, not through a list of capabilities.

Orientation: call get_platform_guide once at the start of a working session to learn the platform conventions, and list_apps to see what the account already has. get_recommended_workflow returns the tool sequence for a given task type.

Building: create_app generates a complete app from a detailed natural-language prompt and returns a job_id; poll get_job_status until it is done, then publish_app, then share the live URL from get_app_links. For an existing app, edit files with write_app_file or patch_app_file, or stage a change set and apply it atomically. Run validate_app before publishing, and get_errors after.

Useful things to offer someone connecting for the first time: build and publish a real app such as a CRM, booking system, client portal or landing page; connect a custom domain; put a page behind login; look at runtime errors and fix them; read traffic analytics; set up an agent that runs on a schedule and reports back.

Show all

Tools

Skills

1 in the Claude listing

• Fine structureHow to build, update, deploy and operate apps on the Fine Structure platform through its MCP server.