Cursor CLI - Not actually an MCP client?

Describe the Bug

I have an mcp.json file set up for my project, and I am able to get the in-IDE agent to use the tools. However, the CLI doesn’t seem to be able to use them.

Steps to Reproduce

Create mcp.json file, launch cursor-agent, try to ask it to use the tools

Expected Behavior

cursor-agent can use MCP tools (ideally with a /mcp command to view connected servers, and/or a --mcp flag to pass when launching to specify which servers it should use, like Claude Code has)

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.2.4
VSCode Version: 1.99.3
Commit: a8e95743c5268be73767c46944a71f4465d05c90

Additional Information

cursor-agent --version
32c684dc5c8a0e364043db77d4e5b9a5dc1e2d3b

Does this stop you from using Cursor

No - Cursor works, but with this issue

9 Likes

Pretty confused about this… am I missing something? I’ve tried a few more things but this part of the docs just seems incorrect

3 Likes

I have this same issue. One MCP (Serena) launches a web browser when I start Cursor CLI so it appears to be “registered” but it will not find any or use any MCP server when asked.

2 Likes

Ok now it seems able to use MCP tools with a new update, but I’m encountering lots of weird bugs. It will run the same tool several times in a row (not acknowledging the previous call’s output), and it seems that using a tool immediately stops the agent from proceeding onto additional steps and awaits a user message.

A bit disappointed by the experience so far, because in general I’m very excited about this product! I don’t mind bugginess for new features, but I’d love some type of ack / update in this thread to at least acknowledge that you’re aware of this or working on it… Fwiw, the CLI is basically unusable for me unless I can connect it with MCP tools

what update do you talk about please ?
I installed cusror cli today (version = 2025.08.09-d8191f3) and have the same issue : mcp servers are not automatically discovered/started and when I ask the agent to use an mcp server listed in the global config file (~/.cursor/mcp.json) it does not seem aware about it and try to write a curl command to interact with the API of the tool the MCP is supposed to interact with

Note: i only installed ”cursor CLI” and do not have any previous cursor installation

1 Like

Yeah I’m seeing the same thing here. it seems Cursor CLI does not pull in global config file (~/.cursor/mcp.json).

1 Like

I’m encountering the same issue with both project settings (./.cursor/mcp.json) and global settings (~/.cursor/mcp.json). When using project settings, I get the following error:
Error: MCP error -32000: Connection closed

When using global settings, there’s no error, but the file isn’t recognized.

However, if I change ./.cursor/mcp.json to ./.mcp.json, ClaudeCode recognizes it correctly, so it’s probably not a formatting issue.
Thank you.

Describe the Bug

Cursor CLI not respecting global mcp and rules configurations stores in ~/.cursor. It does work with project specific configurations.

Steps to Reproduce

  1. Install Cursor CLI
  2. Store some user specific configurations i.e. mcp and rules in ~/.cursor/mcp.json and ~/.cursor/rules/custom-rule.yaml
  3. Start the agent with cursor-agent
  4. Notice the configuration isn’t being respected

Expected Behavior

It should honor the global user specific configurations stores in ~/.cursor/.

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

The latest version as of writing this.

Additional Information

We are trying to pack the Cursor CLI in a module to be used with Coder Tasks feature.

Does this stop you from using Cursor

Yes - Cursor is unusable

I have the same error. When is it planned to be fixed?

I have tested with MCPs in project folder .cursor/mcp.json and it works well with latest version 2025.08.15-dbc8d73

Please update your agent with cursor-agent update and let me know if you can use project MCPs.

It seems like system wide config of ~/.cursor/mcp.json is not yet supported for now but I have updated the team for this.

Thanks for reporting this. It seems that project-level rules are working, but global config isn’t working. The team has been notified about this.

Would using project-level configurations work for you?

Can you also try updating with cursor-agent update and see if that works?

1 Like

hi @matifali also to add to my colleagues notes above: rule files use the path .cursor/rules/*.mdc but not as yaml files or in global folder.

Could you check if you have proper Project Rules setup in IDE and then test them in CLI as they are supported.

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.