markovo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MARKOVO_API_KEY | Yes | API key for Markovo, created in the Developer portal. This is required for authentication. | |
| MARKOVO_MCP_ROOT | Yes | The dedicated project directory that the MCP server is allowed to read and write. If missing, the server refuses all file tools. |
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 |
|---|---|
| markovo_convertC | Convert a supported file through the account-metered Markovo API. |
| markovo_convert_urlB | Convert one public HTTPS page after explicit consent to Markovo's isolated remote fetch. |
| markovo_job_statusC | Fetch a remote job. |
| markovo_job_assetsB | List manifest-verified image assets for a completed job. |
| markovo_asset_urlB | Create a revocable 60-600 second bearer URL for one Bundle image. |
| markovo_asset_revokeC | Revoke a temporary asset URL before it expires. |
| markovo_usageB | Fetch account Credit usage. |
| markovo_capabilitiesC | Fetch the live capability registry. |
| markovo_billingB | Return the secure billing URL. |
| markovo_bundle_verifyC | Verify a downloaded Markovo bundle. |
| markovo_doctorB | Check client, service, and API-key readiness. |
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 11 tools
Each tool targets a distinct action or resource within the conversion/asset lifecycle (file vs URL conversion, job status vs assets, asset URL creation vs revocation, usage/billing/capabilities/readiness). Overlaps are minimal and descriptions clearly differentiate the few related pairs.
All tool names use the same markovo_ prefix and snake_case convention, making them predictable. A few names are noun-only (usage, billing, capabilities, doctor) rather than verb_noun, which is a minor deviation from a strict action pattern.
Eleven tools is well-scoped for a conversion and asset-delivery service. Each tool appears to earn its place, covering submission, job inspection, asset access, verification, and account diagnostics without obvious redundancy.
The surface covers the core lifecycle: conversion, job status, asset listing, asset URL creation/revocation, bundle verification, and account/diagnostic checks. Minor gaps exist around job cancellation/listing or direct bundle download/cleanup, but agents can likely work around them.