Skip to main content
Glama
deenesjakoruzh
agenticdecks

deckrun-mcp

by agenticdecks
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Deckrun MCP 서버

PyPI awesome-mcp-servers

참고: 호스팅된 Deckrun 엔드포인트(free.agenticdecks.com, deckrun-mcp-free.agenticdecks.com, api.agenticdecks.com)는 계약별로 프로비저닝됩니다. 액세스 및 가용성을 참조하세요. 아래에 문서화된 pip install deckrun-mcp 패키지 및 로컬 실행 경로는 귀하의 자체 배포 환경에서 즉시 작동합니다. 호스팅된 액세스를 원하시면 액세스 요청을 제출해 주세요. 영업일 기준 1일 이내에 답변해 드립니다.

Agentic Decks에서 제공하는 Deckrun용 MCP 서버 — Markdown에서 프레젠테이션 PDF, 내레이션이 포함된 비디오 및 오디오를 생성합니다. AI 에이전트와 IDE를 위해 구축되었습니다.

Deckrun은 문서 실행 엔진입니다. AI가 콘텐츠를 작성하면 Deckrun이 이를 단일 Markdown 소스에서 픽셀 단위로 완벽한 브랜드 PDF, 내레이션이 포함된 MP4 비디오 및 MP3 오디오로 렌더링합니다. 슬라이드 편집기, 비디오 도구, 오디오 스튜디오가 필요 없습니다.

설치: pip install deckrun-mcp

빠른 시작 — 설치 불필요

HTTP 전송 방식은 호스팅되어 바로 사용할 수 있습니다. IDE에 JSON 스니펫 하나만 추가하세요.

VS Code (GitHub Copilot Chat — v1.99 이상)

프로젝트의 .vscode/mcp.json (이 파일은 저장소에 포함되어 있습니다):

{
  "servers": {
    "deckrun": {
      "type": "http",
      "url": "https://deckrun-mcp-free.agenticdecks.com/mcp/"
    }
  }
}

Cursor

프로젝트의 .cursor/mcp.json:

{
  "mcpServers": {
    "deckrun": {
      "url": "https://deckrun-mcp-free.agenticdecks.com/mcp/"
    }
  }
}

Google Antigravity (Gemini CLI)

~/.gemini/antigravity/mcp_config.json:

{
  "mcpServers": {
    "deckrun": {
      "serverUrl": "https://deckrun-mcp-free.agenticdecks.com/mcp/"
    }
  }
}

Claude Code (터미널)

~/.claude/settings.json:

{
  "mcpServers": {
    "deckrun": {
      "type": "http",
      "url": "https://deckrun-mcp-free.agenticdecks.com/mcp/"
    }
  }
}

Related MCP server: mcp-ToseaAI

Stdio 설치 (Claude Desktop 및 기타 stdio 전용 클라이언트)

pip install deckrun-mcp

Claude Desktop — ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "deckrun": {
      "command": "python",
      "args": ["/path/to/deckrun_mcp.py"]
    }
  }
}

유료 티어 — API 키 추가:

{
  "mcpServers": {
    "deckrun": {
      "command": "python",
      "args": ["/path/to/deckrun_mcp.py"],
      "env": { "DECKRUN_API_KEY": "dk_live_..." }
    }
  }
}

구독 후 agenticdecks.com에서 API 키를 받으세요.

도구

무료 티어 (키 필요 없음)

도구

설명

get_slide_format

라이브 슬라이드 형식 사양(레이아웃 태그, 구문 규칙, 예제 Markdown) 가져오기

generate_slide_deck

Deckrun Markdown을 PDF로 변환. 공개 URL 반환 (90일 만료)

유료 티어 (DECKRUN_API_KEY 설정 시)

모든 무료 도구 포함:

도구

설명

generate_video

Markdown을 내레이션이 포함된 MP4로 변환 (비동기, job_id 반환)

generate_audio

슬라이드 노트를 MP3 내레이션으로 변환 (비동기, job_id 반환)

check_job

complete 또는 failed 상태가 될 때까지 비동기 작업 상태 폴링

get_account

플랜 이름, 사용/남은 렌더링 단위, 활성 애드온 확인

validate_markdown

Deckrun Markdown 린트 및 사전 비행 RU 추정치 확인

list_themes

사용 가능한 슬라이드/문서 테마 나열 (시스템 + 사용자 지정)

list_voices

사용 가능한 내레이션 음성 나열 — ID, 이름, 티어, 언어

예시 프롬프트

