Developer Tools
finestructure.ai
Creates, updates, and publishes applications from natural language prompts.
ENDPOINT 1
https://finestructure.ai/api/mcp
MCP server metadata
- Name
- fine-structure-mcp
- Version
- 1.0.0
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. Costs: create_app and update_app spend the account's credits. File edits, publishing, domains, data tools and analytics do not. A free tier exists. Safety: every write creates a restorable Saved Version. Tools whose annotations mark them destructive delete or replace data, so confirm with the account owner before calling one. Authentication and credit errors are not retryable: report them to the user instead of looping.
Known tools 82
get_platform_guideReturn a machine-readable Fine Structure / FSe2 guide for AI agents.
Inferred read-onlyget_app_linksReturn editor, preview, published path, subdomain, and custom-domain links plus whether each works for anonymous visitors, app users, or Studio users based on publish and auth settings.
Potential side effectslist_app_domainsList an app's platform path, subdomain, and configured custom domain with verification, SSL, primary-domain, redirect, publish, and login-gating status.
Potential side effectsadd_custom_domainAttach or replace the app custom domain through the same Fine Structure Studio custom-domain flow.
Inferred read-onlyget_domain_verificationReturn the exact DNS records and instructions required to verify and route the app custom domain.
Inferred read-onlycheck_domain_verificationCheck Fine Structure custom-domain verification and SSL status for the configured custom domain, then save the latest status.
Inferred read-onlyset_primary_domainSet which app host should be treated as primary for generated links and custom-domain redirects.
Inferred read-onlyremove_custom_domainRemove the configured custom domain from the app and clean up the platform-side hostname registration when possible.
Potential side effectsget_domain_ssl_statusReturn SSL/certificate status and pending certificate validation DNS records for the app custom domain.
Inferred read-onlyconfigure_domain_redirectsConfigure custom-domain redirect policy: primary domain, optional www/root redirect, and HTTPS enforcement.
Inferred read-onlylist_appsList applications owned by the authenticated user, newest activity first.
Inferred read-onlyget_app_detailDeep introspection of an app: entities, pages, settings, integrations, environment variables, and file structure.
Inferred read-onlyquery_entityQuery app data records for one entity with optional exact-match filters.
Inferred read-onlyget_app_analyticsTraffic analytics for an app's published site over a chosen window: total views, unique visitors, daily series, top pages, top referrer domains and device split.
Inferred read-onlylist_saved_versionsList restorable Saved Versions for an app, including versions created by MCP writes.
Inferred read-onlyvalidate_change_setValidate current app files plus staged change set files before applying.
Inferred read-onlyvalidate_appRun deterministic app checks: syntax, imports, routes/pages, entity schemas, missing entities, and recorded runtime errors.
Inferred read-onlyinspect_previewReturn server-side preview context: URLs, persisted runtime/network errors, static clickable candidates, pages, and explicit live-browser availability.
Inferred read-onlyget_app_security_contextReturn safe security context for one owned app: owner id/email, Studio collaborators, generated-app members, route policies, entity policies, and recent security audit entries.
Potential side effectsset_route_policyCreate or update a server-owned route policy for a generated app route.
Potential side effectsset_entity_policyCreate or update server-side read/write role policy for an app entity.
Potential side effectscompare_saved_versionsCompare two Saved Versions and return per-file additions, removals, modifications, and compact diffs.
Inferred read-onlycompare_current_to_versionCompare the current app files to a Saved Version and return compact per-file diffs.
Inferred read-onlyrestore_file_from_versionRestore one file from a Saved Version instead of restoring the entire app.
Inferred read-onlyvalidate_entity_relationshipsValidate entity relationship metadata and *_id references against existing entity schemas.
Inferred read-onlylist_integrationsList supported integrations and safe connected integration metadata for an app.
Inferred read-onlycreate_ab_testCreate a native Fine Structure A/B test between existing app pages.
Potential side effectsupdate_ab_testUpdate a native A/B test, including active state, variants, traffic, and conversion goal.
Potential side effectsget_ab_test_statsGet views, unique visitors, conversions, and conversion rates for an A/B test.
Inferred read-onlycreate_agentCreate an autonomous AI agent on the user's Fine Structure account: a standing worker, not a chat session.
Potential side effectslist_agentsList the AI agents on the user's account with id, name, role, status and FineMail address.
Inferred read-onlylist_agent_tasksList scheduled tasks for one agent (or the whole account), including schedule, status and next_run_at.
Inferred read-onlyget_agent_whatsappRead the WhatsApp state of the connected account: whether the owner's phone is verified, which platform numbers they can connect, and which conversations already route to which agent.
Inferred read-onlystart_owner_phone_verificationSend a 6-digit code over WhatsApp to the ACCOUNT OWNER's own phone.
Potential side effectsconfirm_owner_phone_verificationConfirm the 6-digit code the owner received on WhatsApp from start_owner_phone_verification.
Inferred read-onlyattach_agent_whatsappConnect a platform WhatsApp number to one of the account's agents, so the owner can message that number and reach that agent.
Potential side effectsdetach_agent_whatsappDisconnect the owner's WhatsApp route from a platform number.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.fine-structure-mcp]
url = "https://finestructure.ai/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"fine-structure-mcp": {
"type": "http",
"url": "https://finestructure.ai/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: fine-structure-mcp
Remote MCP URL: https://finestructure.ai/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"fine-structure-mcp": {
"url": "https://finestructure.ai/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"fine-structure-mcp": {
"type": "http",
"url": "https://finestructure.ai/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "fine-structure-mcp",
"transport": "streamable-http",
"url": "https://finestructure.ai/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.