Skip to content

feat(mcp): allow explicit reranker provider selection - #1698

Open
abouchard11 wants to merge 1 commit into
getzep:mainfrom
abouchard11:feat/mcp-explicit-reranker-config
Open

feat(mcp): allow explicit reranker provider selection#1698
abouchard11 wants to merge 1 commit into
getzep:mainfrom
abouchard11:feat/mcp-explicit-reranker-config

Conversation

@abouchard11

Copy link
Copy Markdown

Summary

Add an explicit MCP reranker.provider configuration while preserving the automatic selection behavior merged in #1637.

  • auto keeps the current LLM → embedder → local BGE fallback chain.
  • openai, azure_openai, and gemini reuse credentials already configured under the matching LLM/embedder provider entry.
  • bge explicitly selects the existing local reranker.
  • Document both YAML and direct environment overrides.

This is the explicit configuration follow-up discussed around #1637 and the earlier provider-matched proposal #1669.

Closes #1697.

Testing

  • Test-first coverage for configuration parsing, explicit Gemini override behavior, and Graphiti service wiring.
  • 68 passed across MCP factory, configuration, core-parity, transport, and stdio unit tests.
  • ruff check and ruff format --check pass for all changed Python files.
  • Focused Pyright passes with 0 errors, 0 warnings.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

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.

RFC: allow explicit MCP reranker provider configuration

1 participant