Add the RoboDebut directory-submission MCP server to the integration catalog
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 68/100
Línea de trabajo
Copia la forma de integrations/catalog/deepwiki.json en un nuevo integrations/catalog/robodebut.json con la URL shttp y auth.strategy establecido en none. Agrega robodebut a public_remote_mcp_ids en tests/test_catalogs.py::test_remote_no_auth_mcp_entries_are_intentionally_public, luego ejecuta npm run build:integrations. Terminado cuando tests/test_catalog_schema.py, tests/test_catalogs.py y tests/test_integration_catalog_in_sync.py pasen y tools/list devuelva exactamente las dos herramientas, sin llamar a submit_project.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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_projectsends 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 (norel="nofollow") in the raw homepage HTML, and an operator reviews each listing before it goes public.get_submission_statusis read-only. It takes the private receipt returned bysubmit_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 singleshttpoption athttps://robodebut.com/api/mcp,auth.strategy: "none",docsUrlhttps://robodebut.com/submit-with-a-coding-agent. - The regenerated
integrations/catalog-index.jsfromnpm run build:integrations. - Add
robodebuttopublic_remote_mcp_idsintests/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.jsonis the only hand-authored catalog file added. The regeneratedintegrations/catalog-index.jsand the allowlist line are the only other changes. - The entry validates against
integrations/catalog.schema.json, andtests/test_catalog_schema.py,tests/test_catalogs.pyandtests/test_integration_catalog_in_sync.pypass. - With no credentials, an MCP client built from the entry lists
submit_projectandget_submission_status. Verification should stop attools/listand not callsubmit_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
popularityRankchange. - 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 regeneratedintegrations/catalog-index.jsvianpm run build:integrations; the issue's file plan matches it, and the entry shape mirrorsdeepwiki.json. tests/test_catalogs.py::test_remote_no_auth_mcp_entries_are_intentionally_publicpins the allowlist to{"cloudflare-docs", "deepwiki", "huggingface"}on main, sorobodebutmust be added there for the suite to pass.- Live verification on 2026-11-22:
https://robodebut.com/llms.txtand thedocsUrlreturn 200;https://robodebut.com/.well-known/oauth-protected-resourcereturns 404; MCPinitializeandtools/listathttps://robodebut.com/api/mcpsucceed with no credentials and return exactly the toolssubmit_projectandget_submission_status;submit_project'scategoryenum matches the list inllms.txt. submit_projectis annotatedreadOnlyHint: falseand creates a proposal for operator review, so validation must stop attools/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-kirorepo 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.jsonis the only new hand-authored catalog file. It defines a singleshttpconnection option athttps://robodebut.com/api/mcpwithauth.strategy: "none"anddocsUrl: https://robodebut.com/submit-with-a-coding-agent; the only other changes are the regeneratedintegrations/catalog-index.jsand therobodebutline inpublic_remote_mcp_idsintests/test_catalogs.py. -
integrations/catalog/robodebut.jsonvalidates againstintegrations/catalog.schema.json, andtests/test_catalog_schema.py,tests/test_catalogs.py(includingtest_remote_no_auth_mcp_entries_are_intentionally_public), andtests/test_integration_catalog_in_sync.pypass. - With no credentials configured, an MCP client built from the entry's connection option connects to
https://robodebut.com/api/mcpandtools/listreturns exactlysubmit_projectandget_submission_status; no tool is invoked beyondtools/list(in particular,submit_projectis never called during validation).
- Lenguaje dominante
- Python
- Estrellas
- 184
- Forks
- 137
- Merge medio
- 1 d 19 h
- PR fusionados (30 d)
- 46
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Sin guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de OpenHands/extensions
-
priority:low ready-for-dev
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
OpenHands/extensions#973 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
OpenHands/extensions#970 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
OpenHands/extensions#969 ·
Los mantenedores suelen responder en 1 día
-
Add a `maven` skill: agents install Debian's `maven` package, which can't load plugins built for Java 17+Posiblemente ocupada @sumitvairagar la tomó hace 3 días. Abiertopriority:medium ready-for-dev
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
OpenHands/extensions#963 ·
Los mantenedores suelen responder en 1 día
-
agent-readiness-report: scan_build_env.sh misses lowercase `justfile` and `just` build commandsPosiblemente ocupada @austinchennn la tomó hace 2 días. Abiertopriority:low ready-for-dev
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
OpenHands/extensions#955 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de OpenHands/extensions
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
huggingface/datasets#9128 ·
Los mantenedores suelen responder en 1 día
-
Function/dict state handlers can't supply provider-state injected values (`generate.provider_state`)Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
pact-foundation/pact-python#1789 ·
Los mantenedores suelen responder en 9 días
-
documentation
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
juandresrodca/AdminForge#66 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
backend/local comp/tools P2 tool/terminal type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
NousResearch/hermes-agent#158788 ·
Los mantenedores suelen responder en 1 día