kaedemeta-mcp-server
Related Servers
Alternatives to kaedemeta-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA Python MCP server that wraps the Gelbooru API. Connect it to any MCP-compatible client (Claude Desktop, Cursor, etc.) to search posts, look up tags, and generate Stable Diffusion prompts from real character appearance data — all directly from your AI assistant.271MIT
- AlicenseAqualityBmaintenanceA local-first MCP server that lets AI agents read any webpage as clean Markdown, crawl whole sites within configured limits, search without API keys, and solve supported captchas locally — all without cloud services or third-party keys.1221AGPL 3.0
- AlicenseAqualityDmaintenanceModel Context Protocol server that enables Claude Desktop (or any MCP client) to fetch web content and process images appropriately.124 npmMIT
- AlicenseAqualityCmaintenancemediamcp is an MCP server that connects your AI assistant — Claude Code, Claude Desktop, Cursor, Windsurf, VS Code, or anything else that speaks MCP — to cloud media models (Gemini Flash Image, GPT-5 Image, Seedream, Veo, Sora, …) via OpenRouter or any OpenAI-compatible API.674 npm4MIT
- AlicenseAqualityFmaintenanceProduction-grade MCP server for image and video understanding and generation across Gemini, OpenAI, and Grok.5114 PyPI4Apache 2.0
- AlicenseAqualityDmaintenanceOpen-source MCP server for AI image and video creation, enabling prompt library search, prompt enhancement, and media generation from Claude Code, Cursor, and other MCP hosts.8MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct scopes: one handles a single post, while the other batch-extracts from a creator feed or tag listing. An agent can easily choose between single-item and batch/feed operations.
Both tool names follow the same extract_* snake_case convention with clear noun phrases. There is no mixing of styles or vague verbs.
Two tools is on the thin side for a metadata extraction server, though the pair covers single-post and batch-feed workflows. It is borderline rather than clearly well-scoped because additional query or lookup operations might reasonably belong here.
The surface covers the core extraction lifecycle: one post and creator/tag feeds across the named platforms. Minor gaps exist, such as keyword search or multi-post URL handling, but agents can work around them for the stated purpose.