Poster MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POSTER_API_KEY | Yes | Required for business calls; without a key, only MCP discovery is available. Use your existing personal Poster key. Never pass it as tool input or a URL parameter. | |
| POSTER_API_URL | No | Optional HTTPS origin; defaults to https://poster.sh. HTTP is allowed only for local development on loopback. | https://poster.sh |
| POSTER_REQUEST_TIMEOUT_MS | No | Optional positive integer, default 15000. A timeout does not prove a submission failed. | 15000 |
| POSTER_MAX_CREDITS_PER_POSTER | No | Optional nonnegative integer. Omitted disables creation; quotes and existing results remain available. Zero permits only a genuinely zero-credit quote. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| quote_posterA | Read the actual price and supported selection from Poster, without generating or charging. Return an exact request to show the user and pass unchanged to create_poster after explicit approval. Models, sizes, availability and prices come from the API. |
| create_posterA | PAID ACTION: submit the exact quoted request only after the user approves its prompt, selection and quoted credits. Requires the operator-configured per-poster credit limit. Reuse the identical requestId and payload after uncertainty; never silently create a replacement task. A planning/generating response is pending, not a finished poster. |
| get_posterA | Read an existing owned poster and its current state. A ready response includes the actual previewUrl and document. Does not advance a task, create images or charge. Non-owned IDs remain refused by the existing API. |
| advance_posterA | MUTATING ACTION: continue an existing owned job only with explicit approval of that job and its original cost. The existing API may perform recovery attempts within that job budget, save results and settle its frozen approved price. This does not create a separate poster request. The new-creation credit cap does not reprice an accepted job. Use get_poster for read-only status. Do not replace a failed job automatically. |
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 occupies a distinct phase of the poster lifecycle: quote is read-only pricing, create is the paid submission, get is read-only status, and advance mutates an existing owned job. The descriptions explicitly clarify boundaries, especially quote vs. create and get vs. advance.
All four tools follow the same snake_case verb_noun pattern with a consistent noun: quote_poster, create_poster, get_poster, advance_poster. The verbs are distinct and predictable.
Four tools are well-scoped for a focused quote-create-read-advance workflow. There is no obvious bloat, and each tool has a clear role in the pipeline.
The core lifecycle is covered: quote a request, create after approval, read status, and advance an existing job. Minor gaps remain around listing owned posters, cancellation, or refund/delete paths, which agents may need in edge cases.