설정이 완료되면 AI에게 다음과 같이 요청하세요:

"엣지 컴퓨팅의 미래에 관한 6슬라이드 분량의 덱을 만들어줘"

AI는 get_slide_format을 호출하여 구문을 학습하고, Markdown을 작성한 뒤 generate_slide_deck을 호출하여 클릭 가능한 PDF 링크를 응답으로 제공합니다.

HTTP 엔드포인트

티어

MCP 엔드포인트

무료

https://deckrun-mcp-free.agenticdecks.com/mcp/

유료

https://deckrun-mcp.agenticdecks.com/mcp/

검색: GET <endpoint>는 서버 메타데이터를 JSON으로 반환합니다.

링크

Available Tools

2 tools
generate_slide_deckA

Convert Deckrun Markdown into a PDF slide deck. Call get_slide_format first to learn the correct Markdown format. Then call this tool with the completed Markdown. Returns: url (public PDF, 90-day expiry), slug, slides (count), warnings (non-fatal notices to self-correct), schema_version. Limits: max 10 slides, 50 KB Markdown. Slides separated by --- on its own line.

ParametersJSON Schema
NameRequiredDescriptionDefault
markdownYesComplete slide deck in Deckrun Markdown format. Must start with a title slide using <!-- <title-slide /> -->.

TDQS

A4.8/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses return values (url with expiry, slug, slides count, warnings, schema_version) and non-fatal notices. Could mention whether operation is destructive, but creation is implied.

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

Conciseness5/5

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

Concise, well-structured sentences. Front-loads main action, then details prerequisites, return fields, and limits. No wasted words.

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

Completeness5/5

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

Complete for a simple tool with one parameter and no output schema. Covers prerequisites, limits, return values, and warnings. No gaps.

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

Parameters5/5

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

Schema coverage 100% with one parameter. Description adds crucial formatting constraint (must start with title slide using specific comment) and reiterates limits beyond schema.

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

Purpose5/5

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

Clearly states it converts Deckrun Markdown into a PDF slide deck, distinct from sibling get_slide_format which teaches the format.

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

Usage Guidelines5/5

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

Explicitly instructs to call get_slide_format first, provides limits (max 10 slides, 50 KB), and explains return fields including warnings.

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

get_slide_formatA

Fetch the authoritative Deckrun slide format specification. Call this first to learn all layout tags, Markdown syntax, and rules before writing slides. Returns JSON with layout_tags, surface_syntax, example_markdown, and limits.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4.3/5.0
Behavior3/5

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

No annotations provided, so description must bear full burden. It states the tool returns JSON with specific fields, but does not explicitly declare it as read-only or side-effect-free, nor mention any auth or rate limits. The nature of the tool is apparent, but some behavioral detail is missing.

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

Conciseness5/5

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

Two sentences, front-loaded with action and purpose. Every sentence provides essential information with no redundancy or waste.

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

Completeness5/5

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

Given no output schema, the description fully specifies the return structure (layout_tags, surface_syntax, example_markdown, limits). This is complete for a simple format-fetching tool with zero parameters.

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

Parameters4/5

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

No parameters exist (0 params, 100% schema coverage). Baseline is 4. The description adds value by listing the return fields (layout_tags, surface_syntax, etc.), which helps the agent interpret the output beyond the empty schema.

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

Purpose5/5

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

The description clearly states the tool fetches the authoritative Deckrun slide format specification, with specific verb 'Fetch' and resource 'slide format specification'. It distinguishes from sibling 'generate_slide_deck' by indicating this is a preliminary step.

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

Usage Guidelines4/5

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

Explicitly says 'Call this first to learn... before writing slides', providing clear when to use. Does not explicitly state when not to use or mention alternatives aside from the implied sibling tool.

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. 2 tool updatesv1.1.1
    • First observedgenerate_slide_deck
    • First observedget_slide_format
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.4/5.0
Disambiguation5/5

The two tools have completely distinct purposes: one provides the format specification, the other generates the slide deck. No overlap in functionality.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern: 'generate_slide_deck' and 'get_slide_format'. Conventions are uniform.

Tool Count3/5

With only 2 tools, the server feels minimal. While it covers the core workflow (get format, generate), the count is low for a full-featured service, but not extreme.

Completeness3/5

The tool set covers the essential flow: fetch format then generate. However, it lacks tools for managing or revising decks, leaving notable gaps for repeated use.

Maintenance

ActivityInactive
ResponsivenessNo issues

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/agenticdecks/deckrun-mcp'

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