Sqlanywhere MCP

Name: Sqlanywhere MCP
Author: Dwarf1er

by Dwarf1erversion 0.1.0i★ –iRuns on your computer

Registry nameio.github.Dwarf1er/sqlanywhere-mcp

Install

Overview

Description from the maker (original English)

MCP server for SAP SQL Anywhere 17: explore schemas and run read-only queries.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Databases & datasets

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: SQLANYWHERE_MCP_CONFIG

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "sqlanywhere": {
      "command": "dnx",
      "args": [
        "SqlAnywhereMcp",
        "--yes"
      ],
      "env": {
        "SQLANYWHERE_MCP_CONFIG": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add sqlanywhere --env SQLANYWHERE_MCP_CONFIG=your-value -- dnx SqlAnywhereMcp --yes

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "sqlanywhere": {
      "command": "dnx",
      "args": [
        "SqlAnywhereMcp",
        "--yes"
      ],
      "env": {
        "SQLANYWHERE_MCP_CONFIG": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "sqlanywhere": {
      "type": "stdio",
      "command": "dnx",
      "args": [
        "SqlAnywhereMcp",
        "--yes"
      ],
      "env": {
        "SQLANYWHERE_MCP_CONFIG": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

SQLANYWHERE_MCP_CONFIG env
Path of the config.json file. Defaults to sqlanywhere-mcp/config.json in the user's config directory.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account Dwarf1er, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Databases & datasetsi

More stars than 0% of the other 953 servers in this category
Published to the registry more recently than 70% of the other 953 servers in this category
Basic checks equal to or better than 100% of the other 953 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Sqlanywhere MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 21 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need .NET on your computer.

What can I use instead?

In the same category: Supabase, MongoDB MCP Server, Elasticsearch MCP Server

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Supabase

by supabase

Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.

Computer or cloud★ 2,993Apache-2.0Updated yesterday

Install

MongoDB MCP Server

by mongodb-js

MongoDB Model Context Protocol Server

Runs on your computer★ 1,157Apache-2.0Updated 2 days ago

Install

Elasticsearch MCP Server

by cr7258

MCP server for interacting with Elasticsearch

Runs on your computer★ 315Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

sqlanywhere-mcp

MCP server for SAP SQL Anywhere 17

MCP (*Model Context Protocol*) server for SQL Anywhere 17. Lets an MCP client such as Claude Code or Claude Desktop query a SQL Anywhere database directly to explore the schema, stored procedures, triggers, and views. It runs on Windows, Linux, and macOS.

Disclaimer: sqlanywhere-mcp is an independent, community open-source project. It is not affiliated with, endorsed by, or sponsored by SAP SE. SAP and SQL Anywhere are trademarks or registered trademarks of SAP SE. sqlanywhere-mcp does not include or redistribute any SAP software.

sqlanywhere-mcp
Table of contents
Prerequisites
ODBC driver setup
Installation
From NuGet
From a release
From source
Configuration
File location
Fields
Live reload
Database password
Suggested helper: keyturn
Claude Code integration
As a plugin
By hand
Claude Desktop integration
Multiple databases
Available tools
Databases
Query execution
Ownership
Schema introspection
Object lists
Source retrieval
Procedure calls
How it works
License

Prerequisites

The SQL Anywhere 17 ODBC driver, installed on the machine that runs sqlanywhere-mcp. It comes with the SQL Anywhere 17 client or server install, for the platform you run on.
On Linux and macOS, an ODBC driver manager: unixODBC (for example apt install unixodbc, dnf install unixODBC, brew install unixodbc). On Windows the driver manager is built in.
The .NET 10 SDK, to build from source.
An MCP client, such as Claude Code or Claude Desktop.

sqlanywhere-mcp itself is a .NET application with no platform-specific code. What differs per platform is how the driver is registered, which is covered in ODBC driver setup.

ODBC driver setup

sqlanywhere-mcp connects with the ODBC driver named SQL Anywhere 17, which is the name the Windows installer registers. Use the driver setting (see Fields) when your driver is registered under another name.

Windows: nothing to do after installing SQL Anywhere 17.
Linux and macOS: unixODBC needs to know the driver. Either register it in odbcinst.ini under the name SQL Anywhere 17, or set driver in config.json to the path of the driver library, for example /opt/sqlanywhere17/lib64/libdbodbc17.so (the path depends on where SQL Anywhere is installed). The driver also needs its own libraries to be loadable; SQL Anywhere provides an sa_config.sh script for that, which you can source before starting your MCP client. See SAP's documentation for the details of your platform.

When the connection fails, the tool error names the driver it used, so a wrong driver name or a missing driver is visible in the client.

Installation

There are three ways to get sqlanywhere-mcp. All of them give the same server, which needs the prerequisites above (the ODBC driver, plus unixODBC on Linux and macOS).

From NuGet

The SqlAnywhereMcp package is a .NET tool with a self-contained build for each platform (win-x64, linux-x64, linux-arm64, osx-x64, osx-arm64), so no .NET runtime is needed to run it. It needs the .NET 10 SDK to install, which provides dnx and dotnet tool.

Run it without installing, which is what MCP clients usually do:

dnx SqlAnywhereMcp --yes

Or install it as a global tool, which puts sqlanywhere-mcp on your PATH:

dotnet tool install --global SqlAnywhereMcp

To register it with Claude Code without installing anything first:

claude mcp add --transport stdio --scope user sqlanywhere -- dnx SqlAnywhereMcp --yes

From a release

Each GitHub release has an archive per platform with the self-contained executable, plus a SHA256SUMS file. Unpack the one for your platform somewhere on your PATH and verify it with sha256sum -c SHA256SUMS. The executables are not code-signed, so macOS Gatekeeper and Windows SmartScreen may warn on first run.

From source

Run the install script for your platform from a regular user account (no administrator rights needed). Each one publishes a self-contained executable, so the .NET runtime is not needed to run it.

Windows (PowerShell):

.\install.ps1

It publishes sqlanywhere-mcp.exe to %LOCALAPPDATA%\sqlanywhere-mcp\, adds that directory to the user PATH, and prints the command to register the server with Claude Code.

Option	Description
`-Configuration Release`	Build configuration (default: `Release`)
`-Configuration Debug`	Build in Debug mode
`-Help`	Show help

Linux and macOS (bash):

./install.sh

It detects the platform (linux-x64, linux-arm64, osx-x64, or osx-arm64), publishes sqlanywhere-mcp to ~/.local/bin/, and prints the command to register the server with Claude Code. -c Debug builds in Debug mode.

The driver must match the architecture of the executable. If your SQL Anywhere 17 driver is x64 only, use an x64 build (on Apple silicon, the x64 build runs under Rosetta).

Any platform, by hand:

dotnet publish src/SqlAnywhereMcp -c Release -r <rid> --self-contained -o <output-dir>

where is a .NET runtime identifier such as win-x64, linux-x64, or osx-x64.

Configuration

File location

Platform	Path
Windows	`%APPDATA%\sqlanywhere-mcp\config.json`
Linux / macOS	`$XDG_CONFIG_HOME/sqlanywhere-mcp/config.json`, or `~/.config/sqlanywhere-mcp/config.json` when `XDG_CONFIG_HOME` is not set

If the file is missing on first launch, an example is created automatically. Edit it and restart sqlanywhere-mcp once; after that, changes are picked up without a restart (see Live reload).

Example configuration:

"defaults": { "username": "dba", "passwordCommand": "keyturn get dev-db --refresh" }, "allowedProcedures": [], "defaultDatabase": "demo", "databases": { "demo": { "host": "localhost", "database": "demodb" }, "staging": { "host": "db.example.com", "port": 2700, "database": "stagingdb", "passwordCommand": "keyturn get staging-db --refresh", "allowedProcedures": ["dbo.sa_conn_info"] } } }

Unknown fields are rejected, so a misspelled field (for example allowedProcedure) is reported instead of being silently ignored.

Fields

Top level:

Field	Required	Description
`databases`	Yes	The databases tools can reach, keyed by name. The name is what tools take as their `database` argument, and must be unique ignoring case. An empty object is valid: tools then report that no database is configured. See the fields below
`defaults`	No	Values every database uses unless it sets its own. See the fields below
`defaultDatabase`	No	Name of the database a tool uses when called without `database`. Not needed with a single database
`allowedProcedures`	No	Stored procedures that `call_procedure` may call on every database, each written as `owner.procedure` (default: none). See Procedure calls

defaults:

Field	Default	Description
`username`	-	Login username. Required, here or on each database
`passwordCommand`	-	Credential helper: a command that prints the database password. Required, here or on each database. See Database password
`appInfo`	-	Value of the `AppInfo` ODBC parameter, used by SQL Anywhere to identify the connecting application (for example `my-app`)
`driver`	`SQL Anywhere 17`	ODBC driver name as registered with the driver manager, or the path of the driver library. See ODBC driver setup
`port`	`2638`	TCP port of the database (SQL Anywhere's standard port)

Each database:

Field	Required	Description
`host`	Yes	Hostname of the SQL Anywhere server
`database`	Yes	Database name (`DBN` ODBC parameter)
`port`	No	Overrides `defaults.port`
`username`	Yes, unless in `defaults`	Overrides `defaults.username`
`passwordCommand`	Yes, unless in `defaults`	Overrides `defaults.passwordCommand`, for a database with other credentials
`appInfo`	No	Overrides `defaults.appInfo`
`driver`	No	Overrides `defaults.driver`
`allowedProcedures`	No	Procedures `call_procedure` may call on this database, in addition to the top-level ones

Live reload

sqlanywhere-mcp checks config.json before every tool call. When the file changed and is valid, the next call uses it: added databases become available, removed ones disappear, and open connections are closed so they reopen with the new settings. No restart of sqlanywhere-mcp or Claude Code is needed.

When the changed file is invalid (malformed JSON, an unknown field, a duplicate name, a bad procedure name, ...) or was deleted, sqlanywhere-mcp keeps using the last valid version. list_databases reports the error in reloadError, and the error is also written to sqlanywhere-mcp's standard error, which MCP clients show in their logs. Fixing the file clears it.

The first load at startup is still strict: sqlanywhere-mcp exits with an error when the file is invalid then.

Database password

sqlanywhere-mcp never stores the database password. It follows the *credential-helper pattern*: passwordCommand is a command that prints the password on its standard output, and sqlanywhere-mcp runs it each time it opens a connection, so a password that rotates is picked up on the next reconnect.

The contract for a helper:

It prints only the password on stdout. A trailing newline is ignored.
It exits 0 on success. Any other exit code fails the connection, and the tool returns an error naming the command and its exit code.
Diagnostics go to stderr, which sqlanywhere-mcp passes through to its own, where MCP clients show it in their logs.
It runs without a shell and without input (stdin is closed). Quote arguments that cont

Only the beginning is shown; read the rest in the repo

Sqlanywhere MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Databases & datasetsi

Common questions

Alternatives

Supabase

MongoDB MCP Server

Elasticsearch MCP Server

README from the maker

sqlanywhere-mcp

MCP server for SAP SQL Anywhere 17

Table of contents

Prerequisites

ODBC driver setup

Installation

From NuGet

From a release

From source

Configuration

File location

Fields

Live reload

Database password