-
Notifications
You must be signed in to change notification settings - Fork 211
Labels
bugSomething isn't workingSomething isn't workingtriageIssues / Features awaiting triageIssues / Features awaiting triage
Description
π Bug Summary
During test case execution, the tools created for testing are being added to the main database instead of a mock or in-memory database
π§© Affected Component
Select the area of the project impacted:
-
mcpgateway
- API -
mcpgateway
- UI (admin panel) -
mcpgateway.wrapper
- stdio wrapper - Federation or Transports
- CLI, Makefiles, or shell scripts
- Container setup (Docker/Podman/Compose)
- Other (explain below)
π Steps to Reproduce
- Run make test.
- Verify the database configured as your main/production DB in the .env file.
- Youβll notice that tools created during the tests are being inserted into this main database and are visible in the UI.
π€ Expected Behavior
Test cases should use a mock or in-memory database for creating tools and performing all related operations, to avoid polluting the main/production database.
π Logs / Error Output

π§ Environment Info
You can retrieve most of this from the /version
endpoint.
Key | Value |
---|---|
Version or commit | e.g. v0.9.0 or main@a1b2c3d |
Runtime | e.g. Python 3.11, Gunicorn |
Platform / OS | e.g. Ubuntu 22.04, macOS |
Container | e.g. Docker, Podman, none |
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingtriageIssues / Features awaiting triageIssues / Features awaiting triage