Fine Structure exposes its whole build pipeline as one remote MCP server, so the assistant you already use can generate a complete app from a prompt, edit its files, shape its database, publish it, and attach a custom domain. There is nothing to install and nothing to self host: you point your AI client at a single HTTPS endpoint and sign in. Most clients handle the sign in through OAuth, and the few that only accept a fixed token read a scoped token you create in the Fine Structure Studio. Every page below gives one platform's current click path and the vendor documentation we checked it against.
The server publishes roughly 70 tools over the OAuth surface, which is enough for an assistant to take a product from a sentence to a live URL without you leaving the chat window. It can call create_app to generate a working application from a prompt, then read and patch individual files, then publish, then point a domain at the result.
The same tools behave the same way in a chat client and in a coding editor. What differs between platforms is only how each vendor lets you register a remote server and how it handles authentication.
The endpoint is https://finestructure.ai/api/mcp and it speaks streamable HTTP. If your client supports OAuth 2.1 with dynamic client registration, that is the whole setup: paste the URL, and the client registers itself and sends you to a Fine Structure sign in page. There is no API key, no client ID and no client secret to create or paste anywhere, and our authorization server uses public clients with PKCE, so there is no static secret to leak.
Some clients only support a fixed bearer token. For those, open the Fine Structure Studio, go to the MCP Server tab, and create a scoped MCP token. You choose whether it is locked to the current app or covers every app the account owns, you pick a permission preset such as read only or build, and the token is shown once. Send it as an Authorization Bearer header, and revoke it from the same tab whenever you want to cut access off.
Remote MCP support arrived quickly and unevenly. Some platforms ship a one field form for any MCP URL, some hide it behind a developer mode, some only accept a remote server in their enterprise or IDE products, and some are still labelled pre release by the vendor. We say which is which.
Registering a server and having a working server are different states, and most clients will happily show a connector that never authenticated. Ask the assistant to list your Fine Structure apps: if it returns your app names, the handshake completed. If it says it has no tools, the sign in did not finish. Where a client reports a health state, read it. Claude Code prints Connected, Needs authentication or Failed to connect per server, which separates a bad URL from a bad login.
Tools that change something are treated as write actions by most hosts, so expect a confirmation prompt the first time your assistant publishes, patches a file or edits a record. That is the host protecting you, not a Fine Structure setting. File edits also create a Saved Version automatically, so a bad edit is recoverable rather than final.
No. On any client that supports OAuth 2.1 with dynamic client registration you paste https://finestructure.ai/api/mcp and sign in. A token is only involved when a client can send nothing but a fixed Authorization Bearer header, and then it is a scoped token from the Studio MCP Server tab rather than a permanent account key.
Probably. Any client supporting a remote MCP server over streamable HTTP can use the endpoint, whether or not we have written a page for it. Give the client the URL, and if it needs a fixed credential instead of OAuth, give it a scoped token from the Studio MCP Server tab as an Authorization Bearer header.
It is listed in Anthropic's connector directory as a Community connector. That means listed, not verified or endorsed, and we will not describe it as either. Check that the publisher is who you expect before you connect, as with any third party server.
Yes. Tokens from the Studio MCP Server tab can be locked to one app or scoped to every app the account owns, with a permission preset such as read only or build chosen before the token is issued. Revoking it stops anything using it immediately.
No. A free account is enough to connect a client and start building, and no credit card is required. Requirements on the other side vary by vendor, and each platform page states what that vendor documents.
Fine Structure account: a free account is enough to connect a client.
Pointing an assistant at a third-party server is a question of trust, so here is where Fine Structure appears independently of this site. Each of these catalogues resolves the same endpoint and several run their own health checks against it.
See also the product overview, the documentation, and pricing.