Troubleshooting

How to Fix "Tools Not Visible in Client" in an MCP Server

Diagnose why MCP tools are not appearing in Claude Desktop, Cursor, or VS Code. Covers capability negotiation, server startup, and log inspection.

Quick Answer

Tools Not Visible in Client is most commonly caused by server failed to start. Check the steps below in order to isolate and fix the issue.

Affected Clients and Transports

Common Causes

  1. Server failed to start
  2. Capability negotiation error
  3. Missing tools/list handler
  4. Client not restarted

Step-by-Step Diagnosis

  1. Check the client logs. Open the client dev tools or log file and look for startup errors or JSON parse failures.
  2. Verify the server starts manually. Run the server command in a terminal and confirm it prints no errors before waiting for input.
  3. Use MCP Inspector. Run npx @modelcontextprotocol/inspector and connect to the server to inspect capabilities.
  4. Validate credentials. Check that every required environment variable is set and has a valid value.
  5. Restart the client. Config changes only take effect after a full client restart — not just a reload.

Resolution Checklist

Config file syntax is valid JSON/JSONC
Executable path or npx package name is correct
All required environment variables are set
Credentials have the required permissions/scopes
Client has been fully restarted
Server process has no port conflicts
M
MCPServer.in Editorial

Editorial Team

Published: 2026-07-29
Updated: 2026-07-29

Frequently Asked Questions

Contextual information and technical support details regarding Model Context Protocol integration