Cursor

Learn how to connect Sofy's MCP Sever with popular AI clients.

Cursor brings brand-consistent content generation directly into the development environment. Developers can apply Sofy brand voice to README files, API documentation, code comments, and user-facing text without switching tools. This integration ensures technical documentation maintains the same voice and tone as marketing content, creating a unified brand experience across all touchpoints. The Sofy MCP Server connection makes brand guidelines accessible during AI-assisted coding sessions, reducing friction in the documentation workflow.

Connect the Sofy MCP Server with Cursor to access brand voice and templates during AI-assisted coding and content generation.

Requirements

Cursor Pro subscription is required to use custom MCP servers. The free tier has limited integration capabilities.

Cursor version 0.41.0 or higher is recommended for MCP support. Check for updates in the Cursor application settings.

Setup instructions

1

Locate configuration directory

Find the Cursor configuration file location based on your operating system:

• macOS and Linux: ~/.cursor/mcp_servers.json

• Windows: %APPDATA%\Cursor\mcp_servers.json

If the file does not exist, create a new file named mcp_servers.json in the appropriate directory.

2

Open configuration file

Open the mcp_servers.json file in a text editor.

3

Add Sofy MCP Server

Add the following configuration:

{
  "mcpServers": {
    "sofy": {
      "type": "url",
      "url": "https://mcp.sofy.io",
      "name": "Sofy"
    }
  }
}

If other MCP servers are already configured, add the Sofy entry as an additional object within the mcpServers section. Ensure proper JSON syntax with commas between entries.

4

Save and restart

Save the configuration file and restart Cursor to apply the changes.

Using Sofy with Cursor

Once connected, Cursor's AI features can access Sofy brand assets during content generation and code documentation tasks.

Content generation

When writing documentation, README files, or user-facing text, reference Sofy explicitly in the prompt. Example: "Write this section using Sofy's brand voice."

Cursor will retrieve brand voice guidelines and apply them to the generated content.

Template usage

Request specific templates by name when generating structured content. Example: "Create a feature announcement using Sofy's Feature Spotlight template."

Cursor will fetch the template instructions and follow the defined structure and formatting.

Code documentation

Apply brand voice to code comments, documentation strings, and technical writing. Cursor can maintain consistency between code documentation and external content.

Troubleshooting

If the MCP server does not connect, verify the JSON syntax in the configuration file. Use a JSON validator to check for errors.

Confirm the file is saved in the correct directory for the operating system. The path varies between macOS, Linux, and Windows.

If authentication fails, check that the Sofy workspace is accessible. Verify that workspace settings allow MCP server access.

Restart Cursor completely after making configuration changes. The application must reload the configuration file to recognize new MCP servers.

Platform-specific notes

Cursor's MCP implementation is based on Visual Studio Code's architecture. Configuration files follow JSON format with strict syntax requirements.

MCP server connections in Cursor are persistent across sessions. Once configured, the Sofy server remains available until removed from the configuration file.

Cursor may cache MCP responses for performance. If brand voice or template changes are not reflected immediately, restart the Cursor application to clear the cache.

Advanced Configuration

Additional configuration options can be added to the Sofy MCP server entry:

• timeout: Set request timeout in milliseconds (default: 30000)

• retry: Enable automatic retry for failed requests (default: true)

• headers: Add custom HTTP headers for authentication or routing

Example advanced configuration:

{
  "mcpServers": {
    "sofy": {
      "type": "url",
      "url": "https://mcp.sofy.io",
      "name": "Sofy",
      "timeout": 60000,
      "retry": true
    }
  }
}

Most users do not need advanced configuration options. The basic setup works for standard use cases.

FAQs

What Cursor subscription is required to use Sofy?

Cursor Pro subscription is required to use custom MCP servers. The free Cursor tier has limited integration capabilities and does not support MCP connections. Users must upgrade to Pro to connect the Sofy MCP Server.

Where is the Cursor MCP configuration file located?

The configuration file location depends on the operating system. On macOS and Linux, the file is located at ~/.cursor/mcp_servers.json. On Windows, the file is at %APPDATA%\Cursor\mcp_servers.json. If the file does not exist, users must create it manually.

Why does Cursor not recognize the Sofy MCP Server after configuration?

Configuration file syntax errors prevent Cursor from loading MCP servers. Verify the JSON syntax is correct with no missing commas or brackets. Cursor must be completely restarted after saving configuration changes to recognize new MCP servers.

When should developers use Sofy brand voice in Cursor?

Sofy brand voice applies to README files, API documentation, code comments and any user-facing text generated in Cursor. Technical documentation should maintain the same voice and tone as marketing content to create consistent brand experience. Developers should reference Sofy explicitly in prompts when generating customer-facing content.

Do changes to Sofy brand voice update automatically in Cursor?

Cursor retrieves current brand voice settings from Sofy with each request. Changes to brand voice configurations or template definitions become available immediately. Cursor may cache responses for performance. Restart Cursor to clear the cache if recent changes do not appear.