Postgres MCP in Agent Chat: ‘Copy’ Button Overlaps Expand SQL Button

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Button to expand SQL from Postgres MCP tool call is inaccessible, currently being overlapped by the “Copy” button.

Steps to Reproduce

Register Postgres MCP. Available here:

Add to Cursor IDE’s MCP list:

{
  "mcpServers": {
    "postgres": {
      "command": "uvx",
      "args": [
        "--python",
        "3.13",
        "postgres-mcp",
        "--access-mode=unrestricted"
      ],
      "env": {
        "DATABASE_URI": "postgresql://redacted"
      }
    }
  }
}

Have the agent execute the execute_sql tool call with any sufficiently long query that would overflow one line. Notice that anything that overflows off one line is truncated with an ellipsis.

First, expand the tool call execution to inspect the details. Then, attempt to expand the sql selection there, but you’ll notice the “Copy” button overlaps it, making it unreachable.

Expected Behavior

I would expect to be able to both expand the SQL to be executed, as well as copy the output, with the buttons not overlapping/interfering with each other.

Screenshots / Screen Recordings

copy-button-overlapping-expand-button.png
copy-button-overlapping-expand-button.png2554×670 54.5 KB

Operating System

MacOS

Version Information

Version: 2.6.12 (Universal)
VSCode Version: 1.105.1
Commit: 1917e900a0c4b0111dc7975777cfff60853059d0
Date: 2026-03-04T21:41:18.914Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

For AI issues: which model did you use?

Any model.

Does this stop you from using Cursor

No - Cursor works, but with this issue

3

Hey, thanks for the detailed report and the screenshot. The steps to reproduce are really clear.

This is a known UI bug where the Copy button overlaps the expand chevron on MCP tool call results, so you can’t click the expand button. The team is aware of it. There’s no ETA yet, but your report helps us prioritize it.

Let us know if you run into anything else.

6

Describe the Bug

In the chat panel, when an AI tool call is made to an MCP server, the tool call input (showing the arguments/query sent to the tool) has a copy button that overlaps or covers the expand/collapse arrow. This makes it impossible to expand the input to read the full query.

Steps to Reproduce

Have an MCP server configured and active
Trigger any MCP tool call from the AI (e.g. a BigQuery execute_sql with a multi-line SQL query)
In the chat panel, locate the collapsed tool call input block
Attempt to click the expand/collapse arrow to read the full query
The copy button intercepts the click — the input block cannot be expanded

Expected Behavior

Expected behaviour The expand/collapse arrow on MCP tool call inputs should be independently clickable and clearly separated from the copy button.

Actual behaviour The copy button sits on top of the expand/collapse arrow. The input block cannot be expanded to view the full query.

Screenshots / Screen Recordings

Screenshot 2026-03-12 103654.png

Operating System

Windows 10/11

Version Information

Environment

OS: Windows 10 (Build 26200)
Shell: PowerShell
Cursor version: 2.6.18

Does this stop you from using Cursor

No - Cursor works, but with this issue

7

this applies to any database connection MCP on cursor

8

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Copy and Expand buttons are overlapped in the chat, so you cannot really expand an mcp call.

Steps to Reproduce

Ask the agent to make some MCP call (sql as an example) with quite long body. See the icons in the chat window.

Expected Behavior

They are separated icons.

Screenshots / Screen Recordings

Screenshot 2026-03-20 at 15.43.17.png
Screenshot 2026-03-20 at 15.43.17.png756×272 23.9 KB

Operating System

MacOS

Version Information

Version: 2.6.20
VSCode Version: 1.105.1
Commit: b29eb4ee5f9f6d1cb2afbc09070198d3ea6ad760
Date: 2026-03-17T01:50:02.404Z
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

For AI issues: which model did you use?

Any

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

9

Thanks for the reports everyone! A fix will land in the next release of Cursor.

10

I see a fix did land in this area—glad it’s fixed! The fix is clicking the sql button to the left of the query to expand and view the full SQL.

Only thing I’ll mention @Colin is that it’s not obvious from a UI standpoint that clicking the sql button is how to expand things (took me several minutes to figure that out). I’d definitely recommend to the UI team to make some sort of change to make it more obvious from a UI standpoint (carrot icon, clicking the SQL text itself, etc.) so that users know where to find it, since it’s pretty essential for reviewing generated SQL.

Also, it wouldn’t be a bad idea if the generated SQL could include formatting and syntax highlighting and be in a monospace font for easier review (edit: it looks like sometimes formatting is already included, but not always (at the agent’s discretion)). That’d be outstanding for perfecting this feature.

Thanks again!