Skip to main content
Glama
profilekit-mcp

profilekit-mcp

by heznpc

profilekit-mcp

ProfileKit 的 MCP 服务器。 通过对话构建 GitHub 个人资料 SVG 卡片 —— 适用于 Claude Code、Codex CLI、ChatGPT Apps 或任何其他支持 MCP 的智能体。


为什么选择 MCP

自 OpenAI 和 Anthropic 于 2025 年末共同宣布 MCP Apps 以来,单个 MCP 服务器即可原生覆盖 Claude Code + Codex CLI + ChatGPT。无需针对每个平台编写适配器。

Related MCP server: unbiased

安装

npm install -g @heznpc/profilekit-mcp

在你的智能体中注册

Claude Code — 添加到仓库中的 .claude/settings.json:

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

Codex CLI — 添加到 ~/.codex/config.toml:

[mcp_servers.profilekit]
command = "profilekit-mcp"

ChatGPT Apps — (Apps SDK MCP 适配器;请参阅 Apps SDK 文档 进行连接)

使用方法

在任何已注册的智能体中,只需询问:

> What ProfileKit cards exist?
> Render a tokyo_night stats card for heznpc.
> Give me a hero banner saying "heznpc" with subtitle "Building the ecosystem AI lives in", wave background, space-grotesk font.
> Build a kanagawa-themed pin card for heznpc/ProfileKit.

智能体将在后台调用 list_cards / list_themes / render,并返回一个 URL 和 Markdown 代码片段,你可以直接粘贴到 README 中。

工具

工具

描述

list_cards

枚举所有 28 种卡片类型,包含单行描述和所需参数

list_themes

列出 17 种内置主题

render

为指定的类型和参数构建卡片 URL、Markdown 和 HTML 代码片段

render 不会获取 SVG。它返回 URL 和代码片段,以便你可以在允许外部 <img> 标签的任何地方嵌入实时图像(GitHub README、dev.to、Hashnode、Notion 封面、幻灯片封面)。

对话示例

You: Render a pin card for heznpc/anvil using the rose_pine theme.

Agent: [calls render(type="pin", params={username: "heznpc", repo: "anvil", theme: "rose_pine"})]

URL:
https://profilekit.vercel.app/api/pin?username=heznpc&repo=anvil&theme=rose_pine

Markdown:
![pin](https://profilekit.vercel.app/api/pin?username=heznpc&repo=anvil&theme=rose_pine)

HTML:
<img src="https://profilekit.vercel.app/api/pin?username=heznpc&repo=anvil&theme=rose_pine" alt="pin" />

路线图

  • v0.2 — 从 ProfileKit /api/catalog 端点进行动态目录同步(当发布新卡片时自动更新)

  • v0.3 — compose_readme(sections) 工具 — 一次调用即可返回完整的博客布局 README 代码片段

  • v0.4 — 可选的 SVG 内联(将卡片内容获取到响应中),供需要分析标记语言的智能体使用

  • v1.0 — 由调用者自身的视觉/LLM 能力支持的调色板建议工具(无内置模型调用)

许可证

MIT © heznpc

Available Tools

3 tools
list_cardsA

List every ProfileKit card type (stats, hero, snake, ...) with a one-line description and the required params for each. Use this before calling render when the user asks what cards exist or which to use. Catalog is fetched live from ProfileKit on first call and cached per process.

Inputs: no named parameters.

list_themesA

List built-in ProfileKit themes (dark, tokyo_night, kanagawa, rose_pine, ...). Any card accepts ?theme=<name>. For fully custom palettes use ?theme_url= pointing to a JSON gist.

Inputs: no named parameters.

renderA

Build a ProfileKit card URL plus ready-to-paste markdown and HTML snippets for the given card type and params. Does NOT fetch the SVG itself — the URL is what consumers embed. Call list_cards first if unsure which type or what params the user's card accepts.

Inputs: type (required), params, alt.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A4.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: list_cards discovers available card types, list_themes retrieves theme options, and render generates card URLs. There is no overlap between them.

    Naming Consistency4/5

    Tools follow a consistent 'verb_noun' pattern with 'list_' for listing and 'render' for generation. 'render' is a bare verb while others have prefix, but it's minor.

    Tool Count5/5

    With 3 tools covering listing, theming, and rendering, the scope is tight and focused. Each tool is essential and the count is appropriate for a card generation server.

    Completeness3/5

    The tools cover the core workflow of discovering cards and themes and generating URLs, but there is no tool for updating or deleting cards (if such operations exist), nor for fetching the rendered SVG directly.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Related MCP Connectors

    Related MCP Servers