Skip to main content
Glama
kaedemeta-mcp-server

kaedemeta-mcp-server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
api_keyNoKaedeMeta API key passed as the api_key query parameter when using the native Streamable HTTP / JSON-RPC MCP endpoint.
KAEDEMETA_API_KEYNoKaedeMeta API key passed as an environment variable when using the local uvx stdio bridge.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
extract_post_metadataA

Extract structured metadata and original high-resolution media URLs from a single X (Twitter), Pixiv, or Danbooru post.

extract_creator_feedB

Batch extract original media URLs and metadata from a creator's profile/timeline (@username for X, users/ID for Pixiv) or Danbooru tags.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 2 tools

Disambiguation5/5

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.

Naming Consistency5/5

Both tool names follow the same extract_* snake_case convention with clear noun phrases. There is no mixing of styles or vague verbs.

Tool Count3/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues