chore(remote): open upstream contribution proposal to modelcontextprotocol/servers

[clouatre]

Summary

After #941 lands, open a contribution proposal issue in modelcontextprotocol/servers for a GitHub/GitLab raw file content server, referencing the v15 benchmark data and the aptu-coder-remote implementation as prior art.

Context

The modelcontextprotocol/servers reference repository (https://github.com/modelcontextprotocol/servers) contains seven active servers: everything, fetch, filesystem, git, memory, sequentialthinking, time. None fetches raw file content from a remote GitHub or GitLab repository without cloning.

The previously active GitHub and GitLab servers were archived to modelcontextprotocol/servers-archived and their development moved upstream:

• GitHub: migrated to github/github-mcp-server (https://github.com/github/github-mcp-server), which exposes get_file_contents (GitHub only, requires OAuth repo scope)
• GitLab: archived, no active replacement

aptu-coder-remote covers both platforms with token-based auth (GITLAB_TOKEN, GITHUB_TOKEN), line-range slicing, and a tree-listing primitive. The v15 benchmark (docs/benchmarks/v15/) measured it against a curl baseline across 60 scored runs on five task types.

What to do

1. Confirm refactor(remote): remove crates/aptu-coder-remote and remote_* tools #941 is merged and aptu-coder-remote is removed from this workspace
2. Open an issue in modelcontextprotocol/servers proposing a src/github-gitlab-content server with:
   • get_file_contents(url, path, ref, line_range) -- raw file fetch from GitHub or GitLab without cloning
   • list_tree(url, path, ref, depth) -- directory tree listing
   • Token-based auth (GITHUB_TOKEN, GITLAB_TOKEN)
   • The existing Rust implementation in aptu-coder-remote as reference (link to the final tagged commit before removal)
   • The v15 benchmark results as motivation (token efficiency vs curl baseline, specifically: 3x fewer tokens for file fetch tasks, 16.8x fewer tool calls for deep tree traversal)
3. Note the gap not covered by github/github-mcp-server: GitLab support and the tree-listing primitive

Constraints

• This is a proposal issue, not a code contribution. Language choice (TypeScript vs Python vs Rust) is a maintainer decision for the modelcontextprotocol/servers repo.
• Do not submit a PR to modelcontextprotocol/servers without prior issue discussion; the repo has a CONTRIBUTING.md that requires an issue first.
• The linked git ref for the Rust implementation must be a tagged release of aptu-coder-remote, not a branch.

Acceptance criteria

• refactor(remote): remove crates/aptu-coder-remote and remote_* tools #941 merged
• Issue opened in modelcontextprotocol/servers with the content above
• Link to the issue posted here as a comment