Skip to content

Conversation

@joshrotenberg
Copy link
Collaborator

Summary

  • MCP server now inspects config profiles to auto-detect which toolsets to expose, so a cloud-only user no longer sees dozens of irrelevant enterprise_* tools in their LLM context
  • Priority chain: --tools flag (explicit override) > config-based auto-detection > all compiled-in features (fallback)
  • Adds toolsets_from_config() as a pure, testable function and detect_toolsets_from_config() as the filesystem wrapper

Test plan

  • 6 unit tests covering: empty config, cloud-only, enterprise-only, cloud+enterprise, database-only, all three types
  • Full cargo test -p redisctl-mcp passes (71 tests)
  • cargo clippy -p redisctl-mcp --all-targets clean
  • Manual: verify cloud-only config logs toolsets: [cloud, app]
  • Manual: verify --tools enterprise,app still overrides auto-detect

Picks up fix for module platforms deserialization (HashMap instead of
Vec) from redis-developer/redis-enterprise-rs#33.
Instead of registering all compiled-in tools by default, inspect the
user's config profiles to only expose relevant toolsets. A cloud-only
user no longer sees dozens of enterprise_* tools in their LLM context.

Priority: --tools flag > config-based auto-detection > all compiled-in.
@joshrotenberg joshrotenberg merged commit 40f96cf into main Feb 10, 2026
19 checks passed
@joshrotenberg joshrotenberg deleted the feat/mcp-auto-detect-toolsets branch February 10, 2026 15:20
@joshrotenberg joshrotenberg mentioned this pull request Feb 10, 2026
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.

1 participant