Skip to content
Picasi Picasi Picasi Documentation
Open App

The MCP server is not responding

Short Answer

If the Picasi MCP server isn’t responding, it’s usually due to an invalid API token, an outdated configuration file, or the MCP server not being properly integrated into the AI application.

Details

Check the token:

In Picasi, go to Settings → API Token and check whether the token is still present and active. If you click Show Token, you will see the full token. Copy it again and replace the value in your .mcp.json or your configuration.

Check the configuration file in Claude Code:

Open ~/.claude.json or the project-specific .mcp.json and check:

  • Is PICASI_API_TOKEN set correctly?
  • Is the URL (https://picasi.app/mcp) correct?
  • Is the JSON syntactically correct (no missing commas, no incorrect quotation marks)?

Claude Desktop / ChatGPT (OAuth):

For OAuth-based connections, the session may have expired. Open Picasi under Settings → Connected Apps and check if the connection is still active. If not, revoke it and reconnect via Settings → Connect AI Assistant.

Reload MCP server:

In Claude Code: Type /mcp in the chat and check if picasi is listed as a connected server. If not, restart the application—MCP servers are loaded on startup.

If nothing works:

Create a new API token (this will invalidate the old one), update all configuration files, and restart the AI Assistant.