Multi Poc Alpha MCP server

mcp-multi-poc

PoC for serving multiple MCP servers from a single PyPI package, using subcommands for server selection and optional extras for on-demand dependencies. Stands in for the Couchbase MCP monorepo question (alpha = operational, beta = analytics, tabulate = the analytics SDK — chosen because it is outside fastmcp's transitive dependency tree; httpx and pyyaml are not, and silently defeat the extras guard).

<!-- mcp-name: io.github.nithishr/mcp-multi-poc-alpha --> <!-- mcp-name: io.github.nithishr/mcp-multi-poc-beta --> <!-- mcp-name: io.github.nithishr/mcp-multi-poc-beta-script -->

What this PoC must answer

Findings so far (2026-07-31)

against the shared package.

• Q1 — multiple entries per PyPI package: YES. mcp-multi-poc-alpha published

three comments present).

• Q2 — multiple mcp-name comments in one README: YES (alpha validated with

Extras in the identifier fail the literal PyPI lookup — PyPI package 'mcp-multi-poc[beta]' not found (status: 404). Fallback works: mcp-multi-poc-beta published successfully with plain identifier: mcp-multi-poc + runtimeArguments: --from "mcp-multi-poc[beta]" (live in the registry, verified via the /v0/servers API).

• Q3 — extras in identifier: NO, but expressible via runtimeArguments.

publish).** Same 404 mechanism ('mcp-multi-poc-beta' not found) — the registry validates the identifier as a real PyPI package before anything else.

• **Q5a — differently-named console script as identifier: NO (confirmed on

io.github.nithishr/mcp-multi-poc-beta-script is live (published 2026-07-31, after trimming description to the 100-char limit — the only validation hiccup). Locally, uvx --from 'mcp-multi-poc[beta]' mcp-multi-poc-beta mcp-multi-poc completes the MCP initialize handshake — the trailing identifier is silently ignored because main() never parses argv. Caveats: only safe when the entrypoint tolerates stray argv (click needs ignoreunknownoptions + allowextraargs or a dummy optional argument); depends on clients preserving runtimeArguments order — the least-exercised metadata path; registry UIs show the identifier as the runnable. For production script-per-server, prefer a shim package per script (identifier == script name, no runtimeArguments at all).

• Q5b — script name as positional runtimeArgument: YES, published.

identifier must be a literal, existing PyPI package (extras rejected); runtimeArguments/packageArguments contents are NOT validated.

• Registry validation limits discovered: description ≤ 100 chars;

Local smoke test (before publishing anything)

Shortened. The full README is on GitHub.