Add the RoboDebut directory-submission MCP server to the integration catalog

Aperta Adatta ai principianti
#975 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
68/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
python
Ambito
devtools

Direzione di ricerca

Copia la forma di integrations/catalog/deepwiki.json in un nuovo integrations/catalog/robodebut.json con l’URL shttp e auth.strategy impostato su none. Aggiungi robodebut a public_remote_mcp_ids in tests/test_catalogs.py::test_remote_no_auth_mcp_entries_are_intentionally_public, poi esegui npm run build:integrations. Fatto quando tests/test_catalog_schema.py, tests/test_catalogs.py e tests/test_integration_catalog_in_sync.py passano e tools/list restituisce esattamente i due strumenti, senza chiamare submit_project.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

priority:low ready-for-dev

Summary

Add RoboDebut's hosted MCP server to the integration catalog (integrations/catalog/robodebut.json) as a no-auth card. RoboDebut is a directory of websites and startups, and coding agents submit the listings. When an agent works on a user's website, it can send that site for manual review and check the submission's status later.

Why

The catalog has nothing for listing a project in a directory. RoboDebut runs a Streamable HTTP server at https://robodebut.com/api/mcp with no account or API key, the same shape as deepwiki. It has two tools:

  • submit_project sends a site for manual review. It creates a submission, so the user should authorize it first. It requires the user's contact email, which RoboDebut keeps private. The site needs a visible RoboDebut badge on its homepage as an ordinary followed link (no rel="nofollow") in the raw homepage HTML, and an operator reviews each listing before it goes public.
  • get_submission_status is read-only. It takes the private receipt returned by submit_project.

Setup and submission rules are in https://robodebut.com/llms.txt, which the server also exposes as the submission_instructions resource.

Proposal

  • One new hand-authored file, integrations/catalog/robodebut.json: a single shttp option at https://robodebut.com/api/mcp, auth.strategy: "none", docsUrl https://robodebut.com/submit-with-a-coding-agent.
  • The regenerated integrations/catalog-index.js from npm run build:integrations.
  • Add robodebut to public_remote_mcp_ids in tests/test_catalogs.py::test_remote_no_auth_mcp_entries_are_intentionally_public, since this is an intentionally public remote entry.

Acceptance criteria

  • integrations/catalog/robodebut.json is the only hand-authored catalog file added. The regenerated integrations/catalog-index.js and the allowlist line are the only other changes.
  • The entry validates against integrations/catalog.schema.json, and tests/test_catalog_schema.py, tests/test_catalogs.py and tests/test_integration_catalog_in_sync.py pass.
  • With no credentials, an MCP client built from the entry lists submit_project and get_submission_status. Verification should stop at tools/list and not call submit_project, because that call creates a submission for operator review.

Non-goals

  • No OAuth or API-key option. The server has neither.
  • No icon or popularityRank change.
  • No source change. The server is closed source and hosted by RoboDebut. The MIT-licensed part is the Kiro package at https://github.com/hboon/robodebut-kiro, which holds configuration and a skill but not the server.

Notes

I built RoboDebut and also build GetLinkBunny. submit_project responses for a submission pending review, including one already in review, and every valid get_submission_status response include an optional GetLinkBunny invitation for the user to read. The invitation authorizes no action, and the RoboDebut review does not depend on it.

Checks on 2026-11-22: https://robodebut.com/llms.txt and the docsUrl return 200, and /.well-known/oauth-protected-resource returns 404, so a no-auth card offers no sign-in.

An AI assistant drafted this issue for me and opened it from my account at my request.

Could a maintainer or the triage automation add ready-for-dev if this fits the catalog?


OpenHands AI triage

The following comments and acceptance criteria were added by the OpenHands AI agent.

Triage

Evidence check against OpenHands/extensions main (root AGENTS.md, integrations/README.md, integrations/catalog.schema.json, the adjacent no-auth entry integrations/catalog/deepwiki.json, and the catalog tests):

  • Repository policy is one hand-authored file change in integrations/catalog/ plus the regenerated integrations/catalog-index.js via npm run build:integrations; the issue's file plan matches it, and the entry shape mirrors deepwiki.json.
  • tests/test_catalogs.py::test_remote_no_auth_mcp_entries_are_intentionally_public pins the allowlist to {"cloudflare-docs", "deepwiki", "huggingface"} on main, so robodebut must be added there for the suite to pass.
  • Live verification on 2026-11-22: https://robodebut.com/llms.txt and the docsUrl return 200; https://robodebut.com/.well-known/oauth-protected-resource returns 404; MCP initialize and tools/list at https://robodebut.com/api/mcp succeed with no credentials and return exactly the tools submit_project and get_submission_status; submit_project's category enum matches the list in llms.txt.
  • submit_project is annotated readOnlyHint: false and creates a proposal for operator review, so validation must stop at tools/list; this is consistent with RoboDebut's own instructions and per-IP/per-domain rate limits.
  • The hosted server is closed source; the MIT-licensed hboon/robodebut-kiro repo holds configuration, not the server, so the non-goal on source metadata holds.

Comparable catalog proposals (#935, #946, #947, #973) carry priority:low; this issue records no user pain beyond the author's request, so it stays priority:low.

Non-goals: no OAuth or API-key option, no icon or popularityRank change, no source-repository metadata on the entry, no runtime/client code changes outside the catalog, no GetLinkBunny-related catalog content, and no changes to RoboDebut's badge or review behavior.

Acceptance Criteria
  • integrations/catalog/robodebut.json is the only new hand-authored catalog file. It defines a single shttp connection option at https://robodebut.com/api/mcp with auth.strategy: "none" and docsUrl: https://robodebut.com/submit-with-a-coding-agent; the only other changes are the regenerated integrations/catalog-index.js and the robodebut line in public_remote_mcp_ids in tests/test_catalogs.py.
  • integrations/catalog/robodebut.json validates against integrations/catalog.schema.json, and tests/test_catalog_schema.py, tests/test_catalogs.py (including test_remote_no_auth_mcp_entries_are_intentionally_public), and tests/test_integration_catalog_in_sync.py pass.
  • With no credentials configured, an MCP client built from the entry's connection option connects to https://robodebut.com/api/mcp and tools/list returns exactly submit_project and get_submission_status; no tool is invoked beyond tools/list (in particular, submit_project is never called during validation).
Lingua principale
Python
Stelle
184
Fork
137
Merge medio
1g 19h
PR unite (30g)
46

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di OpenHands/extensions

Tutte le issue di OpenHands/extensions

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.