Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

🎃 AnythingMCP October Challenge 2026: pick an issue, ship your first contribution

Abierto
  • ¿Algo no está bien?
#997 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
1/5
Tiempo estimado
Menos de una hora
Aptitud para principiantes
12/100
Tipo de issue
Documentación
Claridad
Necesita aclaración
Estado de actividad
Activo
Área
documentation

Línea de trabajo

This is a challenge announcement, not a task, so there is no code to locate here. Read .github/CONTRIBUTING.md for setup and tests and CLA.md for the sign-off step, then choose one of the linked, concrete issues (such as #1013 or #1000) and work from that issue instead. Done means that issue has an assignee and an open pull request that references it.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

good first issue hacktoberfest help wanted

Hacktoberfest no longer counts pull requests this year, but October is still a great month to make your first open-source contribution. We put together a set of small, well-scoped issues on AnythingMCP, the open-source MCP gateway that turns any REST, SOAP, GraphQL, OData or SQL API into tools for Claude, ChatGPT and Copilot.

Why join

  • Real impact: your change ships in the next release and is used by self-hosted instances and AnythingMCP Cloud.
  • Credit: every merged contributor is thanked by name in the release notes and listed as a contributor.
  • Fast feedback: we assign issues within a day and aim to review pull requests within a few days.
  • Help when you need it: ask questions right in the issue or in Discussions. We're happy to point you to the right files.

Open challenge issues

Every issue lists the files to touch, acceptance criteria, and how the feature behaves on self-hosted instances vs AnythingMCP Cloud.

Small: a few hours, good first issues
  • "Star on GitHub" button on self-hosted instances (done)
  • #999: "Copy as cURL" on an audit log entry (frontend)
  • #1000: show the build version and git commit in the UI and startup log
  • #1002: "Open in MCP Inspector" on the MCP server page (frontend)
  • AGENTS.md for AI coding agents (done)
  • new adapter: MOCO (done)
  • #1013: new adapter: Qonto (read-only)
  • #982: contribute any new MCP adapter
Medium: 1–2 days
  • #998: export the audit log as CSV or JSON
  • #1001: shared EmptyState component (frontend)
  • #1003: opt-in Prometheus /metrics endpoint
  • #1004: export a single connector as JSON or YAML
  • #1005: import a HAR file as REST tools
  • #1010: ⌘K / Ctrl+K command palette (frontend)
  • #1011: generate llms.txt from the docs
  • #1012: "Add to Cursor / VS Code" README badges
  • #1014: new adapter: PlentyONE / plentymarkets
Large: several days, can be split
  • #1006: alert webhook when a connector keeps failing
  • #1007: Helm chart for Kubernetes
  • #1008: i18n foundation for the UI (DE, IT)
  • #1009: amcp CLI (MVP)

More issues are added during the month. Look for the hacktoberfest label and the sub-issues of this issue.

How it works

  1. Pick an issue from the list and comment "I'd like to work on this".
  2. We assign it to you, first come, first served. Please work on one issue at a time.
  3. Open a pull request that references the issue (Closes #<number>). If you need more time, say so in the issue. Otherwise an issue with no pull request after 7 days goes back to the pool.
  4. On your first pull request, the CLA check asks you to sign the Contributor License Agreement. It's a single comment.
  5. Accepted pull requests get the hacktoberfest-accepted label.

Setup, coding conventions and tests are covered in CONTRIBUTING.md.

Quality over quantity

One focused, tested pull request is worth more than five drive-by ones. Pull requests that are generated without understanding the code, or that only change whitespace or typos across files, will be closed.

Have an idea for a good challenge issue? Comment below.

Lenguaje dominante
TypeScript
Estrellas
856
Forks
82
Merge medio
5 h 18 min
PR fusionados (30 d)
162

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de HelpCode-ai/anythingmcp

Todos los issues de HelpCode-ai/anythingmcp

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.