Skip to content

Conversation

dale-stewart
Copy link

  • Added support for multiple databases via a JSON configuration file, allowing simultaneous access to SQLite, SQL Server, PostgreSQL, and MySQL.
  • Introduced an insights database for storing business insights, with functionality to append and list insights.
  • Updated various handlers and tools to require a dbId parameter for database operations.
  • Enhanced README documentation to reflect new features and usage instructions for multi-database configuration and insights management.
  • Version updated to 1.1.0 in package.json and package-lock.json.

I've found this tool very useful in my work, but I am only able to use one instance of the server at a time. Because I wanted to access multiple databases simultaneously, I thought I would add that capability. I'm sure this could use some refinement, but I thought I would offer this pull request to start the conversation.

- Added support for multiple databases via a JSON configuration file, allowing simultaneous access to SQLite, SQL Server, PostgreSQL, and MySQL. - Introduced an insights database for storing business insights, with functionality to append and list insights. - Updated various handlers and tools to require a `dbId` parameter for database operations. - Enhanced README documentation to reflect new features and usage instructions for multi-database configuration and insights management. - Version updated to 1.1.0 in package.json and package-lock.json.
@executeautomation
Copy link
Owner

@dale-stewart - Love the idea, can you please help me update the Documentation of the change like how you mentioned in the Readme.md

Thanks,

@fabrizio11
Copy link

@dale-stewart with this would I able to run 2 mcp servers for two different MySQL connections?

@dale-stewart
Copy link
Author

It would manage two connections from a single MCP server instance. My original motivation for doing this is that I could not get multiple instances of this MCP server working correctly with Cursor at the same time - it would get confused about which instance it was talking to. I haven't had any more time to work on this, so I've just been using the existing MCP server version one database at a time instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants