Why Cody can only query postgresql table schema but can't directly get the data?

Cody
1

I’m using the same MCP: servers-archived/src/postgres at main · modelcontextprotocol/servers-archived · GitHub

  1. Configure with github copilot, I can get table schema, and also I can directly ask it to give me the data of every record in table
  2. But after configure with cody, I still can get the table schema, but I can’t get the data records of the table, it told me next:

I don’t have access to the actual data in the database. The information I provided was based on the schema definitions you shared, which only describe the structure of the tables (column names and data types).

To view the actual data in these tables, you would need to connect to the PostgreSQL database and run queries. Here’s how you could do that:

psql > postgresql://lavaserver:lavaserverdbpass@10.192.244.104:5432/lavaserver

Why difference for cody and copilot to get the data with the same MCP server? I cody can’t directly give me the data, instead need me to install a psql in local computer, then execute it myself?
BTW, I’m using vscode.

2

Hey @atline Thank you for reporting. The current implementation of MCP server in Cody is still in experimental phase and only resources are submitted. We are working on it to make it full compatible.

Sorry for the inconvenience.

3

Thanks @PriNova for the confirm, looking forward to the update.

1 Like