Connect Fine Structure to Cursor

Cursor reads MCP servers from an mcp.json file, either per project or globally for your user. A remote server needs nothing more than a url, so the Fine Structure entry is three lines. Once saved, Cursor connects and prompts you to authenticate if the server requires it.

Before you start

• A Fine Structure account on the free tier or above.
• Cursor installed, with agent features available on your account.
• A decision about scope: .cursor/mcp.json in a project root shares the server with that repository, and ~/.cursor/mcp.json makes it available everywhere for you.

Step by step

1. Decide the scope: create .cursor/mcp.json in your project root, or ~/.cursor/mcp.json in your home directory.
2. Add the entry from the config snippet below. For remote servers the type field is not required, because Cursor only requires type for stdio servers.
3. Save the file and let Cursor pick it up, reloading the window if it does not.
4. Complete the authentication prompt when Cursor asks. Cursor's docs state that it supports OAuth for servers that require it, and Fine Structure registers the client for you.
5. Ask the agent to list your Fine Structure apps to confirm the tools are live.
6. If the OAuth handshake does not complete in your Cursor version, create a scoped token in the Fine Structure Studio MCP Server tab and add a headers object with Authorization set to Bearer plus that token.
7. If you use a token, reference it as ${env:FINESTRUCTURE_MCP_TOKEN} rather than pasting the value, since Cursor resolves variables in the url and headers fields.

Configuration

{
  "mcpServers": {
    "finestructure": {
      "url": "https://finestructure.ai/api/mcp"
    }
  }
}

What to watch out for

• Do not commit a project mcp.json that contains a literal token. Cursor supports ${env:VAR} references in url and headers precisely so secrets can stay out of the file, and a project file is the one most likely to end up in version control.
• Cursor's documentation covers static OAuth client credentials in an auth object with CLIENT_ID, CLIENT_SECRET and scopes, for providers that hand you a fixed client. Fine Structure does not issue those, so leave auth out entirely.
• Cursor's docs do not explicitly document OAuth 2.1 dynamic client registration for remote servers, so if your version does not raise a sign in prompt, the scoped token path is the reliable fallback rather than a workaround.
• A global ~/.cursor/mcp.json is usually the better choice for Fine Structure, because building and publishing apps is not tied to one repository.
• The tools are identical to the ones Claude and ChatGPT see. The only difference is that Cursor keeps the configuration in a file you can review and diff.

Questions people ask

Do I need to set "type": "http" in Cursor?

No. Cursor's docs say the type field is only required for stdio servers, so a remote entry with a url is complete. This differs from Claude Code, which does require a type when a url is present.

Project file or global file?

Use the global ~/.cursor/mcp.json unless you specifically want the server shared with a repository. Building and publishing apps is account level work rather than repository level work.

How do I revoke Cursor's access later?

If you used a scoped token, revoke it in the Fine Structure Studio MCP Server tab, which takes effect immediately. If you signed in with OAuth, remove the entry from mcp.json to stop Cursor from using it.

Vendor documentation we checked

• https://cursor.com/docs/mcp
• https://finestructure.ai/api/mcp/docs

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