PromptReady MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| loginB | Open the browser Google login page and save tokens for this machine. Starts a local callback on http://127.0.0.1:18765/callback, opens PromptReady Google OAuth, stores credentials under ~/.config/promptready/credentials.json (mode 600), and applies them to this process. Users should run this once (or use CLI: promptready-mcp-login) instead of pasting tokens manually. Requires Supabase redirect allowlist for that URL. |
| logoutA | Remove saved MCP credentials from this machine and clear env tokens. |
| get_creditsA | Get the calling user's PromptReady credit balance. Returns JSON: ok + credit_balance + email, or ok:false + error. Requires prior login (promptready-mcp-login / login tool) or env token. |
| get_convert_settingsA | Show saved convert defaults for this machine (not per-file options). Defaults live in ~/.config/promptready/settings.json. convert_pdf always uses these until you change them with set_convert_settings. |
| set_convert_settingsA | Update saved convert defaults (persists for future convert_pdf calls). Only pass fields you want to change. Example: set engine to paddle_vl15 once, then every convert uses that until changed again. Args: engine: paddle | paddle_vl15 | glm_ocr include_tables: keep markdown tables include_images: include image/visual extraction (heavier) remove_references: strip references section when supported |
| convert_pdfA | Upload a local PDF/CSV and queue conversion (same credits as the web app). Uses saved user settings (get_convert_settings / set_convert_settings), not per-call engine flags. Factory default: paddle, tables on, images off. Args: path: Absolute or home-relative path to a .pdf or .csv file. wait: If true, poll until done and download markdown (can take many minutes). timeout_sec: Max wait when wait=true (default 3600). output_dir: Directory for downloaded .md when wait=true. Returns JSON with job info; if wait=true and completed, includes local md path. |
| get_statusA | Get conversion status for the authenticated user's current session job. Uses GET /api/v1/convert/status (session = user_id when logged in). |
| wait_and_downloadA | Poll get_status until completed/failed/cancelled, then download markdown if available. Args: timeout_sec: Max seconds to wait (OCR can take many minutes). poll_interval_sec: Sleep between polls (default 3). output_dir: Where to write the .md file. source_path: Optional original file path (used only for output filename). |
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 8 tools
Tools have distinct purposes: auth, settings, conversion, status, download. However, convert_pdf with wait=true and wait_and_download both handle waiting and downloading, which could cause slight confusion, but descriptions clarify their different roles.
All names use snake_case, but inconsistent patterns: some are verb_noun (convert_pdf, get_credits), others are bare verbs (login, logout), and wait_and_download uses 'and'. Minor deviations from a strict verb_noun pattern.
8 tools feel appropriate for a PDF conversion service, covering auth, settings, conversion, and status. Not excessive nor too sparse, though a few additional tools (e.g., list conversions) could be added.
The tool set covers the essential lifecycle: auth, configuration, conversion, status polling, and download. Minor gaps like listing past conversions or deleting jobs exist, but core workflow is complete.