Skip to content

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

@VIEWVIEWVIEW

Description

@VIEWVIEWVIEW

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)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions