MariaDB / MariaDB/mcp

Simplify MCP setup by publishing to PyPI and adding a console entry point

Open
#53 0 comments 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

Hi,

I really enjoy this MCP, however I found the setup to be more complicated than it should be. Most MCPs can be set up in agent tools (claude, codex etc) via a simple codex mcp add mariadb-mcp -- uxv mariadb-mcp. However, it is not published on the PyPi index and has no console entry point defined in pyproject.toml, so it's currently not possible to setup this project like this. I find it really cumbersome to clone the project via git for local usage and manually start the stdio server, especially for multiple projects.

I think this should be changed, but only the maintainers of this project are able to complete all tasks to do this, as it requires to set up a PyPi account, org and project.

Task list:


I already played around on how to do it it in the test environment test.pypi.org, my fork is here https://github.com/VIEWVIEWVIEW/mariadb-mcp and the PyPi package is here: https://test.pypi.org/project/mariadb-mcp/. I wrote it together with an LLM and reviewed+tested the code, but I'm not aware of guidelines of MariaDB about LLM generated code. (Maybe you don't like it or have fear of licensing stuff)

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 with pyproject.toml and .github/workflows/publish-pypi.yml, then review the README changes and the trusted publisher guidance linked in the issue. Confirm the package metadata and console entry point, configure the maintainer-owned PyPI trusted publisher, and run the publishing job so mariadb-mcp is available on PyPI.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, python
Domain
ci-cd, release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.