Credentials. The MCP server opens its own database connections, so each profile needs its access level and password source checked before an agent is connected.
Who it is forAn engineer who wants an AI agent to answer questions about a database, and who must limit what the agent can touch.
The problemGiving an agent direct database credentials with no limits is risky, and copying data by hand is slow.
The outcomeThe agent reads from allowed profiles through Masume, and writes are limited by the access level you set.
What you need first
- A terminal on macOS, Linux, or Windows
- A database you can reach, or a local SQLite file
- One install method: Homebrew, npm, Go 1.27 or later, or a release package
Steps
- Enable the profile for MCP in the settings screen or config, as described in docs/mcp.md
- Run
masume --mcp --checkto check the enabled MCP profiles - Run
masume --mcp --profile <profile>to serve one allowed profile (inferred, check the README) - Point your agent at the stdio server and confirm it lists the database tools
Prompt for your agent
Using the masume MCP server for profile <profile>, list the tables and report the row count of <table>. Expected output: a table list and one integer. Verify the count by running a matching count query in masume yourself.
Caveat. Read-only checks run in the client and on engines that support server-side enforcement, so confirm the level in docs/mcp.md for your engine.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for masumedb/masume and "Let an external agent query allowed databases over MCP"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer