Jsoncut MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JSONCUT_API_KEY | Yes | Your Jsoncut API key from jsoncut.com |
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
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_image_configA | Create a JSON configuration for image generation based on jsoncut documentation. Returns a complete configuration object that can be used with the validate_config tool or submitted directly to the jsoncut API. WORKFLOW:
Image Structure:
Layer Types:
Positioning Options:
Visual Effects:
Text Features:
Output Formats:
Defaults System:
File paths should be placeholders like "/image/2024-01-15/userXXX/filename.ext" or "/font/2024-01-15/userXXX/font.ttf". |
| create_video_configA | Create a JSON configuration for video generation based on jsoncut documentation. Returns a complete configuration object that can be used with the validate_config tool or submitted directly to the jsoncut API. WORKFLOW:
Video Structure:
Layer Types:
Audio Options:
Video & title layer Positioning:
Title Layer Animation Styles:
Transitions: 75+ transition effects including fade, wipe, circle, cube, glitch, zoom, etc. File paths should be placeholders like "/input/userXXX/filename.ext". |
| validate_configA | Validate a job configuration against the jsoncut API. This tool sends the configuration to the API's validation endpoint to check:
WHEN TO USE:
BENEFITS:
|
| get_image_schemaA | Get the complete JSON schema for image generation. Returns the full JSON Schema document that defines all possible configuration options for image generation jobs. Use this to understand all available options, constraints, and examples. NOTE: This schema is also available as a resource at schema://image which can be read directly without a tool call. IMPORTANT: Get this schema FIRST when creating image configurations to understand the complete structure, available layer types, positioning options, and all properties. This ensures you create valid and complete configurations. |
| get_video_schemaA | Get the complete JSON schema for video generation. Returns the full JSON Schema document that defines all possible configuration options for video generation jobs. Use this to understand all available options, constraints, and examples. NOTE: This schema is also available as a resource at schema://video which can be read directly without a tool call. IMPORTANT: Get this schema FIRST when creating video configurations to understand the complete structure, available layer types, audio options, transitions, and all properties. This ensures you create valid and complete configurations. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Image Generation Schema | Complete JSON schema for image generation configurations |
| Video Generation Schema | Complete JSON schema for video generation configurations |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: two for image config/schema, two for video config/schema, and one for validation. No overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case (create_, get_, validate_), with parallelism between image and video tools.
5 tools is well-scoped for the server's purpose of handling image and video configuration creation, schema retrieval, and validation. No extraneous tools.
Core workflow is covered: schema retrieval, config creation, and validation. Minor gaps include lack of a tool to submit jobs or manage existing configs, but these may be out of scope.