Jam SQL Studio

com.jamsqlPublished by jamsql.comv1.0.0Updated Oct 24, 2026

Lets AI agents query SQL Server, PostgreSQL, MySQL, Oracle and SQLite via the Jam SQL Studio app.

VerifiedSTDIODesktop onlyDatabases

Server details

Identifier: com.jamsql/jam-sql-studio
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Oct 10, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to jamsql.com. It runs from a package rather than a hosted endpoint, so there is no endpoint to match against that domain.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.jamsql%2Fjam-sql-studio.svg)](https://sourceweft.com/mcp/com.jamsql%2Fjam-sql-studio?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Connects an AI assistant to the local Jam SQL Studio app so it can query SQL Server, PostgreSQL, MySQL, Oracle and SQLite databases.

What you can do: Query databases: run SQL against SQL Server, PostgreSQL, MySQL, Oracle and SQLite through the Jam SQL Studio app running on the same machine.
When to use it: Useful when you already work in Jam SQL Studio and want an assistant to query one of the supported databases from the same desktop setup.
Requirements: A local process installed from the npm package @jamsql/mcp, plus the Jam SQL Studio desktop app running on the same machine. Authentication uses the secret JAMSQL_MCP_TOKEN, a bearer token from Settings → AI Integrations, or the token saved by the jam-sql pair command. JAMSQL_MCP_URL can point at the app's MCP endpoint; if unset, it is discovered automatically through a local discovery file.

Before you install

The server needs a bearer token (JAMSQL_MCP_TOKEN) that grants access to your databases; keep it private. Queries run against real databases, so statements that change or delete data may take effect. Desktop only.

Installation

In SourceWeft

Open Jam SQL Studio in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.0.0LatestOct 10, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.