How to Add an MCP Server to Cursor

Download Hemory
On this page

MCP setup instructions are not interchangeable across clients. A server entry copied from Claude Code or VS Code may use a different configuration location, scope, or structure, so copying it into Cursor unchanged can leave the server unavailable.

The safe approach is to choose whether the server should apply to one project or across your Cursor use, follow Cursor’s current MCP configuration instructions for that scope, and check the result in Cursor. The exact file path and configuration format should come from Cursor’s documentation; don’t assume another client’s example is valid.

1. Choose project-level or global configuration

Use project-level configuration when the server is needed for a particular repository or project. This keeps the setup associated with that work rather than applying it everywhere. Use global configuration when you want the server available across projects.

Before choosing, consider whether the project’s configuration will be shared with other contributors. Keep credentials and other sensitive values out of shared files unless the project’s security practices explicitly allow them.

2. Follow Cursor’s configuration format

Start with the server provider’s connection instructions, then use Cursor’s own documented format and location. The server’s connection details may be reusable, but the surrounding configuration structure can differ by client. In particular, don’t assume that a top-level key, file path, or project-versus-global convention from Claude Code or VS Code carries over to Cursor.

Use Cursor’s current documentation or MCP settings to confirm the exact location and required fields. This guide does not prescribe a configuration block because those client-specific details need to match Cursor’s current instructions.

If the server needs credentials or environment values, use the method its provider and Cursor document. Avoid placing secrets in a shared project file or exposing them in screenshots, source control, or messages.

3. Confirm that Cursor recognizes the server

After applying the configuration, check Cursor’s MCP settings for the server and its connection status. If it does not appear or is unavailable:

  1. Recheck that you used the correct project or global location.
  2. Compare the structure and required fields with Cursor’s current instructions, not a sample for another client.
  3. Confirm that the server’s own connection details and any required credentials are present.
  4. Reopen or refresh the relevant Cursor view if its instructions call for that step, then check the status again.

A server appearing in the settings is a useful registration check. It does not, by itself, establish that every tool or permission is working as intended. Check the capabilities you actually need using the server and client documentation.

Where Hemory fits

Hemory describes a standard MCP Server capability, and Cursor is publicly listed as a client. That listing is not independent verification of a particular Cursor setup. Use Hemory’s current connection instructions together with Cursor’s configuration requirements; do not infer a Hemory endpoint, configuration block, tool list, or permission scope from another MCP client’s example.

FAQ

Should I use project-level or global MCP configuration in Cursor?

Choose project-level configuration when the server belongs to one project; choose global configuration when you want it available across projects. Consider whether project configuration will be shared before placing any sensitive values there.

Can I copy an MCP configuration from Claude Code or VS Code?

Use it only as a reference for the server’s connection details. Check Cursor’s documented path, scope, and format before adapting it; client-specific configuration structures are not guaranteed to match.

What should I check if the server does not appear in Cursor?

Check the configuration location and format against Cursor’s current instructions, then confirm the server’s required connection details and credentials. Use the status shown in Cursor and the server’s documentation to narrow down the issue.

The reliable outcome is a server registered in the intended Cursor scope and visible in Cursor’s MCP settings. Use Cursor’s current documentation for the exact path and syntax, and verify the capabilities you need rather than assuming another client’s setup or permissions apply.

Related reading

Start building your memory palace

Download Hemory — from today on, every real conversation becomes material you can generate from tomorrow.

Get Hemory for iOS Get Hemory for Android Download APK

macOS, Windows, Linux, Web, and Self-host coming soon