Connect Fine Structure to Cline

Cline has a dedicated Remote Servers tab, so adding Fine Structure takes a name, a URL and a transport choice. The important detail is the transport value: it must be streamableHttp in camel case, or Cline falls back to the legacy SSE transport and the connection fails. Cline documents bearer token authentication, so create a scoped token before you start.

Before you start

• A Fine Structure account on the free tier or above.
• The Cline extension installed in VS Code or a compatible editor.
• A scoped MCP token created in the Fine Structure Studio MCP Server tab. Cline's remote server documentation describes bearer token authentication in the Authorization header and does not document an OAuth flow, so plan on a token.

Step by step

1. Create the token first: open the Fine Structure Studio, go to the MCP Server tab, choose whether the token covers the current app or all apps the account owns, pick a permission preset, and create it. Copy it immediately, because it is shown once.
2. In your editor sidebar, click the Cline icon.
3. Click the MCP Servers icon.
4. Open the Remote Servers tab.
5. Enter a Server Name such as finestructure and a Server URL of https://finestructure.ai/api/mcp
6. Choose Streamable HTTP as the Transport Type, not SSE.
7. Click Add Server.
8. To add the Authorization header, or to configure everything at once, click Configure MCP Servers to open the JSON and use the config snippet below.
9. Save, then ask Cline to list your Fine Structure apps to confirm the connection.

Configuration

{
  "mcpServers": {
    "finestructure": {
      "type": "streamableHttp",
      "url": "https://finestructure.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_FINE_STRUCTURE_MCP_TOKEN"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

What to watch out for

• The transport value is case sensitive: streamableHttp works, and streamable-http or an omitted type causes Cline to fall back to the legacy SSE transport, which typically surfaces as a 405 error.
• Cline's remote server documentation covers bearer tokens in the Authorization header and does not document an OAuth flow, which is the main practical difference from Claude, Zed or VS Code Copilot. Use a scoped Studio token rather than trying to force OAuth.
• Leave autoApprove empty at first so you see each tool call before it runs. Add read only tools to it later once you know the flow you want.
• A scoped token is the right lever here. Create a read only token to explore, then issue a build scoped one when you are ready to have Cline change files and publish.
• Revoke the token in the Studio MCP Server tab if you uninstall Cline or hand the machine to someone else. Removing the config entry does not invalidate the token.

Questions people ask

Why does my Cline connection return a 405?

Almost always the transport. Cline treats a missing type, or a type of streamable-http, as the legacy SSE transport, and the Fine Structure endpoint is streamable HTTP. Set "type": "streamableHttp" exactly as spelled.

Can Cline sign in with OAuth instead of a token?

Cline's documentation for remote servers describes bearer token authentication and does not document an OAuth flow, so treat the scoped Studio token as the supported path here.

Where do I get the token?

In the Fine Structure Studio, on the MCP Server tab. You choose the app scope and the permission preset, and the token is shown once at creation. It is revocable from the same tab.

Vendor documentation we checked

• https://docs.cline.bot/mcp/connecting-to-a-remote-server
• https://finestructure.ai/api/mcp/docs

All platforms: connect Fine Structure to any AI. Also the documentation and pricing.