ShapeWords MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHAPEWORDS_API_KEY | No | Backward-compatible alias for SHAPEWORDS_RENDER_API_KEY. | |
| SHAPEWORDS_API_BASE_URL | No | ShapeWords app URL. | https://shapewords.fun |
| SHAPEWORDS_RENDER_API_KEY | No | Optional bearer token if your Render API requires one. | |
| SHAPEWORDS_MAX_IMAGE_BYTES | No | Max downloaded artifact size when returnImage is true. | 8388608 |
| SHAPEWORDS_POLL_TIMEOUT_MS | No | Render wait timeout. | 90000 |
| SHAPEWORDS_POLL_INTERVAL_MS | No | Polling interval for completed renders. | 1500 |
| SHAPEWORDS_REQUEST_TIMEOUT_MS | No | Per-request timeout for hosted API and artifact requests. | 30000 |
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 |
|---|---|
| render_word_cloudA | Create a ShapeWords word cloud, wait for completion, and return the artifact URL plus optional image content. |
| create_word_cloud_jobA | Start a ShapeWords render job and return status/artifact URLs without waiting for completion. |
| get_word_cloud_jobA | Check a ShapeWords render job status by ID. |
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 clearly distinct purpose: one performs the full operation synchronously, one initiates an async job, and one checks job status. No overlap or ambiguity exists.
Names follow verb_noun pattern and are readable, but 'render_word_cloud' vs 'create_word_cloud_job' uses different verbs for similar actions. Minor inconsistency, but 'job' suffix clarifies async nature.
3 tools is well-scoped for a job-based word cloud service: sync, async, and status check. Each tool earns its place without redundancy or bloat.
The surface covers the full workflow: create a job, check status, and get the result. No obvious missing operations for the stated domain.