Can I use Immigrant as a CLI?

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

Can I expose Immigrant through MCP?

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

Where are Immigrant credentials stored?

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

Can I deny write access for Immigrant MCP tools?

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

productivity

Immigrant MCP Integration for Codex

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

7 functions 6 read 1 write Bearer token auth

Submit Immigrant feedback View package source

Connect Immigrant 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.

Immigrant MCP Config for Codex

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

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

Expose only Immigrant 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.

Immigrant Tools Visible to Codex

Codex sees stable MCP tool names generated from the Immigrant integration catalog.

MCP tool	Source function	Type	Description
`integration__immigrant__immigrant_list_applications`	`immigrant.immigrant_list_applications`	Read	List immigration applications. Returns a paginated list of applications, optionally filtered by status.
`integration__immigrant__immigrant_get_application`	`immigrant.immigrant_get_application`	Read	Get details of a specific immigration application by its ID.
`integration__immigrant__immigrant_create_application`	`immigrant.immigrant_create_application`	Write	Create a new immigration application. Requires a type and applicant name. Optionally provide additional details.
`integration__immigrant__immigrant_list_documents`	`immigrant.immigrant_list_documents`	Read	List documents for a specific immigration application. Returns a paginated list of documents.
`integration__immigrant__immigrant_get_document`	`immigrant.immigrant_get_document`	Read	Get details of a specific document by its ID.
`integration__immigrant__immigrant_list_statuses`	`immigrant.immigrant_list_statuses`	Read	List all available immigration application statuses. Use this to understand valid status values for filtering.
`integration__immigrant__immigrant_get_current_user`	`immigrant.immigrant_get_current_user`	Read	Get the profile of the currently authenticated Immigrant user. Use this to verify credentials and see user details.

Related Immigrant Pages

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