feat(connectors): add optional You.com search connector - #57
Open
mouse-value-add wants to merge 1 commit into
Open
feat(connectors): add optional You.com search connector#57mouse-value-add wants to merge 1 commit into
mouse-value-add wants to merge 1 commit into
Conversation
Adds You.com (https://api.you.com/mcp) to the built-in connector catalog as the first 'search'-category entry, using the mcp_dcr pathway: You.com hosts an MCP-spec OAuth authorization server with RFC 7591 dynamic client registration, so the app self-registers at first connect — no Orkas-side pre-registration, no bundled secrets. Once connected, agents get You.com web search / URL contents / research tools for cited web research. Exact-count assertions in open-source-boundary.test.ts updated 21→22 total, 11→12 mcp_dcr, per catalog contract. Signed-off-by: mouse-value-add <mouseparker123@gmail.com>
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.
What this adds
A You.com entry in the built-in connector catalog — the first
'search'-category connector. Orkas ships research-heavy agents (DeepResearcher, ContentWriter, SeoGeoAgent) but the catalog currently has no web-search provider, so agents doing evidence-grounded research have no search backend to connect.I used the existing
mcp_dcrpathway (same as Notion / Linear / Atlassian / Cloudflare): You.com hosts an MCP-spec OAuth authorization server with RFC 7591 dynamic client registration, so the app self-registers at first connect. No Orkas-side pre-registration and no bundled secrets — the DCR client credentials and rotating refresh grant stay in the local encrypted connector registry, like the other DCR connectors.Changes
src/main/features/connectors/catalog.ts— new entry:id: 'you',category: 'search',auth_mode: 'mcp_dcr',transport_template: { kind: 'streamable-http', url: 'https://api.you.com/mcp' }, inline SVG icon (simple "Y" glyph in You.com's brand purple rather than a traced logo mark — happy to swap if you have a preferred asset).test/main/features/connectors/open-source-boundary.test.ts— exact-count assertions updated per the catalog contract (21→22 total, 11→12mcp_dcr).Fully opt-in: nothing changes for existing users until they click Connect on the You.com card.
Why mcp_dcr works here (verified)
https://api.you.com/mcp/.well-known/oauth-protected-resource→ 200, advertises the AS and the RFC 8707resourceURI — this is the exact path-suffixed discovery_fetchWellKnowntries first.registration_endpoint(RFC 7591) andtoken_endpoint_auth_methods_supportedincludingclient_secret_post— matching_chooseTokenAuthMethod.authorization_code+refresh_tokenwith PKCE S256, matching the handshake inoauth-dcr.ts.Validation
npx vitest run test/main/features/connectors/ test/renderer/connector-icons.test.ts test/renderer/connectors-card.test.ts test/renderer/connectors-degraded-card.test.ts test/renderer/connectors-render-cache.test.ts— 18 files, 149 tests passed.npm run typecheck(tsc --noEmit) — clean.test/main/ipc/library-write.test.tshas 3 failures in this environment on a clean checkout too (native embedding moduleERR_DLOPEN_FAILED— missing platform binary, unrelated to this change).Tracking: youdotcom-oss/integration-tracking#233