feat: add multi-host support for connecting to multiple SQL Servers - #35
Open
Abdulmajeed-Alrajhi wants to merge 2 commits into
Open
feat: add multi-host support for connecting to multiple SQL Servers#35Abdulmajeed-Alrajhi wants to merge 2 commits into
Abdulmajeed-Alrajhi wants to merge 2 commits into
Conversation
added 2 commits
March 26, 2026 15:29
Allow a single MCP server instance to connect to multiple SQL Server hosts. Connections are configured via indexed env vars (MSSQL_HOST_<N>_*) or a JSON config file (MSSQL_CONNECTIONS_FILE). In multi-host mode, execute_sql gains a required 'connection' parameter and a new list_connections tool is exposed. Fully backward compatible - existing single-host setups (MSSQL_SERVER/USER/etc.) continue to work unchanged.
Resource URIs built in multi-host list_resources() embedded the raw connection name as the URI authority (host) and the raw table name as the first path segment, e.g. `mssql://payment gateway - QA/Hash/data`. Pydantic's AnyUrl validator (used by mcp.types.Resource.uri) rejects spaces and other characters that are illegal in the URI authority, causing every resource for spaced connection names to fail validation with `invalid domain character` and surface as `Failed to list resources: 1 validation error for Resource`. As a result, all tables on those connections silently disappeared from the resource list. Percent-encode connection and table names with urllib.parse.quote when building the URI, and decode them with unquote in read_resource so routing still resolves to the original names. Single-host mode also encodes the table name for consistency.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Allow a single MCP server instance to connect to multiple SQL Server hosts. Connections are configured via indexed env vars (MSSQL_HOST__*) or a JSON config file (MSSQL_CONNECTIONS_FILE).
In multi-host mode, execute_sql gains a required 'connection' parameter and a new list_connections tool is exposed. Fully backward compatible - existing single-host setups (MSSQL_SERVER/USER/etc.) continue to work unchanged.