Can I use API Template IO as a CLI?

Yes. KosmoKrator exposes a API Template IO CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose API Template IO through MCP?

Yes. The KosmoKrator MCP gateway can expose selected API Template IO tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are API Template IO credentials stored?

API Template IO credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for API Template IO MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

documents

API Template IO MCP Integration for Codex

Connect API Template IO to Codex through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

5 functions 3 read 2 write API key auth

Submit API Template IO feedback View package source

Connect API Template IO to Codex

Use KosmoKrator as a local MCP proxy for Codex so coding sessions can reach selected integrations with explicit write policy.

Register kosmo mcp:serve as a local stdio server and choose the integration allowlist. The gateway is local, scoped to this integration, and starts with --write=deny so Codex can inspect read-capable tools without receiving write access by default.

API Template IO MCP Config for Codex

Keep write access denied or ask-based unless the workspace is trusted.

{
  "mcpServers": {
    "kosmokrator-apitemplateio": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=apitemplateio",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=apitemplateio --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only API Template IO instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

API Template IO Tools Visible to Codex

Codex sees stable MCP tool names generated from the API Template IO integration catalog.

MCP tool	Source function	Type	Description
`integration__apitemplateio__apitemplateio_create_pdf`	`apitemplateio.apitemplateio_create_pdf`	Write	Generate a PDF document from an API Template IO template. Provide a template ID and the data to merge into the template.
`integration__apitemplateio__apitemplateio_create_image`	`apitemplateio.apitemplateio_create_image`	Write	Generate an image (PNG or JPEG) from an API Template IO template. Provide a template ID, data, and the desired output format.
`integration__apitemplateio__apitemplateio_list_templates`	`apitemplateio.apitemplateio_list_templates`	Read	List available templates in API Template IO. Returns a paginated list of template IDs, names, and metadata.
`integration__apitemplateio__apitemplateio_get_template`	`apitemplateio.apitemplateio_get_template`	Read	Get details for a specific API Template IO template by ID. Returns the template definition, schema, and configuration.
`integration__apitemplateio__apitemplateio_get_current_user`	`apitemplateio.apitemplateio_get_current_user`	Read	Get the current authenticated user's account information from API Template IO, including usage and subscription details.

Related API Template IO Pages

API Template IO CLIUse direct JSON commands instead of MCP discovery. API Template IO MCPFull gateway reference and MCP tool names. KosmoKrator for CodexClient-level gateway setup.