MCP Meme Sticky

Created By
nkapila6a year ago
Create AI generated memes using MCP Meme Sticky. Can converted generated memes into stickers for Telegram or WhatsApp (WA coming soon). ✨ no APIs required ✨.
Overview

What is MCP Meme Sticky?

MCP Meme Sticky is a tool that allows users to create AI-generated memes and convert them into stickers for platforms like Telegram and WhatsApp (coming soon). No APIs are required for its operation.

How to use MCP Meme Sticky?

To use MCP Meme Sticky, install it using the provided command and follow the instructions to generate memes based on your prompts. You can then convert these memes into stickers for Telegram.

Key features of MCP Meme Sticky?

  • AI-generated meme creation based on user prompts.
  • Conversion of memes into Telegram stickers.
  • Easy installation and usage without the need for APIs.
  • Integration with the MCP-Sticky Telegram Bot for sticker generation.

Use cases of MCP Meme Sticky?

  1. Creating custom memes for social media sharing.
  2. Generating stickers for use in Telegram chats.
  3. Fun and creative meme generation for personal or group use.

FAQ from MCP Meme Sticky?

  • Can I use MCP Meme Sticky without coding knowledge?

Yes! The installation and usage are designed to be user-friendly.

  • Is there support for WhatsApp stickers?

Currently, WhatsApp sticker conversion is pending development.

  • What platforms does MCP Meme Sticky support?

It has been tested on various MCP clients including Claude Desktop and Cursor.

Server Config

{
  "mcpServers": {
    "mcp-sticky": {
      "command": "uvx",
      "args": [
        "--python=3.10",
        "--from",
        "git+https://github.com/nkapila6/mcp-meme-sticky",
        "mcp-sticky"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
nkapila6
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Voyei

4 hours ago