Skip to main content
Glama

CosplayTele MCP

面向 CosplayTele 及同类图库站点的 MCP 2(Model Context Protocol,规范 2026-07-28)服务器。

需要 Python 3.14+。已发布:cosplaytele-mcp。

安装

uvx cosplaytele-mcp

uvx 会临时拉取包并走 stdio 启动,适合直接接到宿主。持久安装:

uv tool install cosplaytele-mcp
# 或
pip install cosplaytele-mcp

装完后命令是 cosplaytele-mcp。

Related MCP server: ZeroChan MCP

接入宿主

推荐用 uvx,不必克隆仓库。若宿主找不到 uvx,把 command 换成 uvx 的绝对路径(常见是 ~/.local/bin/uvx)。

Claude Desktop / Cursor(mcpServers):

{
  "mcpServers": {
    "cosplaytele": {
      "command": "uvx",
      "args": ["cosplaytele-mcp"]
    }
  }
}

已用 uv tool install 或 pip install 时:

{
  "mcpServers": {
    "cosplaytele": {
      "command": "cosplaytele-mcp"
    }
  }
}

VS Code .vscode/mcp.json:

{
  "servers": {
    "cosplaytele": {
      "type": "stdio",
      "command": "uvx",
      "args": ["cosplaytele-mcp"]
    }
  }
}

运行

stdio(给宿主用):

uvx cosplaytele-mcp
# 或已安装后
cosplaytele-mcp

HTTP:

uvx cosplaytele-mcp --transport streamable-http --port 8000
# 或
cosplaytele-mcp --transport streamable-http --host 127.0.0.1 --port 8000

对外绑定时必须显式列出可信的浏览器 Origin:

cosplaytele-mcp --transport streamable-http --host 0.0.0.0 --port 8000 \
  --allowed-host mcp.example.com \
  --allowed-origin https://mcp.example.com

--host 只是本地监听地址;--allowed-host 必须填写反向代理转发的 Host(可重复指定, 也可使用 example.com:* 匹配端口)。非 localhost 监听时,--allowed-host 和 --allowed-origin 都是必填项。生产环境还应在反向代理或网关启用 HTTPS、认证、限流和审计。 本项目只公开现代 Streamable HTTP;旧版 HTTP+SSE 已从 CLI 移除。

popular_kind=archive 表示源站的分类或默认归档,不表示按统计热度排名。ranking_kinds 与内容 categories 分开列出。

源

id

站点

热门

最新

搜索

cosplaytele

https://cosplaytele.com

页脚「Popular Cosplay」组件

HTML 归档 /page/N/

HTML ?s=

hentaicosplay

https://hentai-cosplay-xxx.com

/ranking/ 及 like/bookmark 等

/search/

/search/keyword/

everia

https://everia.club

无

Cosplay 等分类 REST

WP REST

misskon

https://misskon.com/tag/cosplay/

无

WP REST tags=cosplay

WP REST

fourkhd

https://www.4khd.com

分类 popular

orderby=date

WP REST

kiutaku

https://kiutaku.com

/hot

/?start=

?search=

cup2d

https://cup2d.com

无

WP REST

WP REST

beauty3600000

https://3600000.xyz

HTML /category/cosplay/

无

无(?s= 与 WP REST 均触发 PHP 内存错误)

foamgirl

https://foamgirl.net/cosplay

/cosplay

无

?s=

ososedki

https://ososedki.com

/api/albums?type=top

/api/albums

type=search

mitaku

https://mitaku.net

/category/ero-cosplay/

无

?s=

lovecutes

https://www.lovecutes.com/type/6/

Cosplay 分类(type/6)

无

全站搜索后仅保留 Cosplay 分类

simplycosplay

https://www.simply-cosplay.com

API sort=hot

API sort=new

api.simply-porn.com/v2/search

jjcos

https://jjcos.com/tag/HSQ2151O0wZ/

Cosplay 标签归档

无

/api/index.html 标题过滤

buondua

