docs(README.md): adding mcp-meme-sticky to README #1834
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
A MCP server that allows you to generate memes and further convert them to stickers using the open source free memegen API. No other API use!
Server Details
Motivation and Context
While there exist a few meme generator MCPs, this one adds extra features, namely:
How Has This Been Tested?
Have tested this on Claude using both 3.7 and 3.5 models. Works fine with both, below are some screenshots.
Telegram sticker generation using my custom built Telegram bot - https://github.com/nkapila6/mcp-sticky-tele

Meme saved on desktop!

Breaking Changes
Yes, the user will need to update their MCP configuration on their MCP host of choice, eg. Claude, Cursor, Goose, etc.
UPDATE: added installation instructions in README.
Types of changes
Checklist
Additional context
One important design decision I had to make as Claude Desktop does not support MCP Sampling yet.
To resolve this, I had to a few tool calls (instructing LLM via documentation). I will experiment more on sampling differently until Claude supports it or I find a better solution.
UPDATE: I preprocessed the templates and created metadata for it. Using cosine similarity (dot products) to fetch the best template since nested tool calling is not reliable. Works well, much more deterministic and stable!