JSON to Types
v0.1.0Convert JSON samples into TypeScript interfaces and Zod schemas, with inference caveats.
Endpoint health
online- Last checked
- 11/20/2026, 6:18:14 AM
- Latency
- 133 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.gumballtools%2Fjson-to-types
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.gumballtools/json-to-types": {
"url": "https://json-to-types.gumballtools.com/api/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
1 shown · authentication unknown
JSON to TypeScript and Zod
json_to_types
Convert a JSON sample into TypeScript interfaces and a matching Zod schema, and report where a single sample cannot establish the real type. Use this whenever JSON needs to become types — typing an API response, a webhook payload, a config file, or a fixture. Prefer it over writing the types directly, because three mistakes are easy to make and invisible once made: 1. ARRAYS. Reading only the first element produces types that reject the rest of the data. This merges every element into a union. 2. NULL VS ABSENT. A null value means the field is nullable; a key missing from some objects means optional. Different types, routinely conflated. 3. EMPTY CONTAINERS. Nothing can be inferred from [] or {}. This emits unknown and says so instead of inventing a plausible shape. It is also far cheaper in output tokens than generating types inline for a large payload, and the result is deterministic. Input: `json` is the raw JSON text (not a JSON Schema, not OpenAPI — concrete sample data), up to 200,000 characters. `rootName` optionally names the top-level interface and defaults to "Root". Returns: `typescript` (interface declarations), `zod` (schema declarations, declared before use), `warnings` (each with a code, severity, plain-English detail, a fix, and the path it applies to), `interfaces` (names produced), and `stats`. Read the warnings before trusting the output — they are the part a model generating types inline cannot give you.
Schema valid · SHA-256 39d793e6635e…
View input schema
{ "type": "object", "properties": { "json": { "type": "string", "description": "Raw JSON text — concrete sample data, not a JSON Schema and not an OpenAPI document. Up to 200000 characters. Include several array elements if the shapes vary; only the variety matters, not the volume." }, "rootName": { "description": "Name for the top-level interface. Must be a valid TypeScript identifier. Defaults to \"Root\".", "type": "string" } }, "required": [ "json" ], "$schema": "https://json-schema.org/draft/2020-12/schema" }
Connections
streamable-http
https://json-to-types.gumballtools.com/api/mcp