Can I use Later as a CLI?

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

Can I expose Later through MCP?

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

Where are Later credentials stored?

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

Can I deny write access for Later MCP tools?

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

marketing

Later MCP Integration for Claude Code

Connect Later to Claude Code through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 6 read 1 write Manual OAuth token auth

Submit Later feedback View package source

Connect Later to Claude Code

Connect local KosmoKrator integrations to Claude Code through one scoped MCP gateway entry.

Add KosmoKrator as a stdio MCP server in the Claude Code project config and select the integrations that should be visible. The gateway is local, scoped to this integration, and starts with --write=deny so Claude Code can inspect read-capable tools without receiving write access by default.

Later MCP Config for Claude Code

Claude Code can launch the local kosmo binary directly from the project MCP config.

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

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

Later Tools Visible to Claude Code

Claude Code sees stable MCP tool names generated from the Later integration catalog.

MCP tool	Source function	Type	Description
`integration__later__later_list_profiles`	`later.later_list_profiles`	Read	List all social media profiles connected to the Later account. Returns profile IDs, platform types, and display names.
`integration__later__later_get_profile`	`later.later_get_profile`	Read	Get details of a specific social media profile in Later by its ID. Returns profile platform type, display name, and account metadata.
`integration__later__later_list_posts`	`later.later_list_posts`	Read	List scheduled and published posts in Later. Optionally filter by profile ID, status (scheduled, published, draft), and paginate results.
`integration__later__later_create_post`	`later.later_create_post`	Write	Create and schedule a new social media post in Later. Provide the caption text, target profile IDs, and optionally a scheduled time or media URL.
`integration__later__later_list_media`	`later.later_list_media`	Read	List media items in the Later media library. Returns media IDs, URLs, types, and metadata. Optionally filter by media type.
`integration__later__later_get_media`	`later.later_get_media`	Read	Get details of a specific media item in Later by its ID. Returns the media URL, type, dimensions, and metadata.
`integration__later__later_get_current_user`	`later.later_get_current_user`	Read	Get the currently authenticated Later user profile. Returns the user name, email, and account info.

Related Later Pages

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