oJo MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OJO_API_KEY | No | Optional oJo API key. Without it the server runs in preview-only mode; with it the full tool surface is registered. | |
| OJO_API_BASE_URL | No | Optional. Defaults to https://api.ojo.so/v1. | |
| OJO_WEB_BASE_URL | No | Optional. The web app that serves /preview for create_preview_link. Defaults to https://ojo.so. |
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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_preview_linkA | Render HTML/Handlebars into a live, full-resolution image preview — free, unlimited, and with no oJo account. Returns an oJo |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| author_ojo_template | Guidance for writing oJo templates: the Handlebars helper catalog, Template Variables vs Modify Payload, viewport conventions, and the inspect→iterate loop. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of confusion or overlap. The tool's purpose is clearly defined and distinct.
The tool name 'create_preview_link' follows a clear verb_noun pattern. With only one tool, there are no inconsistencies to evaluate.
One tool is too few for the apparent scope of an oJo integration, especially as the description references additional features (permanent PNG, template saving) that are unavailable. The toolset feels thin and limited.
The tool covers live preview creation, but lacks operations for permanent image generation and template management, which are part of the broader oJo domain. These gaps require agents to work around missing functionality.