Skip to main content
Glama
quantalogic

SafeMarkdownEditor MCP Server

by quantalogic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
load_documentB
        Load and analyze a Markdown document from a file path.
        
        Args:
            document_path: Path to the Markdown file (supports absolute, relative, and ~ expansion)
            validation_level: Validation strictness - "STRICT", "NORMAL", or "PERMISSIVE"
insert_sectionC
        Insert a new section at a specified location.
        The document will be saved after the operation if successful and auto_save is True.
delete_sectionC
        Delete a section by ID or heading.
        The document will be saved after the operation if successful and auto_save is True.
update_sectionC
        Update the content of an existing section.
        The document will be saved after the operation if successful and auto_save is True.
get_sectionB
        Get a specific section by ID.
        
        Args:
            document_path: Path to the Markdown file
            section_id: The section ID to retrieve
            validation_level: Validation strictness - "STRICT", "NORMAL", or "PERMISSIVE"
list_sectionsC
        List all sections in the document.
        
        Args:
            document_path: Path to the Markdown file
            validation_level: Validation strictness - "STRICT", "NORMAL", or "PERMISSIVE"
move_sectionC
        Move a section to a different position.
        The document will be saved after the operation if successful and auto_save is True.
get_documentB
        Get the complete document content and structure.
        
        Args:
            document_path: Path to the Markdown file
            validation_level: Validation strictness - "STRICT", "NORMAL", or "PERMISSIVE"
save_documentA
        Save the document (mainly for validation purposes since auto_save handles most cases).
        
        Args:
            document_path: Path to the source Markdown file
            target_path: Path to save to (if different from source)
            backup: Whether to create a backup before saving
            validation_level: Validation strictness - "STRICT", "NORMAL", or "PERMISSIVE"
analyze_documentC
        Analyze document structure and provide insights.
        
        Args:
            document_path: Path to the Markdown file
            validation_level: Validation strictness - "STRICT", "NORMAL", or "PERMISSIVE"

Prompts

Interactive templates invoked by user choice

NameDescription
document_editing_guideGuide for using the stateless document editing tools.
section_operations_examplesExamples of common section operations.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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

A3.5/5.0

Scored across 10 tools

Disambiguation4/5

Most tools have distinct purposes targeting different document operations, but there is some overlap between get_document and load_document where both retrieve document content. The descriptions clarify that load_document includes analysis while get_document focuses on content/structure, but an agent might initially confuse them.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with snake_case naming (e.g., analyze_document, delete_section, get_document). The verbs are clear and appropriate for the actions, making the tool set predictable and readable.

Tool Count5/5

With 10 tools, this is well-scoped for a Markdown editor server, covering core operations like loading, analyzing, reading, writing, and manipulating sections. Each tool has a clear role without unnecessary duplication, fitting typical server sizes.

Completeness5/5

The tool set provides comprehensive coverage for document management, including CRUD operations for sections (list, get, insert, update, delete, move) and full document handling (load, get, analyze, save). There are no obvious gaps for the domain of editing and analyzing Markdown files.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources