Summarization Functions

Created By
Braffolka year ago
Provides summarised output from various actions that could otherwise eat up tokens and cause crashes for AI agents
Overview

What is Summarization Functions?

Summarization Functions is a powerful MCP server that provides intelligent text summarization capabilities to manage context windows effectively for AI agents.

How to use Summarization Functions?

To use the Summarization Functions, install the package via npm and integrate it into your MCP configuration. Use the various summarization methods provided for command output, file contents, and directory structures.

Key features of Summarization Functions?

  • Concise command output summarization.
  • Technical analysis of file contents.
  • Overview of complex directory structures.
  • Optimization for various AI agents to prevent context overflow.
  • Support for multiple AI providers for enhanced flexibility.

Use cases of Summarization Functions?

  1. Enhancing the performance of AI agents by managing context size.
  2. Summarizing lengthy command outputs to focus on critical information.
  3. Analyzing and summarizing multiple file contents for brevity.

FAQ from Summarization Functions?

  • Is it necessary to use summarization functions for AI agent operations?

Yes, it is essential to use summarization for all potentially large outputs to avoid context overflow.

  • Can I use different AI providers with this server?

Yes, the server supports multiple AI providers including Anthropic, OpenAI, and Google.

  • How can I configure the server?

Configuration requires setting environment variables for the chosen AI provider along with the API key and model ID.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Braffolk
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago