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

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)
• 🎃 Add "Copy as cURL" to an audit log entry to replay the MCP tool call #999: "Copy as cURL" on an audit log entry (frontend)
• 🎃 Show the build version and git commit in the UI and the backend startup log #1000: show the build version and git commit in the UI and startup log
• 🎃 Add "Open in MCP Inspector" to the MCP server page #1002: "Open in MCP Inspector" on the MCP server page (frontend)
• AGENTS.md for AI coding agents (done)
• new adapter: MOCO (done)
• 🎃 New adapter: Qonto business banking (read-only) #1013: new adapter: Qonto (read-only)
• 🐣 Good first issue: contribute a new MCP adapter #982: contribute any new MCP adapter

Medium: 1–2 days

• 🎃 Export the audit log as CSV or JSON from /logs #998: export the audit log as CSV or JSON
• 🎃 Add a shared EmptyState component and use it for the "No … yet" screens #1001: shared EmptyState component (frontend)
• 🎃 Add an opt-in Prometheus /metrics endpoint for tool calls #1003: opt-in Prometheus /metrics endpoint
• 🎃 Export a single connector as JSON or YAML, and accept YAML on import #1004: export a single connector as JSON or YAML
• 🎃 Import a HAR file (browser network capture) as REST tools #1005: import a HAR file as REST tools
• 🎃 Add a ⌘K / Ctrl+K command palette to the admin UI #1010: ⌘K / Ctrl+K command palette (frontend)
• 🎃 Generate llms.txt and llms-full.txt from the repo docs so AI agents can read them #1011: generate llms.txt from the docs
• 🎃 Add a "Share / README badge" section with Add-to-Cursor and Add-to-VS-Code badges #1012: "Add to Cursor / VS Code" README badges
• 🎃 New adapter: PlentyONE / plentymarkets (e-commerce ERP) #1014: new adapter: PlentyONE / plentymarkets

Large: several days, can be split

• 🎃 Send an alert webhook when a connector keeps failing #1006: alert webhook when a connector keeps failing
• 🎃 Add a Helm chart for self-hosted Kubernetes installs #1007: Helm chart for Kubernetes
• 🎃 Set up i18n in the frontend and translate the sidebar and sign-in form (DE, IT) #1008: i18n foundation for the UI (DE, IT)
• 🎃 Build an amcp CLI (MVP): log in with an API key, list and call tools #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.