How to publish an MCP from a GitHub Organization repository?

[flightmasterDast]

We are trying to publish our official Remote MCP service to the LobeHub Marketplace.

Repository:
https://github.com/flight-master-dast/aviation-data-mcp

The repository is owned by the GitHub Organization flight-master-dast. The GitHub account connected to LobeHub is my personal account, and I am an owner/admin of that organization.

The current Market CLI appears to require the repository owner to match the connected GitHub username, which prevents organization-owned repositories from being submitted.

I found a similar issue here:
#17416

Is there currently an alternative submission method, manual review path, or recommended workaround for official GitHub Organization repositories?

[skyzhao1223]

No — there is still no documented and confirmed-working submission path for GitHub-Organization-owned repositories, and #17416 remains open. However, the strict "repo owner must equal your GitHub username" check you hit belongs to the old lhm plugin submit flow, which was removed in @lobehub/market-cli 0.0.40 (2026-08-06); the current CLI/SDK contract explicitly says "own it or have push access" and "Organization repositories require push or admin access" — so the right first step is to retry with the current publish flow below and report the exact result in #17416.

(Note: lobehub/lobe-chat was renamed to lobehub/lobehub; old URLs redirect, so your links still resolve.)

What the ownership check actually is (evidence)

The check is server-side in the closed-source Market backend (https://market.lobehub.com; the repo referenced by the npm packages, lobehub-biz/lobehub-market, is private/404). The CLI only relays the API error, which is why the message "Repository owner … does not match your GitHub username …" appears nowhere in the CLI or SDK bundles. What is public and verifiable is the contract shipped in the npm packages:

Version (date)	Contract for repo submission
@lobehub/market-sdk 0.39.2 (2026-07-08), used by CLI 0.0.38/0.0.39	submitRepo doc: "The user must have a verified GitHub profile and the repository owner must match their GitHub username." SubmitRepoParams.type: 'plugin' | 'skill', gitUrl "(must be owned by the authenticated user)" → POST /v1/user/claims/submit-repo. This is the version that produced the errors in #17005/#17416/#17431.
@lobehub/market-sdk 0.40.0/0.40.1 (2026-08-06/13), used by CLI 0.0.40/0.0.41	submitRepo doc: "Submits a GitHub repository the authenticated user owns or can push to … Organization repositories require push or admin access." type narrowed to 'skill' only. New publishPlugin → POST /v1/user/plugins with PublishPluginParams.gitUrl: "GitHub repository URL (authenticated user must own it or have push access)".
CLI claim hint	0.0.38–0.0.40: "3. Your GitHub username matches the plugin's author" → 0.0.41 (2026-08-13, current latest): "3. You own, or have push access to, the plugin's GitHub repository".

I also verified against the full command list in dist/cli.js of 0.0.41: there is no --org flag or any organization option in the CLI. The SDK's org surface (setOwnerAccountId / x-lobe-owner-account-id, /v1/organizations/*) is for LobeHub cloud workspace organizations (trusted-client-created, keyed by clerkId/workspaceId), not GitHub orgs, and the CLI never calls it.

Timeline worth noting: maintainer @ONLY-yours (LiJian, LobeHub; npm publisher of market-cli 0.0.41 as blueboylijian) acknowledged #17416 on Jul 21 ("I've dealt with this claim before; I'll double-check to see why it failed"), and the publish flow + ownership contract were reworked on Aug 6–13. That strongly suggests the push-access relaxation is the in-flight fix — but the backend is closed-source and neither #17416 nor #17431 has a public confirmation that org repos now pass, so treat it as documented but unconfirmed.

The current submission flow to try (CLI 0.0.41+)

Your server is already in the official MCP registry as io.github.flight-master-dast/aviation-data-mcp (v1.0.0, streamable-http at https://fly.huoli.com/mcp/dast_mcp), and the repo is org-owned — exactly the case the new contract claims to support:

npx -y @lobehub/market-cli@latest login
npx -y @lobehub/market-cli@latest github connect   # on GitHub's authorize page, grant the flight-master-dast org
mkdir aviation-data-mcp && cd aviation-data-mcp
npx -y @lobehub/market-cli@latest plugin init --url https://fly.huoli.com/mcp/dast_mcp
npx -y @lobehub/market-cli@latest plugin publish https://github.com/flight-master-dast/aviation-data-mcp

Notes, all verified from the 0.0.41 bundle: plugin submit no longer exists (if you still see it, npx served you a stale ≤0.0.39 build); plugin init generates lhm.plugin.json (identifier will be flight-master-dast-aviation-data-mcp, tools discovered live from your endpoint); plugin publish POSTs the manifest + gitUrl and the server runs ownership validation + async repo enrichment. If it still rejects with an owner-mismatch error, please paste the exact message into #17416 — that is the data point the maintainers are missing.

State of the tracking issues (as of 2026-09-21)

• #17416 — open. Maintainer acknowledged Jul 21; a second org (roamzy-io) reported on Aug 5 that the claim path (scorecard "Not Claimed by Owner" + GitHub badge) still fails; no fix confirmation since.
• #17431 — open. Same bug: org admin with the OAuth org grant explicitly given, still Repository owner "seldonframe" does not match your GitHub username "fixlyai".
• #17005 — closed not_planned and locked (first report, contains the original error text).

Workarounds, ranked, with honest labels

1. Retry with the current CLI publish flow (above). Mechanism verified from shipped source; org acceptance documented in SDK 0.40.x types but not publicly confirmed. Most likely intended path today.
2. Subscribe to / comment on [Bug] Market CLI cannot claim or submit GitHub organization repositories #17416 with your exact CLI version + error. Verified as the active tracking issue with maintainer engagement; also the channel where a user successfully asked maintainers to manually correct a listing (GCrapuzzi, Aug 24).
3. Wait for the official-MCP-registry crawl, then claim. Mechanism verified: the Market backend has admin-only importOfficialMcpRegistry/syncOfficialMcpRegistry services, and other org repos got unclaimed public listings this way (lobehub.com/mcp/ampres-ai-talamus, …/roamzy-io-mcp-server — both 200 today; yours is 404 so far). Once listed, lhm plugin claim flight-master-dast-aviation-data-mcp. Caveat: claim for org repos is precisely what [Bug] Market CLI cannot claim or submit GitHub organization repositories #17416 reports as broken (badge claim failed Aug 5), so this only helps if the push-access fix shipped server-side.
4. Web "Submit Repo" modal. Exists (verified in code): lobehub.com → Community → your profile → Skills section → "Submit Repo" ("Submit your GitHub repository to import your Skills or MCPs to the community… will be reviewed before being published" — SubmitRepoModal.tsx, locale user.submitRepo*). It posts to the same /v1/user/claims/submit-repo endpoint (hard-coded type: 'skill' in the frontend), so the same server-side ownership validation applies; org/MCP behavior unverified. One user reported it "automation-gated" ([Request] Add reelier to the MCP marketplace #17427).
5. Mirror or transfer the repo to your personal account. Speculative, not documented anywhere. Mechanically consistent with the old check (owner == username), but it splits your official branding, duplicates the registry entry (which points at the org repo), and changes the listing identifier. Last resort only.
6. What does not exist (verified): a --org-style CLI flag; GitHub App / machine-user authentication (CLI login is OAuth2 PKCE against market.lobehub.com with fixed client id lobehub-cli, and a machine user wouldn't match the org name either); any documented manual-review form/email; the "[Request] Add …" issue route as a reliable path — precedent [Request] Add reelier to the MCP marketplace #17427 was closed and that server (reelier) has no public listing today.

One correction to a claim circulating in those issues

A bot comment in #17431 points to a "Request a Server" button on lobehub.com/mcp as the interim path. I could not verify any such button in the current app locales or code (the verified entry point is the "Submit Repo" modal on your Community profile, item 4). Treat the bot's claim as unverified.

---

What I read: @lobehub/market-cli 0.0.38/0.0.39/0.0.40/0.0.41 and @lobehub/market-sdk 0.39.2/0.40.0/0.40.1/0.41.0 npm tarballs (dist/cli.js, dist/index.mjs, dist/index.d.mts); lobehub/lobehub files apps/server/src/routers/lambda/market/socialProfile.ts, src/routes/(main)/community/(detail)/user/features/SubmitRepoModal.tsx, …/workspace/features/WorkspaceSkillList.tsx, packages/locales/src/default/discover.ts; issues #17005/#17416/#17427/#17431; registry.modelcontextprotocol.io.

[andrii-dolzhenko]

This looks like a known Market CLI limitation rather than an issue with your GitHub permissions.

#17416 reproduces the same behavior with organization-owned repositories: plugin claim / plugin submit compare the repository owner with the connected GitHub username, so an org repo is rejected even when the connected user has owner/admin access.

Since #17416 is still open, I don't see a documented self-service workaround for organization repositories at the moment. I'd reference your case there (or open a related issue) with the CLI version and exact error output so it can be tracked against the same bug.