Skip to main content
Glama
enesjakozh
0xshellming

mcp-summarizer

by 0xshellming
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

MCP内容摘要服务器

模型上下文协议 (MCP) 服务器使用 Google 的 Gemini 1.5 Pro 模型，为各种类型的内容提供智能摘要功能。此服务器可以帮助您生成简洁的摘要，同时保留不同内容格式的关键信息。

由 3MinTop 提供支持

摘要服务由3MinTop提供支持，这是一款基于人工智能的阅读工具，可帮助您在三分钟内理解章节内容。3MinTop 将复杂的内容转化为清晰的摘要，提高学习效率并帮助养成持久的阅读习惯。

Related MCP server: Summarizer Ai MCP

特征

  • 使用 Google Gemini 1.5 Pro 模型进行通用内容摘要

  • 支持多种内容类型：

    • 纯文本

    • 网页

    • PDF 文档

    • EPUB 图书

    • HTML 内容

  • 可自定义摘要长度

  • 多语言支持

  • 智能上下文保存

  • 用于测试的动态问候语资源

入门

  1. 克隆此存储库

  2. 安装依赖项：

    pnpm install

  3. 构建项目：

    pnpm run build

  4. 启动服务器：

    pnpm start

发展

  • 使用pnpm run dev以监视模式启动 TypeScript 编译器

  • 修改src/index.ts以自定义服务器行为或添加新工具

与桌面应用程序一起使用

要将此服务器与桌面应用程序集成，请将以下内容添加到应用程序的服务器配置中：

{
  "mcpServers": {
    "content-summarizer": {
      "command": "node",
      "args": [
        "{ABSOLUTE PATH TO FILE HERE}/dist/index.js"
      ]
    }
  }
}

可用工具

总结

使用以下参数总结来自各种来源的内容：

  • content (string | object): 需要汇总的输入内容。可以是：

    • 文本字符串

    • 网页的 URL

    • Base64编码的PDF

    • EPUB 文件内容

  • type （字符串）：内容类型（“text”，“url”，“pdf”，“epub”）

  • maxLength （数字，可选）：摘要的最大长度（以字符为单位）（默认值：200）

  • language （字符串，可选）：摘要的目标语言（默认值：“en”）

  • focus （字符串，可选）：摘要中需要关注的具体方面

  • style （字符串，可选）：摘要样式（“简洁”，“详细”，“要点”）

使用示例：

// Summarize a webpage
const result = await server.invoke("summarize", {
  content: "https://example.com/article",
  type: "url",
  maxLength: 300,
  style: "bullet-points"
});

// Summarize a PDF document
const result = await server.invoke("summarize", {
  content: pdfBase64Content,
  type: "pdf",
  language: "zh",
  style: "detailed"
});

问候

演示基本 MCP 资源功能的动态资源：

  • URI 格式： greeting://{name}

  • 返回带有指定名称的问候消息

贡献

欢迎贡献代码！欢迎提交 Pull 请求。

执照

该项目根据 MIT 许可证获得许可 - 有关详细信息，请参阅LICENSE文件。

Available Tools

1 tool
summarizeD
ParametersJSON Schema
NameRequiredDescriptionDefault
languageNoen
maxLengthNo
textYes

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

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

  1. 1 tool updatev1.0.0
    • First observedsummarize
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

D1.7/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'summarize' has no competing alternatives within this server, making disambiguation trivial.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'summarize' follows a clear verb pattern, but consistency cannot be assessed across a set of one.

Tool Count2/5

One tool is too few for most practical server purposes, as it severely limits functionality and scope. For a summarizer, this feels thin and incomplete, lacking operations like list_summaries, get_summary, or customize_summary that would enhance utility.

Completeness1/5

The server is severely incomplete for a summarizer domain. With only a single 'summarize' tool and no description, there are obvious gaps: no way to retrieve, update, delete, or list summaries, and no coverage of related operations like configuration or batch processing.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches