docs: add ADOPTERS.md (#602)

[Diogo-Damasceno]

Fixes #602. Adds an ADOPTERS.md with a table and instructions for projects to list themselves as adopters.

[github-actions]

👋 Welcome, @Diogo-Damasceno, and thanks for opening your first PR on AnythingMCP!

A few quick pointers:

• Make sure CI is green before requesting review (Backend, Frontend, Playwright, CodeQL, Trivy).
• If this is a new adapter, the parametrised catalog.spec.ts test will validate it automatically.
• Sign off your commits if you can — it's not blocking, just nice to have.

Someone from the core team will look at this within ~48h. If you don't hear back, please ping us in Discussions / Q&A.

⭐ While you wait — if you find AnythingMCP useful, a star helps others discover it.

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[keysersoft]

Thanks for picking this up, and welcome. The shape is right, a table plus a "how to add yourself" section is exactly what I asked for. Three changes and it goes in.

Seed it with the first row. An adopters file whose only row is _Add your row here_ reads like nobody uses the project, which is worse than not having the file. Start with us:

| Organization / Project | What they connect | Running since |
| --- | --- | --- |
| [KOCH Freiburg GmbH](https://www.kochfreiburg.de/) | 15+ internal systems: ERP, CRM, SOAP services, on-prem databases | 2025 |

Use the columns from the issue. "What they connect" and "Running since" are the two things a reader actually wants, and a contact column invites people to publish an email they will regret. Also please keep the note from the issue that an organisation can list itself as "a manufacturing company in Germany" if it cannot be named, plenty of our users are in that position.

Add the README link. One line under the Community section pointing at ADOPTERS.md, otherwise nobody finds the file.

One small thing: drop step 3 about applying labels. Contributors cannot set labels on this repo and they should not have to think about it.

Last thing, and it is the only blocker: the CLA check is red. Post the one line the bot asks for on this PR and I will merge once the above is in. Also, fork PRs here need me to approve the workflows by hand, I have done that, so you should see the real checks now.

[Diogo-Damasceno]

I have read the CLA Document and I hereby sign the CLA

[keysersoft]

CLA is in and you addressed everything, thanks for the quick turnaround. I pushed one small commit on top: dropped the leftover "apply the good first issue or roadmap label" step, since contributors cannot set labels here, and reworded the README bullet to match the style of the ones around it.

Merging. The KOCH row is the honest starting point, and now anyone who wants to be listed has a file to send a PR against.