Repository navigation
refactor!: remove built-in exa and context7 MCP servers - #27
Merged
Merged
Conversation
BREAKING CHANGE: the [mcp] enable_exa and enable_context7 flags are removed, and EXA_API_KEY no longer auto-configures a server. Add these servers by hand under [mcp.servers]; a schema v2 migration strips the removed flags from existing configs.
This was referenced Sep 29, 2026
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.
Removes the built-in Exa and context7 MCP integrations. lecode ships no
preconfigured servers; users add hosted servers under
[mcp.servers]by hand(docs/mcp.md shows the Exa and context7 snippets). Generic MCP support
(stdio, streamable-HTTP, SSE, OAuth 2.1, permissions) is unchanged, and
servers named
exa/context7/grep-appstay read-equivalent when addedmanually.
Breaking change:
[mcp] enable_exa/enable_context7are gone and anambient
EXA_API_KEYno longer auto-configures anything. A schema v1→v2migration strips the removed flags from existing config files on first load.
McpConfigdrops the two flags;auto_servers()/all_server_configs()and the
EXA_URL/CONTEXT7_URLconstants are deleted; the managerconnects
[mcp.servers]directly./mcphelp no longer mention theauto-configured servers.
Validation:
ruff check,ruff format --check, and the full pytestsuite (1951 tests) pass locally with
--extra telemetry.Note: whichever of this and #22 lands second needs a trivial rebase fix —
#22's new
tests/test_headless.pysets the two removed flags.