Suprasūtā Markdown Notes
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEMINI_API_KEY | No | Optional: enables cloud OCR, which can also describe charts and diagrams. The image is sent to Google. | |
| ASSEMBLYAI_API_KEY | No | Optional: enables audio transcription. The audio file is sent to AssemblyAI. | |
| MARKDOWN_MCP_ROOTS | No | Optional: limits which folders the server is allowed to read. Without it, any path the assistant asks for is allowed. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert_to_markdownA | Convert a document on this machine to clean Markdown. Handles PDF, Word (.docx), Excel (.xlsx/.xls/.xlsm), PowerPoint (.pptx), OpenDocument text and spreadsheets (.odt/.ods), EPUB, CSV/TSV and plain text. Images are read with OCR, and audio is transcribed. Conversion happens locally and the file is not uploaded, except for the image and audio cases noted in ocr_mode. Prefer this over reading a binary file directly. The Markdown is SAVED AUTOMATICALLY as a .md file beside the original, so the user does not need to ask. Short documents are also returned in full; long ones come back as a preview plus the saved path, to avoid filling the conversation with tens of thousands of words. If you need more of a long document than the preview shows, call this again with return_content "full". |
| convert_folder_to_markdownA | Convert several documents at once and return a summary of what succeeded. Use when the user points at a set of files rather than one. |
| save_summaryA | Save a summary you have written about a document, as a .md file beside it. Call this WITHOUT being asked whenever you summarise, outline or answer a broad question about a document you converted — the user wants the summary kept, not just shown once in the chat. Do not call it for narrow factual lookups, and never invent a summary in order to save one: pass the text you actually produced. |
| list_supported_formatsA | List the file extensions this server can convert, and report which optional cloud features are configured. Call this if a conversion fails as unsupported. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: convert one document, convert a folder, save a summary, and list supported formats. The only similar pair (single vs. folder conversion) is well differentiated by cardinality, and save_summary is explicitly limited to agent-written summaries rather than document conversion.
All tool names are lowercase snake_case and begin with imperative verbs, making the set predictable. There is a minor stylistic split between the convert_*_to_markdown pattern and plain verb_noun names like save_summary and list_supported_formats, but the overall convention is coherent.
Four tools is ideal for this narrow server: single-file conversion, batch conversion, summary persistence, and format discovery. Each tool earns its place and there is no redundancy.
The conversion workflow is fully covered: agents can convert one file or many, get content back, and handle unsupported formats. The notes side is thinner since save_summary only creates summaries with no server-side way to read, update, or delete them, but this is workable because summaries are saved as .md files on disk.