A connected MCP server may still expose no tools, have tools blocked by permissions, or leave them waiting for on-demand discovery. Start with /mcp and the server’s tool count. Reinstalling before checking those details can send you after the wrong problem. 123
Check what the server actually exposes
Run claude mcp list from the project folder, then inspect /mcp inside the session. Record the server name, status and tool count before changing anything. 1
MCP servers can provide tools, resources and prompts. A connection alone does not promise that all three are available. Compare the server’s documented capabilities with what the client reports. 2 For an Analytics integration, for example, establish whether report-reading tools are exposed before investigating a particular property.
Check permission rules and deferred tools
A permission rule can block one MCP tool or an entire server. Inspect the active rules and their scope; ask the administrator about a managed restriction instead of removing controls globally. 3
Current Claude Code normally discovers MCP tools on demand. A tool marked as deferred is not necessarily missing. 1
Verify one useful operation
Choose one small read operation, such as listing the Analytics properties you can access. Request that operation by name and keep the exact error if it fails.
If the tool runs but rejects the account, property or query, investigate that response separately. You have moved beyond the original discovery problem. A useful support report includes the client version, server version, tool count and redacted error; it should never include an API key or refresh token.