Agent chat "No MCP resources available" when trying to use MCP

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Agent chat “No resources found - No MCP resources available” when instructing agent to use mcp server. I have tried using different mcps (local and remote) and all throw the same error, it was working just fine few days back.

Steps to Reproduce

Add context7 mcp to mcp.json

{
  "mcpServers": {
    "context7": {
      "command": "npx",
      "args": ["-y", "@upstash/context7-mcp", "--api-key", "<api-key>"]
    }
  }
}

instruct agent to use context7 mcp tool, fetch documentation and implement code.
The agent throws “No MCP resources available” box and goes on to use internet search.

Context7 package is latest, I have tried using remote mcp url too which leads to same result. Other mcp tools like which interact with local software also give same error, none of the mcps are working for me.

Expected Behavior

Agent should be able to list and use tools offered by the mcp.

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.41
VSCode Version: 1.105.1
Commit: 2ca326e0d1ce10956aea33d54c0e2d8c13c58a30
Date: 2026-01-16T19:14:00.150Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin x64 25.1.0

For AI issues: which model did you use?

Opus 4.5, Sonnet 4.5, Auto

Additional Information

Output Log for MCP: user-context7

2026-01-17 18:36:37.928 [info] Handling CreateClient action
2026-01-17 18:36:37.944 [info] Starting new stdio process with command: npx -y @upstash/context7-mcp --api-key <api-key>
2026-01-17 18:36:39.751 [error] WARNING: Using default CLIENT_IP_ENCRYPTION_KEY.

2026-01-17 18:36:39.849 [error] Context7 Documentation MCP Server v2.1.0 running on stdio

2026-01-17 18:36:39.855 [info] Successfully connected to stdio server
2026-01-17 18:36:39.856 [info] Storing stdio client user-context7
2026-01-17 18:36:39.856 [info] CreateClient completed, server stored: true
2026-01-17 18:36:39.866 [info] Handling ListOfferings action, server stored: true
2026-01-17 18:36:39.866 [info] Connected to stdio server, fetching offerings
2026-01-17 18:36:39.869 [info] listOfferings: Found 2 tools
2026-01-17 18:36:39.869 [info] Found 2 tools, 0 prompts, and 0 resources

Does this stop you from using Cursor

Yes - Cursor is usable but I need to use mcp tools

Edit: opened a new chat windows asked agent to list all the mcp tools it has access to and then asked it to use them and it worked, but the no mcp resource available error comes up too often to just open a new chat tab wasting a request to list tools

4 Likes

exact same issue here! hope this gets fixed asap

Hey, thanks for the detailed report. I can see the screenshot with the error.

What’s interesting is the logs show the MCP server connects fine and finds 2 tools, but the agent can’t see them. This is a known issue with tool discovery.

Your workaround of starting a new chat is still the best option for now. For some users, this also helps:

  • Restart Cursor after setting up MCP
  • Explicitly mention context7 in the prompt

For engineering, can you share the Request ID from the broken chat? (Three dots in the top-right corner of the chat > Copy Request ID.) This will help us figure out why discovery isn’t working.

Same here.

Cursor reports that the agent cannot find resource with list_mcp_resources .
The request id is 42b20ba0-4963-45a4-bf1a-9839495f35a8.

More detailed report generated by cursor:

Hi, I’m encountering the same issue as described in this thread: agents cannot retrieve MCP resources despite MCP servers being configured.

Setup Details

  • I have configured MCP servers in .cursor/mcp.json:
    • confluence-PROJECTNAME (configured with URL: https://mcp.atlassian.com/v1/sse)
    • another-confluence-PROJECTNAME (configured globally in Cursor settings)
  • Both servers appear to be connected (I receive error responses, not connection failures)

Issue Behavior

When using the agent to access Confluence pages:

  1. list_mcp_resources returns no resources available for both servers
  2. fetch_mcp_resource with various URI formats results in “Method not found” error (-32601)

Additional Technical Details

  • Cursor version information (I updated that today, and I believe that’s most possible cause):
    Version: 2.3.41 (user setup)
    VSCode Version: 1.105.1
    Commit: 2ca326e0d1ce10956aea33d54c0e2d8c13c58a30
    Date: 2026-01-16T19:14:00.150Z
    Electron: 37.7.0
    Chromium: 138.0.7204.251
    Node.js: 22.20.0
    V8: 13.8.258.32-electron.0
    OS: Windows_NT x64 10.0.26100

  • Full content of .cursor/mcp.json
    {

    “mcpServers”: {

    "confluence-PROJECTNAME": {
    
      "url": "https://mcp.atlassian.com/v1/sse"
    
    }
    

    }

    }

  • Other environments:

    • I’m working with agent mode chat.
    • Working inside devcontainer.

Same issue for me. My MCP servers all load fine but when agent tries to see what it has, it gets No resources found most of the time.

Same problem with me, Request Id is a263d4d9-9202-4bf4-8b09-8ddc35db22dd

Same. MCP for Supabase was working yesterday, I believe I updated Cursor and that was the issue.

I see this in my logs:
2026-01-17 14:43:37.493 [info] Found 20 tools, 0 prompts, and 0 resources

And a repeated refrain from my agent “I still cannot invoke MCP tools directly — my available functions don’t include MCP tool calls, only list_mcp_resources and fetch_mcp_resource (which are for resources, not tools).”

Updated to:
Version: 2.3.41
VSCode Version: 1.105.1
Commit: 2ca326e0d1ce10956aea33d54c0e2d8c13c58a30
Date: 2026-01-16T19:14:00.150Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.1.0

None of my MCPs are working anymore

Same issue here.

Restarting Cursor did not fix it, and explicitly mentioning the MCP server (Context7, TaskMaster, etc) also did not fix it.

Also tried uninstalling and reinstalling, Cursor and all the MCP’s, but that still did not fix it.

MCP’s are just completely dead.

I have the same issue, nothing works.

I restarted cursor, tryed with multible new chats and diffrent models! All MCP‘s dont work!!!

I have the same issue, clearly this is the issue happening after updating the cursor. This is a serious issue. Without mcp, it’s hard to work with. Please look into this quickly and release an update.

2 Likes

Same here - tried everything

No matter what i do, i get this:

1 Like

Same issue here since the weekend. Severe issue affecting the overall usability of Cursor.

Request id 481d09dd-5570-4216-9b7d-e4e78f4661aa

Downgrading to Cursor 2.2 fix the issue for me

1 Like

Wow….. how is it possible to have such bad testing practice, so that something that central can be released totally broken?

1 Like

Thanks @ikedam for sharing that Request ID - that should help the team investigate.

For anyone else hitting this, the workarounds from deanrie are still the best options: starting a new chat, restarting Cursor after MCP setup, or explicitly mentioning the MCP server name (e.g., “use context7”) in your prompt. Team is investigating this issue. We’ll share any updates here.

1 Like

Tried this, didn’t work for me

I reset my MacBook, installed Cursor and I still have the same problem

This issue has persisted for two days, affecting developers globally, and Cursor’s handling of it has been unsatisfactory. The comments confirm that the problem remains. Downgrading to version 2.3.35 fixed the issue for me, so I suggest others experiencing it do the same. The ongoing feedback indicates that the issue is far from resolved.

1 Like