Agent Is not able to access the MCP Despite they are fully active

I have restarted cursor , new chat , again login and everything but still stuck there, tried different llm as well including opus 4.6 but still cursor agent is not able to access figma or neon mcp

my cursor version is also latest

Version: 2.5.20
VSCode Version: 1.105.1
Commit: 511523af765daeb1fa69500ab0df5b6524424610
Date: 2026-02-19T20:41:31.942Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.2.0

1 Like

Hey, this is a known issue. MCP servers can show as connected (green), but the agent can’t discover or use their tools.

A few things to try:

  1. Toggle the MCP servers: go to Cursor Settings > Tools & MCP, turn off Figma and Neon, then turn them back on. Restart Cursor after.

  2. Start a fresh chat. In your first message, explicitly reference the MCP by name, for example: “Using the Figma MCP, inspect the design for…” This can kick off tool discovery for that session.

  3. In a new chat, try: “List all MCP tools you have access to.” After the agent lists them, it should be able to use them for the rest of that session.

The team is aware of this. To help with prioritization, can you share:

  • A Request ID from a chat where the tools aren’t being found (three dots in the top-right of the chat > Copy Request ID)
  • Where Figma and Neon are configured, in .cursor/mcp.json (project level) or in global Cursor settings?

Let me know how it goes.

Please fix this, have been experiencing this constantly. Currently I am moving all my MCP deployment to docker to make sure the stability. Cursor MCP stabiilty issue is making MCP usage slower than I querying the data sources myself.