Drop the operation count from the Firefly III MCP Server entry

[YakupEmreYerli]

Hello — I maintain the Firefly III MCP Server listed on this page, and this is a request to make my own entry less work for you, not more.

The paragraph currently states how many operations the server exposes. That number changes every time I add one, and because the copy lives here, the only way to correct it is another pull request and another review from you. I would rather it never came to that. So this rewrites the entry to describe what the server does rather than how much of it there is — there is nothing left in it that a release can invalidate, and it should not need touching again.

While I was in there I also added Claude web and mobile, which the server has supported over OAuth since after this entry was written, and credited the author the way the rest of the page does. No links change, and the entry does not get longer.

Thank you for keeping this page. It is how people found the project in the first place.

[JC5]

Hi there!

This is an automated reply. Share and enjoy

You triggered an automated reply, because it seems you removed or changed the AI assistance disclosure from the PR template. Without a valid disclosure, your PR cannot be processed.

Even if you did not use AI, this disclosure must be present. Please reply to your PR and explain your use of AI in any or all of the following areas:

1. Code generation (e.g., when writing an implementation or fixing a bug).
2. Test/benchmark generation
3. Documentation (including examples)
4. Research and understanding

There cannot be interaction with your PR without this disclosure.

If the disclosure is present but the bot did not pick up on it, please accept my apologies for the intrusion. Contrary to other bots, this one is just a simple bash script and it may be wrong.

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[YakupEmreYerli]

Apologies — I replaced the PR template with my own description and dropped the disclosure with it. That was careless of me, not an attempt to avoid the question.

AI usage disclosure

I used AI assistance for:

• Code generation (e.g., when writing an implementation or fixing a bug)
• Test/benchmark generation
• Documentation (including examples)
• Research and understanding

For this pull request: I drafted the replacement paragraph and the description with an AI assistant, and used it to check the house style of the surrounding entries and to confirm my fork was in sync with main before editing, so this would not revert anyone else's work. I reviewed the result before opening the PR. The change is a single line, and the facts in it — OAuth support for Claude web and mobile, npm provenance, the MCP Registry listing — are all things I can point at.

[JC5]

Hey, thanks for your PR. Just one thing from my side, could you make the app description a bit less verbose this time around? I expect most of your text is superfluous to your own readme anyway.

[YakupEmreYerli]

You are right, and it reads that way to me too now — most of it was my README leaking onto your page. Cut to one sentence, which also drops the version-specific numbers this PR was about in the first place.

Thanks for taking the time.

[JC5]

Nice work, this is short and to the point. Merged!