masume MCP
A terminal database client with AI chat and a masume --mcp mode: agents work with databases inside defined access limits.
- 108 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- The `read-write` and `full` levels permit writes, and `full` also `DROP` and `TRUNCATE` in the connected database.
- Query results, including personal data from tables, reach the model context.
- Profile passwords come from the environment or keyring and are available to the server process.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/masumeDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The `read-write` and `full` levels permit writes, and `full` also `DROP` and `TRUNCATE` in the connected database.
- Query results, including personal data from tables, reach the model context.
- Profile passwords come from the environment or keyring and are available to the server process.
This is third-party code. Review the repository files before installing.
What it does
`masume` is a keyboard-first terminal database client: PostgreSQL, MySQL, MariaDB, SQL Server, ClickHouse, SQLite, Cassandra, ScyllaDB, Redis, MongoDB and hosted Neon, Supabase, PlanetScale, Turso. It has AI chat and query notebooks. The `masume --mcp` command starts an MCP server over stdio: an external agent gets `list_profiles`, `list_tables`, `describe_table`, `explain_query`, `plan_write`, `run_query` and notebook reading. Only profiles from `[mcp] profiles` in the global config are served, and the `access` level defaults to `read-only`. The `read-write` and `full` levels permit writes, and `full` also `DELETE`, `DROP` and `TRUNCATE`.
Who it is for. Developers and analysts who work with databases in a terminal and connect an agent to them with limited rights.
Good fit when
- An agent builds a query from the database schema and explains the result with no write rights.
- Before a bulk `UPDATE` the agent shows row counts and triggers through `plan_write`.
- The project has a `.masume.toml` with profiles and only one is open to MCP: `--profile=shop`.
- You need to find databases in running containers: `masume --detect`.
Not a fit when
- You need a graphical environment with diagrams and visual editors.
- A profile points to a production database and the `full` level has not been thought through.
- The password is typed only in the terminal; the MCP server cannot ask for it.
Example request
List the tables of the shop database, describe the orders table and build a query with the number of orders per day for the last week.MCP
- Transport
- stdio
- Authentication
- not required
Limitations
The MCP server reads only profiles listed in `[mcp] profiles` of the global config: with an empty list nothing is available, and a project `.masume.toml` cannot add a profile to the list. The password comes from an environment variable, a keyring, a command or a secret store, so a profile with a terminal password prompt is unavailable to MCP. `masume` does not update itself. `go install` needs Go 1.27 or newer, and the README marks the Alpine packages as unsigned.
How to disable. Remove the server entry from the client configuration (`claude mcp remove masume`) or leave `[mcp] profiles` empty. Delete keyring entries and profiles separately.
FAQ
What does the agent see by default?
Only profiles from `[mcp] profiles` and only reads: `access` defaults to `read-only`. An empty profile list opens nothing.
How do I limit the server to one database?
Run `masume --mcp --profile=shop`. The profile must be on the allowed list, and the tools lose their `profile` argument.
How do I check the connection?
Run `masume --mcp --check`: stderr prints `ok` with the table count or `FAILED` with the error for each profile.
Does MCP work when AI chat is off?
Yes. MCP does not depend on `[ai] enabled` and does not use the AI chat credentials.
How do I connect it to Claude Code?
With `claude mcp add --scope user masume -- masume --mcp`. The documentation has configuration examples for other clients.
Discussion
No questions or reviews yet.
Related
MCP serversOne MCP server for SQLite, SQL Server, PostgreSQL and MySQL: read and change data, edit schemas and export to CSV and JSON
A single-binary MCP server for MySQL, MariaDB, PostgreSQL and SQLite: read-only by default, with optional PII redaction
MCP server that gives an agent access to MySQL: schema inspection and queries, read-only by default, writes behind flags
A Go MCP server that lets an agent ask a PostgreSQL database questions in plain language and returns the query result
vi-sql is a terminal SQL client with a built-in MCP server: the agent sees the schema and drafts queries straight in your editor
A Python MCP server for MySQL: listing tables, reading data, running SQL and inspecting schema through a controlled interface
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| masume (this card) | no | not required | 108 | |
| DBHub | no | not required | 3,839 | a universal MCP for databases; masume is first a terminal client, and its MCP is bound by profiles and access levels |
| MCP Toolbox for Databases | yes | not required | 16,857 | a Google server with configurable tools; here ready-made tools and a terminal client |
README in short
The server speaks JSON-RPC 2.0, one message per line. The `confirm_writes` setting sets confirmation for deletes, writes or all destructive operations.