https://buondua.com/tag/cosplay-10688

Cosplay 标签归档

无

?search=

xasiat

https://www.xasiat.com/albums/categories/cosplay/

sort_by=album_viewed_week

sort_by=post_date

/search/search/

baobua

https://baobua.net/category/Cosplay

Cosplay 分类归档

无

全站 ?s=

工具

  • list_sources:源目录

  • open_url(url, offset=0, limit=20):从完整帖子 URL 按域名选源并打开图集

  • search(query, source=all, page=1, category?, exclude_ai=true):按站点真实接口搜索。source=all 时并行查全部源,结果按源交错排列

  • browse(source, sort=popular|latest, page=1, query?, category?, period?, exclude_ai=true):排行 / 最新;只带 category 时按该分类列出,不走关键词搜索;带 query 时走该源搜索。period 仅部分源的热门有效:CosplayTele 为 last24hours|last7days|last30days|all,Hentai Cosplay 为 day|week|month|year。CosplayTele 的 WordPress 排行 REST 接口当前整站 500,源改为抓站内 HTML;所有 period 都回落到同一个「Popular Cosplay」精选组件,不再区分时间窗

  • browse_tag(source, tag, page=1, exclude_ai=true):按标签列出

  • related(source, path, page=1, exclude_ai=true):相近套图。CosplayTele 走 Contextual Related Posts;其余源用图集第一个标签

  • get_gallery(source, path, offset=0, limit=20):详情和图片 URL。默认只回前 20 张加 image_count;limit=0 只回元数据。path 用列表或搜索结果里的 path,也接受完整帖子 URL。image_assets 为每个 image_urls 条目附带源站要求的请求头;可能带 download_urls、has_video(有视频时只打标,不返回可播放流)

  • fetch_image(source, path, index):按需取图集中的一张,按 image_assets 的请求头请求源站,并返回 MCP ImageContent。只拉取源站 allowlist 上的 URL;JJCOS(i1.wp.com)、BaoBua(blogger.googleusercontent.com)、Simply Cosplay 独立 CDN 会被拒绝,请改用 image_assets 自行请求。不写本地文件,不下载整套图集;单图上限 20 MiB,较大的原图同样用 image_assets。

列表项在源站提供时带 tags、published_at、image_count、has_video。没有的字段为 null / 空列表,不会为凑字段再打详情。年龄语义容易被误判的制服主题词(如 JK、校服、制服、school girl、school uniform、after school)会在标题和标签中追加 (18+);路径、搜索词和源站原始标识不变。

CosplayTele 的 category 除表内 slug 外,也接受模特/作品分类 slug(如 byoru)。Hentai Cosplay 热门 category 为排行种类:like、bookmark、download、tag、keyword、images。OSOSEDKI category=cosplays 列出角色目录,再把名字交给 browse_tag。

exclude_ai 默认开启。只认明确 AI 标记,避免误伤 Ai Yamada、Ai Hoshino 这类名字:

源

AI 标记

CosplayTele

标题/路径/标签命中 ai-art、ai-generated、ai-enhanced(原 ai-art 分类 REST 已失效,改由 HTML 结果打标)

Hentai Cosplay

标题 (AI Generated) / (AI Enhanced),路径 *-ai-generated*,标签 ai-generated / ai-enhanced

MissKon

标签 ai-generated,搜索用 tags_exclude

Cup2D

分类 ai-art / aimodel,搜索用 categories_exclude

OSOSEDKI

标题里的 ai-generated,无独立分类

Mitaku

无 AI 标签页,只能靠标题/路径

其余新源

标题/路径/标签命中 ai-art、ai-generated、ai-enhanced

结果里带 is_ai。get_gallery 仍会返回 AI 图集,只打标不拦截。

搜索实现:

源

接口

CosplayTele

HTML ?s=;分类走 /category/<slug>/,标签走 /tag/<slug>/(WP REST 整站 500 后不再依赖)

Everia / Cup2D

