Skip to main content
Glama
cappt-team

mcp-server-cappt

Official
by cappt-team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mcp-server-cappt: A MCP server for Cappt

Overview

A Model Context Protocol server for generating outline and presentation with cappt.cc.

Tools

  1. generate_presentation

  • Generate a presentation from outline (generated by generate_outline)

  • Input:

    • outline (string): a standard outline

    • include_gallery (bool): whether to include gallery in result

    • include_preview (bool): whether to include preview in result

  • Returns:

    • record_id: the record ID of the generated presentation

    • status: the status of the generation process'

    • total_page: the total number of slides in the presentation

    • editor_url: the URL to edit the presentation

    • title: the title of the presentation

    • thumbanil: the thumbnail of the presentation

    • gallery： the gallery of the presentation

    • preview: the preview of the presentation

Prompts

  1. geenrate_outline

  • Generate a standard outline

  • Input:

    • input (string): user input, eg, title, article, etc.

  • Returns: A standard outline

Related MCP server: Marp MCP Server

Installation

cd path/to/repo
npm install
npm run build

Configuration

Usage with Claude Desktop

Add this to your claude_desktop_config.json:

{
  "mcpServers": {
    "sentry": {
      "command": "node",
      "args": [
        "path/to/repo/dist/index.js"
      ],
      "env": {
        "CAPPT_TOKEN": "YOUR_CAPPT_TOKEN"
      }
    }
  }
}

Debugging

You can use the MCP inspector to debug the server. Please make sure you have installed this package with uv, then run:

npx @modelcontextprotocol/inspector node dist/index.ts

License

This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.

Available Tools

1 tool
generate_presentationC

Generate presentation based on the outline generated by generate_outline

ParametersJSON Schema
NameRequiredDescriptionDefault
outlineYesA standard outline generated by `generate_outline`
include_galleryNoInclude gallery in the generation result
include_previewNoInclude preview in the generation result

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the basic action (generating a presentation). It does not mention side effects, authentication needs, output format, or any constraints. This is insufficient for understanding the tool's behavior.

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

Conciseness4/5

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

The description is a single sentence, very concise and front-loaded with the key purpose. It earns its place without extraneous information. However, it could be slightly more detailed without losing conciseness.

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

Completeness2/5

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

Given the tool has three parameters, no output schema, and no annotations, the description is incomplete. It does not explain what the tool returns, any side effects, or typical usage context. Agents would lack critical information to use the tool effectively.

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

Parameters3/5

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

The input schema covers all parameters with descriptions, achieving 100% coverage. The tool description adds no additional meaning beyond what the schema provides. Baseline score of 3 is appropriate; there is no added value but no deficiency.

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

Purpose4/5

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

The description clearly states the tool generates a presentation based on an outline from `generate_outline`. It uses a specific verb and resource, and implies a pipeline dependency. While there are no sibling tools to differentiate from, the purpose is unambiguous.

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

Usage Guidelines2/5

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

The description only hints that the tool should be used after generating an outline. It provides no explicit guidance on when to use or avoid this tool, no prerequisites, and no alternatives. The lack of context for usage is a significant gap.

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 updatev0.1.5
    • First observedgenerate_presentation
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

C2.9/5.0

Scored across 1 tool

Disambiguation4/5

Only one tool exists, so no ambiguity among tools. However, the tool description references a missing `generate_outline` tool, which could cause confusion about server capabilities.

Naming Consistency5/5

Single tool, so no naming inconsistencies. The name `generate_presentation` follows a clear verb_noun pattern.

Tool Count1/5

A single tool is insufficient for a presentation generation server, especially when it depends on a missing `generate_outline` tool.

Completeness1/5

The server lacks the required `generate_outline` tool that is referenced in the only tool's description, making the tool surface severely incomplete.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers