Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Write example prompts and a FAQ for the Zucchetti and TeamSystem satellites

Open Beginner friendly
#996 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
Half a day
Newbie friendliness
70/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
markdown
Domain
documentation

Research direction

Use scripts/satellites/content/weclapp-mcp-server/ as the template for the layout and tone. Read the tools in packages/backend/src/adapters/it/zucchetti.json and it/teamsystem.json to choose the example questions about invoices, customers, suppliers, items and documents. Done when each of the two satellite folders has prompts.md and faq.md, with Italian .it.md versions optional but welcome.

Written by the indexing model from the issue text.

Description

good first issue hacktoberfest

Same idea as #995, for the two Italian ERPs: zucchetti-mcp-server and teamsystem-mcp-server (tools in packages/backend/src/adapters/it/zucchetti.json and it/teamsystem.json).

  • prompts.md and faq.md in scripts/satellites/content/<repo>/, like content/weclapp-mcp-server/.
  • Italian versions (prompts.it.md, faq.it.md) are very welcome.
  • Good questions are the ones an Italian SME asks its gestionale: open invoices, customers and suppliers, items, documents.

Both adapters were built from the vendors' docs and never run against a live installation. If you have access to one, telling us what works is worth even more than the text.

(This issue first asked for the Kaufland and OTTO satellites; those are published now.)

Dominant language
TypeScript
Stars
856
Forks
82
Avg merge
7h 30m
Merged PRs (30d)
121

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from HelpCode-ai/anythingmcp

All issues in HelpCode-ai/anythingmcp

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.