Skip to content

Consider publishing BoJ Server to the MCP Server Registry #188

@hyperpolymath

Description

@hyperpolymath

Opportunity

The canonical discovery path for MCP servers is now the MCP Server Registry. Upstream modelcontextprotocol/servers retired its README Community Servers list in favour of the registry (see their CONTRIBUTING.md).

BoJ Server is not currently listed. Publishing would make it discoverable at https://registry.modelcontextprotocol.io/ alongside other MCP servers.

What this would take

Per the registry quickstart:

  1. Write a server entry per the registry's schema (capabilities, install instructions, repo URL)
  2. Submit to modelcontextprotocol/registry

Estimate: ~15–30 minutes once BoJ's current capability inventory is locked in.

Historical context (so future-self knows why this is filed)

A local fork of modelcontextprotocol/servers at /home/hyperpolymath/developer/repos/servers had a commit (aa744a6) adding a BoJ entry to upstream's old README list. That fork is being abandoned (bundle archived at ~/repo-archives/2026-06-02-local-only-forks/servers-fork-archive-2026-06-02.bundle) because the README list it patches no longer exists upstream. The visibility intent is preserved by this issue.

Decision needed

Owner: publish to registry (yes/no/later). Not urgent; low-cost option-preserving filing.

🤖 Generated with Claude Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions