18 days ago
I have four projects, and I just deployed the Postgres MCP connector.
So far, they have been extremely flaky trying to use them in Perplexity as well as Claude desktop.
It seems they work for a little while, and then they don't work, and then I'm getting time outs.
Is there anything I'm missing here to use these properly? Are there any settings I can provide that maybe I'm doing something wrong?
For example, right now, by Claude Chat in Claude Desktop is trying to list schemas and it's timing out. But then other times this morning, it works fine.
1 Replies
Status changed to Open Railway • 18 days ago
16 days ago
By default, Claude Desktop has a strict 60-second initialization and execution budget for MCP tools. If your Postgres server takes too long to wake up, or if list_schemas / list_tables takes more than a few seconds, Claude kills the transport stream.
You can explicitly inject an environment variable directly into your claude_desktop_config.json to extend this budget:
{
"mcpServers": {
"postgres": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-postgres",
"postgresql://username:password@localhost:5432/mydb"
],
"env": {
"MCP_TIMEOUT": "300000"
}
}}
}