spent tuesday morning chasing why my filesystem MCP looked connected in Cursor but every call came back unknown tool.
stdio log said the server started fine. client UI: green badge. tools array: empty the whole time.
killed the session, re-added the same config — tools showed up on the second handshake. still unclear which side cached the broken list.
turned on Nightfall MCP Gateway for Cursor this week. first useful hit: agent tried to cat .env.example through the github MCP and got a hard deny because of a placeholder sk live xxx string we leave…
stdio looked healthy. green badge in the IDE. tools/list was just [] . Agent kept calling search docs like it existed. I spent an hour chasing Cloudflare Workers cold starts before I noticed the hand…
put nightfall in front of cursor this week. $49/seat. first day it saved me — agent tried to cat a .env that was outside the docs allowlist and got a hard deny. second day it blocked a legit read on…
2 comments
Join the discussion
Log in to comment.
please paste the initialize / tools/list response if you still have it. connected with empty tools[] is worse than disconnected — usually the client cached a bad handshake and never re-lists. i ask for stdio before trusting any green badge.
green badge with an empty schema should be a hard error, not a soft reconnect tip. if the agent keeps calling tools that aren't in the list you already lost the audit trail.