If you watched the launch video from the SQLcl team, you were probably just as excited as I was to give it a whirl. So here’s a quick post showing what I did to get it to run and do a basic test.

(Note: A few big GIF’s in this post, so it might take a bit to load)

1) First make sure your VS Code is up to date, because it needs the latest/later versions to run Agent mode in Copilot.

sqlcl_mcp_1

 

2) Now make sure you have the latest version of the SQL Developer extension (25.2 or later)

sqlcl_mcp_2

 

3) List the MCP servers to make sure you see SQLcl, and ensure that it is started and running.

sqlcl_mcp_3

4) Set Copilot Chat to Agent mode and pick the model you want to use.

sqlcl_mcp_4

And that should be it! I checked what existing connections I had in SQLcl

Screenshot 2025-07-14 113210

and then used one of these to interact with the database via chat!

sqlcl_mcp_5

When I was done, I closed the connection…

sqlcl_mcp_6

… and sat there for a while with my mind blown 🙂

Footnote: Let’s be very clear what an MCP tool is from the perspective of you as an IT professional. If someone walked up to your desk at work and said: “Hey, you don’t know me, but I need to use the database for a bit. Can you give me some connection details and let me do whatever I want?”, you would naturally spit out your coffee and laugh at them. But that’s exactly what an MCP tool could be equivalent to. You’re handing a database connection over to a stranger and saying “Go for it!“.  Hopefully you have read my recent post on vibe coding where I discuss the recent spate of vibe coded apps being riddled with security holes. Any MCP tool poses the same risk if you’re simply handing over the keys to your database schemas. Be sure to use some standard security principles when it comes to MCP tools:

  • Don’t let the tool run any SQL statement before you review it,
  • Don’t let the tool connect to an account with any kind of privilege that could damage your data/database,
  • Think long and hard before ever letting the tool connect to a production database.

You do not want to be having an awkward conversation with your company CEO when you casually typed into the chat “Yeah, let’s drop this conversation”, and your MCP tool misinterpreted that into wiping out your company’s financials!

 

2 responses to “First dabblings with SQLcl MCP server”

  1. Christopher Ellison Avatar
    Christopher Ellison

    Hey Connor, I have the same install, I thought this might be a breakthrough as the standalone SQLcl is “presenting some issues”.

    I installed VS Code 1.102, added the SQL Developer extension version 25.2.

    When I then go to Command palette and MCP: List Servers I don’t see the SQLcl option you seem to have. Are those the complete steps?

    I don’t have Copilot I have Gemini but steps 1-3 appear to be precursors to actually using the MCP server.

Got some thoughts? Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Trending