8000 Add Multi-Tenancy Support by chensxb97 · Pull Request #80 · ClickHouse/mcp-clickhouse · GitHub
[go: up one dir, main page]

Skip to content

Add Multi-Tenancy Suppor 10BC8 t - #80

Closed
chensxb97 wants to merge 17 commits into
ClickHouse:mainfrom
chensxb97:main
Closed

chensxb97 wants to merge 17 commits into
ClickHouse:mainfrom
chensxb97:main

Conversation

@chensxb97
Copy link
Copy Markdown

This PR is similar to #48. The intention is provide multi-tenancy in a single MCP server but in a more flexible manner. If no custom prefix is defined, we assign a "default" tenant, otherwise we create tenant IDs based on the prefix used. To prevent any confusion, "default" is not allowed as a prefix.

For my team's usecases, we are planning to have a single MCP server to intelligently communicate with more than 5 clusters so this implementation provides that flexibility for us.

README and unit tests have been updated accordingly. Am welcome to any feedback.

@CLAassistant
CLAassistant commented Aug 19, 2025 •
Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@joe-clickhouse
Copy link
Copy Markdown
Collaborator

Thanks for the work here @chensxb97. Very sorry for the delay, but I am closing this as obsolete at this point. Runtime ClickHouse routing is now supported through request-scoped middleware overrides, added in #115 and made even stronger in #221. This branch also predates the current FastMCP 4 architecture and would require a rewrite. If first-class cluster aliases are still needed beyond middleware routing, please open a new issue so we can design the configuration and authorization model against current main. Thanks!

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

0