feat: in-app links back to the project (discussion #948) - #1008
Merged
Conversation
Users arrive via Homebrew / plugins / AI recommendations and often never see the GitHub repo, so the running app gave no way back to the homepage, docs, or issue tracker. Add project links across every surface a user might look, from one source of truth per language (internal/branding, ProjectLinks.swift, config/links.ts). - Tray menu (highest-impact surface): "Documentation", "Report an Issue…", and "About MCPProxy" (standard About panel with homepage/GitHub/docs credit links) before Quit. - Web UI: persistent footer on every page — "MCPProxy vX.Y · Homepage · GitHub · Docs · Discussions". Previously the only outbound links were buried in settings. - CLI: `mcpproxy --version` and `--help` print Homepage / GitHub / Docs. - MCP serverInfo: the protocol-level instructions carry the homepage/repo/docs, so an agent (and anyone reading its logs) can find the project. Verified locally: Web UI footer rendered + all four hrefs correct via the Chrome extension; tray menu items present, correctly placed before Quit, and the Documentation action opens docs.mcpproxy.app via mcpproxy-ui-test; all four URLs return HTTP 200. Part 2 of the discussion (product-name fragmentation) is not addressed here. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01H7J8Yv5zr4tMQZaY3ot3Za
Deploying mcpproxy-docs with
|
| Latest commit: |
397dffb
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://d332fabd.mcpproxy-docs.pages.dev |
| Branch Preview URL: | https://feat-948-in-app-links.mcpproxy-docs.pages.dev |
|
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
📦 Build ArtifactsWorkflow Run: View Run Available Artifacts
How to DownloadOption 1: GitHub Web UI (easiest)
Option 2: GitHub CLI gh run download 32248285474 --repo smart-mcp-proxy/mcpproxy-go
|
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
2 participants
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.
Addresses part 1 of discussion #948 (thanks @twardoch): the running app gave a user no way back to the homepage, docs, or issue tracker. Users arrive via Homebrew / plugins / AI recommendations and never see the repo, so installs don't convert to stars/issues. This adds project links across every surface a user might look.
One source of truth per language:
internal/branding(Go),ProjectLinks.swift(tray),frontend/src/config/links.ts(Web UI).Surfaces
Documentation,Report an Issue…, andAbout MCPProxy(standard About panel with clickable Homepage / GitHub / Documentation credit links) added before Quit.MCPProxy vX.Y · Homepage · GitHub · Docs · Discussions.mcpproxy --versionandmcpproxy --helpprint Homepage / GitHub / Docs in the header.instructionsnow carry the homepage/repo/docs, so an agent (and anyone reading its logs) can find the project — relevant given the tool is being AI-recommended.Verified locally
mcpproxy.app, the repo,docs.mcpproxy.app, repo/discussions).mcpproxy-ui-test): the three items appear correctly positioned before Quit, and clickingDocumentationopensdocs.mcpproxy.app(built the tray, swapped it in via a temp bundle, verified, then restored the production tray).mcpproxy --version/--helpoutput checked; Go + Swift both build; new tests for the version output and serverInfo instructions.Not in this PR
Part 2 of the discussion (product-name fragmentation — org
smart-mcp-proxyvs repomcpproxy-govs binarymcpproxyvs sitemcpproxy.app) is a separate, non-code discussion and is left for a follow-up.🤖 Generated with Claude Code