MariaDB / MariaDB/mcp

Bad request

Open
#44 4 comments 1 reaction 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 follow the tutorial to locally deploy in a container mariadb and MVP server and it works , now I integrate the same code in a xampp stack dockerized but in vs code , in Claude or in n8n , I get bad request on /sse
I saw the log of mcp server and it start correctly with sse and the connection to the database was done
The only slightly modification I have gone is on port exposed because 9001 is already in use by portsiner agent but again the request of connection arrive to Mcp in 9001 internally bec as use I see the error
Firewall is disabled on vm Rocky Linux where is deployed the docker stack
I don't what else to check

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

Compare the tutorial's local container deployment with the dockerized XAMPP stack, starting with the MCP server logs and the /sse request path. Check the exposed-versus-internal port mapping around 9001 and the MariaDB connection; done means identifying why /sse returns a bad request and confirming a client can connect successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, mariadb, python
Domain
backend, databases, devops, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.