Cursor MCP 'No server info found' After Restart — Tools Not Loading

What this error means

[error] No server info found is a Cursor failure pattern reported for developers trying to fix cursor mcp servers not loading tools after restart with ‘no server info found’ errors. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

After Cursor restart, MCP tools stop loading. Log shows repeated ‘Handling GetInstructions action’ followed by ‘[error] No server info found’. Affects Atlassian MCP server and potentially other MCP integrations.

Common causes

• After restarting Cursor, MCP tools stop loading with repeated ‘No server info found’ errors in the log. Developers using Atlassian or other MCP integrations lose productivity until this is resolved.
• After Cursor restart, MCP tools stop loading. Log shows repeated ‘Handling GetInstructions action’ followed by ‘[error] No server info found’. Affects Atlassian MCP server and potentially other MCP integrations.

Quick fixes

1. Confirm the exact error signature matches [error] No server info found.
2. Check the Cursor account, local tool state, and provider configuration involved in the failing workflow.
3. Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

• Verify the command, editor, extension, or API client that produced the error.
• Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
• Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

1. Capture the exact error message and the command, editor action, or request that triggered it.
2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
3. Review the source evidence below and compare it with your environment.
4. Apply one change at a time and rerun the smallest failing action.
5. Keep the working fix documented for the team or deployment environment.

How to prevent it

• Keep provider/tool configuration documented.
• Record non-secret diagnostics such as tool version, provider name, model name, and command path.
• Add a lightweight check before CI or production workflows depend on the tool.

Sources checked

• https://github.com/atlassian/atlassian-mcp-server/issues/56

Evidence note: After Cursor restart, MCP tools stop loading. Log shows repeated ‘Handling GetInstructions action’ followed by ‘[error] No server info found’. Affects Atlassian MCP server and potentially other MCP integrations.

Related errors

• Cursor MCP connection refused
• Cursor MCP tools disappeared after update

FAQ

What should I check first?

Start with the exact [error] No server info found text and the smallest action that reproduces it.

Can I ignore this error?

No. Treat it as a failed Cursor workflow until the root cause is understood.

Is this guaranteed to have one fix?

No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.

How do I know the fix worked?

Rerun the same command, editor action, or request. The fix is working when that action completes without [error] No server info found.