Repository navigation
docs: add Sofya MCP server example - #702
Merged
ericdallo merged 1 commit intoNov 12, 2026
Merged
Conversation
Adds a Sofya tab to the mcpServers examples in docs/config/tools.md, between Serply and You.com. The server accepts an Authorization bearer header with ${env:SOFYA_API_KEY}; without headers ECA's OAuth flow signs in (the server supports dynamic client registration).
ericdallo
approved these changes
Nov 12, 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
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.
Adds a Sofya tab to the MCP examples in
docs/config/tools.md, between Serply and You.com, in the same format as the other tabs. Docs only.Sofya's hosted MCP server (
https://mcp.sofya.co/mcp, streamable HTTP) has web search, page fetch as markdown, extraction from a page and multi-source research. The example uses anAuthorization: Bearer ${env:SOFYA_API_KEY}header so the key stays out of the config file. Withoutheaders, ECA's OAuth flow works too: the server answers the ping probe with a 401 +resource_metadata, and supports dynamic client registration.Validation:
docs-image buildpasses and the tab rendersinitialize+tools/listwith a bearer key return the 6 tools (search, fetch, extract, research, get_balance, buy_credits)Calls are paid per credit, so the note says to keep approval prompts on. No CHANGELOG entry, like the other example PRs.
Disclosure: I work on Sofya.