MariaDB / MariaDB/mcp

MCP presents itself as read-only

Open
#33 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
204
Forks
85
PR merge metrics
No merged PRs in 30d

Description

Although I set read-only mode to false and I can do DMLs and DDLs via the MCP, somewhere the MCP advertises itself as read-only.
I have to counteract this behavior via agent rules to let it know that it can perform DMLs and DDLs despite the MCP's warnings.
It would be best for the MCP to advertise its capabilities depending on the read-only mode.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating where the MCP server advertises its capabilities and how the read-only configuration is passed into that code. Reproduce the behavior with read-only mode enabled and disabled, then verify that the advertised capabilities match each setting and that DML and DDL operations remain represented correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.