mcp-thumbapi
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_thumbnailA | Generate a thumbnail / social share image from a title using the ThumbAPI service. Use this when the user wants to create a YouTube thumbnail, Instagram post image, X/Twitter card, LinkedIn share image, or blog post hero image from a headline or title. Returns the generated image inline (viewable by the model) plus metadata: format, outputFormat, generationId, and imageUrl (a public URL on ThumbAPI's CDN — use this to download or embed the image without handling base64). Requires an API key. Either set THUMBAPI_API_KEY in the environment or run the |
| loginA | Sign the MCP server in to ThumbAPI. Opens a browser to app.thumbapi.dev/mcp-login, asks the user to consent, and saves the returned API key to ~/.thumbapi/config.json. Call this tool when:
The tool blocks up to ~30s per invocation waiting for the browser callback. If the user hasn't consented yet, it returns "still waiting" — just call login again to keep waiting. The underlying local callback server stays alive across calls for up to 15 minutes. |
| logoutA | Remove the saved ThumbAPI API key from ~/.thumbapi/config.json. Does not revoke the key on the server — that's a separate action from the dashboard. |
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 3 tools
Each tool has a distinct purpose: generate_thumbnail for the core task, login for authentication, and logout for de-authentication. There is no functional overlap, so an agent can easily select the right tool.
All tool names are lowercase with underscores, but the pattern is mixed: generate_thumbnail follows verb_noun, while login and logout are simple verbs. This is a minor deviation and the names are still intuitive.
With 3 tools, the server is well-scoped for its purpose: one core operation plus necessary authentication lifecycle. This is a reasonable size and each tool serves a clear function.
The tool surface covers the full workflow: authenticate (login), generate thumbnail (generate_thumbnail), and de-authenticate (logout). No obvious missing operations for the stated domain of ThumbAPI.