@cyanheads/docgen-mcp-server
by cyanheads
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OTEL_ENABLED | No | Enable OpenTelemetry instrumentation (spans, metrics, completion logs). | false |
| MCP_AUTH_MODE | No | Auth mode: none, jwt, or oauth. | none |
| MCP_HTTP_PORT | No | Port for the HTTP server. | 3010 |
| MCP_LOG_LEVEL | No | Log level (RFC 5424). | info |
| MCP_PUBLIC_URL | No | Public origin behind a TLS proxy. (The downloadUrl envelope field is reserved for a future HTTP download route and is not emitted in this version.) | |
| DOCGEN_PDF_ENGINE | No | PDF rendering engine. Only lightweight is implemented; chromium is reserved and rejected at startup. | lightweight |
| MCP_TRANSPORT_TYPE | No | Transport: stdio or http. | stdio |
| STORAGE_PROVIDER_TYPE | No | Storage backend for document bytes + metadata. | in-memory |
| DOCGEN_INLINE_MAX_BYTES | No | Artifacts at or under this byte size are returned inline as base64; larger ones omit it. | 5242880 |
| DOCGEN_RENDER_TIMEOUT_MS | No | Per-render wall-clock budget in milliseconds; exceeding it aborts the render. | 30000 |
| DOCGEN_MAX_DOCUMENT_BYTES | No | Hard ceiling on a single rendered artifact in bytes; exceeding it aborts the render. | 26214400 |
| DOCGEN_DOCUMENT_TTL_SECONDS | No | How long a rendered document is retrievable before it expires, in seconds. | 900 |
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
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/cyanheads/docgen-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server