/wp-json/wp/v2/posts?search=

4KHD

/index.php?rest_route=/wp/v2/posts

Hentai Cosplay

/search/keyword/<kw>/

MissKon

WP REST search=,默认浏览 tag cosplay

Kiutaku

?search=

FoamGirl

/?s=,默认浏览 /cosplay

OSOSEDKI

/api/albums?type=search

Mitaku

/?s=

Simply Cosplay

api.simply-porn.com/v2/search?query=

JJCOS

/api/index.html 缓存后按标题/链接/标签过滤 Cosplay;默认浏览 Cosplay 标签

Buon Dua

?search=;默认浏览 /tag/cosplay-10688

Xasiat

/search/search/ XHR block;category=cosplay 时按标题/路径过滤;默认浏览 Cosplay 相册分类

BaoBua

全站 /?s=(无法锁到 Cosplay 分类);默认浏览 /category/Cosplay

资源:sources://catalog、gallery://{source}/{+path}。提示词:find_gallery。

开发

克隆仓库后用 uv:

uv sync --dev
uv run ruff check src tests
uv run ruff format --check src tests
uv run pytest
uv run mcp dev src/cosplaytele_mcp/server.py

格式化:

uv run ruff format src tests
uv run ruff check --fix src tests

Available Tools

7 tools
browseBrowse a gallery sourceA
Read-only

List popular or latest galleries from one source.

Use search() when the user names a character, series, model, or tag. If query is set, this tool searches that one source instead of ranking. If only category is set, list that category with sort (not a keyword search). Pass each item's path to get_gallery to fetch image URLs.

Inputs: source (required), page, sort, query, +3 more. Returns: page, items, source, has_next_page

browse_tagBrowse galleries by tagA
Read-only

List galleries for one tag on one source.

Prefer this over search() when you already have a tag from get_gallery.

Inputs: tag (required), source (required), page, exclude_ai. Returns: page, items, source, has_next_page

list_sourcesList gallery sourcesA
Read-only

Return every gallery source this server can query.

Call this first when you need a source id, a category slug, or to check whether a source supports search or latest listings.

Inputs: no named parameters. Returns: result

open_urlOpen a gallery URLA
Read-only

Open a gallery from a full post URL.

Picks the source from the URL host. Use this when the user pastes a link.

Inputs: url (required), limit, offset. Returns: url, path, tags, is_ai, +10 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 7 tools

    Disambiguation4/5

    Tools are mostly distinct: list_sources is metadata, browse is for ranked/listing views, search is keyword-based across sources, browse_tag is tag-specific, related expands from a set, open_url handles full URLs, and get_gallery fetches details. Some overlap exists between browse with a query and search, and browse_tag could be seen as a specialized browse, but descriptions clarify boundaries.

    Naming Consistency3/5

    Most tools follow verb_noun naming (list_sources, open_url, get_gallery, browse_tag), while browse and search are bare verbs, and related deviates entirely. The mixed styles are still readable, but the pattern is not uniform.

    Tool Count5/5

    Seven tools is well-scoped for a gallery aggregator server. Each tool covers a distinct interaction mode (discovery, search, browsing, detail fetch), and none feel redundant or extraneous.

    Completeness4/5

    The surface covers the core read-only lifecycle: discover sources, search/browse, drill into tags, open URLs, and fetch gallery details. Minor gaps exist such as explicit pagination for browse results, but the described workflows are largely complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      Provides AI assistants with access to Civitai's collection of AI models, enabling users to browse, search, and discover AI models through MCP-compatible AI assistants.
      14
      13
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for searching cosmos.so, returning direct CDN image URLs without page scraping.
      3
      109 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables assistants in any MCP client to generate new images or edit existing ones, automatically enriching short requests with composition, lighting, and camera details before sending them to Gemini, OpenAI, or BytePlus Seedream. Supports quality presets, aspect ratios, image sizes, character consistency, blended inputs, and Google Search grounding for current information.
      1,781 npm
      MIT