Who is this for?
Users who pasted MCP config but cannot see tools in their AI client.
Config path and example
Client MCP config and logs
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "./"]
}
}
}Installation steps
1
Validate config syntax
Make sure JSON or TOML is valid and the server name is correctly quoted.
2
Confirm config path
Check you edited the config path used by the active client or project.
3
Test command manually
Run the command from terminal to confirm it can start.
4
Restart completely
Fully quit and reopen the client, not just the chat session.
5
Check logs
Client logs usually show command, permission, or token errors.
Common setup issues
Config saved in wrong file
Project-level and global config files are different.
Missing environment token
Some servers require API keys or app permissions.
FAQ
Does restarting matter?
Yes. MCP clients often load servers only on startup.
What is the fastest fix?
Validate config, run command in terminal, then restart the client.