Fine Structure Launches Claude MCP Connector and Open Source Claude Code Plugin

The MCP ecosystem the launch is joining

MCP, short for Model Context Protocol, is the open standard Anthropic published for connecting AI assistants to external tools and data sources. Instead of every vendor building a bespoke integration for every assistant, a service exposes a single MCP endpoint and any compatible client can discover and call the tools behind it.

Anthropic now runs two curated listings around that standard: a connectors directory for remote MCP servers that Claude users can add from their settings, and a plugin directory for extensions to Claude Code, the company's terminal based coding tool. Vercel, Neon and Notion are among the services already shipping connectors, and the app builder Base44 appears as an export destination inside Claude Design.

Most of those integrations are deliberately narrow. A deployment platform accepts a build, a database vendor exposes queries, a notes tool exposes documents. Fine Structure is arguing for a wider surface, a single connected destination that covers hosting, data, authentication and domains together, positioned as an alternative to static deploy targets that handle only the front end.

What the connector exposes

The connector sits at https://finestructure.ai/api/mcp and authenticates with OAuth 2.1 using dynamic client registration, so users do not generate API keys or paste tokens. Setup involves entering the URL in claude.ai connector settings and approving a consent screen, after which the assistant acts on the user's own Fine Structure account.

Behind that endpoint are roughly 69 tools spanning the lifecycle of an application:

• Application generation from a natural language description, and iteration on projects that already exist
• File reading and editing backed by saved versions, with rollback to an earlier state
• Database work, including entity schemas, records, queries and relationship validation
• Publishing to a live URL and attaching custom domains with automatic TLS certificates
• Access policies for routes and data, member roles, and traffic analytics

A plugin for developers who stay in the terminal

The version history is a larger detail than it looks. An assistant editing files without one gives the user no cheap way to undo a bad turn, so the connector treats saved versions and file restores as tools in their own right rather than as a hidden platform feature.

Alongside the connector, Fine Structure published a Claude Code plugin under the MIT license at github.com/finestructure-ai/claude-plugin. It adds three slash commands to the terminal client, /deploy, /fs-status and /fs-domain, covering deployment, project state and domain configuration.

The split between the two products is deliberate. The connector serves people who describe an application in conversation and never open an editor, while the plugin serves developers already running Claude Code against a local checkout who want a short path from repository to hosted environment.

Media tools left out on purpose

One notable part of the launch is a subtraction rather than an addition. Fine Structure sells AI media generation on its own platform, covering images, video and slideshows, and none of those tools appear on the connector surface. The company describes the omission as a compliance decision made to meet Anthropic's directory policy for connectors, and says the media features remain available through API tokens on the platform itself.

That trimming is becoming a visible cost of directory distribution. A vendor with a broad product line has to decide which parts belong in a listed connector and which stay behind its own authentication, and the boundary is set by the host's policy rather than by the vendor's roadmap. Users who connect from claude.ai will therefore see a narrower Fine Structure than users who log in to the platform directly.

Directory review still pending

Fine Structure has submitted the connector to Anthropic's connectors directory and the plugin to the plugin directory. Both submissions are under review, and neither is listed at the time of writing, so discovery currently depends on users adding the endpoint URL manually or installing the plugin from GitHub.

Directory placement is the variable worth watching. A listed connector is visible to every Claude user browsing the settings catalogue, while an unlisted one reaches only people who already know the product exists. For a platform whose pitch is that an assistant can carry a project from prompt to live domain in one place, that difference determines whether the integration functions as a distribution channel or as a convenience for customers it already has.

Questions readers ask

What is the Fine Structure MCP connector for Claude?

It is a remote Model Context Protocol server at https://finestructure.ai/api/mcp that gives Claude roughly 69 tools for building and running applications on Fine Structure, covering app generation, file editing with rollback versions, database schemas and records, publishing, custom domains with automatic TLS, access policies and traffic analytics.

How do you add the Fine Structure connector in Claude?

Users add the connector from the connector settings on claude.ai by entering the single endpoint URL and approving the consent screen. Authentication runs on OAuth 2.1 with dynamic client registration, so no API key or manual token is required. The connector had been submitted to Anthropic's connectors directory but was still under review in August 2026, so it is not yet installable from the directory listing.

Is the Fine Structure Claude Code plugin open source?

Yes. The plugin is published under the MIT license at github.com/finestructure-ai/claude-plugin and adds the /deploy, /fs-status and /fs-domain commands to Claude Code. It has been submitted to Anthropic's plugin directory, where the submission is under review.