Skip to main content
Glama
0xshellming

mcp-summarizer

by 0xshellming

MCP Content Summarizer Server

A Model Context Protocol (MCP) server that provides intelligent summarization capabilities for various types of content using Google's Gemini 1.5 Pro model. This server can help you generate concise summaries while maintaining key information from different content formats.

Powered by 3MinTop

The summarization service is powered by 3MinTop, an AI-powered reading tool that helps you understand a chapter's content in just three minutes. 3MinTop transforms complex content into clear summaries, making learning efficient and helping build lasting reading habits.

Related MCP server: Summarizer Ai MCP

Features

  • Universal content summarization using Google's Gemini 1.5 Pro model

  • Support for multiple content types:

    • Plain text

    • Web pages

    • PDF documents

    • EPUB books

    • HTML content

  • Customizable summary length

  • Multi-language support

  • Smart context preservation

  • Dynamic greeting resource for testing

Getting Started

  1. Clone this repository

  2. Install dependencies:

    pnpm install
  3. Build the project:

    pnpm run build
  4. Start the server:

    pnpm start

Development

  • Use pnpm run dev to start the TypeScript compiler in watch mode

  • Modify src/index.ts to customize server behavior or add new tools

Usage with Desktop App

To integrate this server with a desktop app, add the following to your app's server configuration:

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

Available Tools

summarize

Summarizes content from various sources using the following parameters:

  • content (string | object): The input content to summarize. Can be:

    • Text string

    • URL for web pages

    • Base64 encoded PDF

    • EPUB file content

  • type (string): Content type ("text", "url", "pdf", "epub")

  • maxLength (number, optional): Maximum length of the summary in characters (default: 200)

  • language (string, optional): Target language for the summary (default: "en")

  • focus (string, optional): Specific aspect to focus on in the summary

  • style (string, optional): Summary style ("concise", "detailed", "bullet-points")

Example usage:

// 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"
});

greeting

A dynamic resource that demonstrates basic MCP resource functionality:

  • URI format: greeting://{name}

  • Returns a greeting message with the provided name

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

This project is licensed under the MIT License - see the LICENSE file for details.

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. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • First observedsummarize

TDQS

D1.7/5.0
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

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/0xshellming/mcp-summarizer'

If you have feedback or need assistance with the MCP directory API, please join our Discord server