JSON sample to TypeScript: setup, supported tools and cost

What you can do

Infer TypeScript interfaces from a small inline JSON sample on TaskVegas. No local installation or provider key required; sample inference is not schema validation.

• taskvegas_generate_types — reads information

Infer an API response interface

Illustrative prompt: Call taskvegas_generate_types with json set to {"id":1,"name":"Example","active":true} and typeName set to Account. The json argument is a string containing that sample.

Verification: Check that id is a number, name is a string and active is a boolean. Compare optional fields and unions with additional real cases; one sample does not define a complete API contract. Generated declarations are returned as text, never executed.

Setup and execution

Execution

On the TaskVegas server

Requirements

No provider key required. Workspace activation and OAuth permission are still required.

Who pays

Free within the existing gateway limits; your AI host may have its own charges.

Create or recover a workspace, save the required connection, test it, enable the module, then approve the exact tools in your OAuth-capable MCP client. Searching the catalog grants no execution permission.

Permissions and boundaries

• Read only the supplied inline JSON sample
• Return advisory TypeScript declarations

Free within shared hosted quotas. 24 KiB encoded input, 64 KiB result, five-second deadline and worker V8 limits; not an OS sandbox. No executable configuration, remote schema references, file discovery or generated-code execution.

Only the named typed operations are available. Responses may be truncated; check returned identifiers, source links and error details before acting. Existing quotas and the operator pause switch apply. There is no owner-paid fallback.

Source and review evidence

Adapter version

quicktype-core-24.0.0

Reviewed

2026-10-23 · TaskVegas pinned dependency and bounded-adapter review

Contract evidence

local-tested

MCP client evidence

verified; account evidence: not-required

Reviewed revision

npm:quicktype-core@24.0.0;git:9b81813064895d8c3d3f4d591db7547915b116d3

Implementation

server/gateway/type-tools.js

Real REST and Node MCP SDK sample inference, unsafe-input denial and exact authority checks passed on 9b69287fb5f16aa3cbe7aec4553e7543f694741e. Distinct-repository qualification and named AI-host verification remain separate; no provider/model call was made.

Apache-2.0; pinned root and 26 dependency-location notices retained in vendor/quicktype. See integrity.json for exact versions and notice hashes.

Next steps

• Connect an OAuth-capable MCP client
• Understand costs and quotas
• Read compatibility evidence
• Open your workspace