Can I use Klipfolio as a CLI?

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

Can I expose Klipfolio through MCP?

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

Where are Klipfolio credentials stored?

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

Can I deny write access for Klipfolio MCP tools?

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

analytics

Klipfolio MCP Integration for CrewAI

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

7 functions 7 read 0 write Bearer token auth

Submit Klipfolio feedback View package source

Connect Klipfolio to CrewAI

Expose KosmoKrator integrations to CrewAI workers as scoped local tools.

Wrap kosmo integrations:call for specific tasks or connect workers to a local MCP gateway. The gateway is local, scoped to this integration, and starts with --write=deny so CrewAI can inspect read-capable tools without receiving write access by default.

Klipfolio MCP Config for CrewAI

Use per-worker integration scopes to avoid giving every worker every tool.

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

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

Klipfolio Tools Visible to CrewAI

CrewAI sees stable MCP tool names generated from the Klipfolio integration catalog.

MCP tool	Source function	Type	Description
`integration__klipfolio__klipfolio_list_dashboards`	`klipfolio.klipfolio_list_dashboards`	Read	List all dashboards accessible to the authenticated user in Klipfolio. Returns dashboard IDs, names, and metadata.
`integration__klipfolio__klipfolio_get_dashboard`	`klipfolio.klipfolio_get_dashboard`	Read	Get details for a specific Klipfolio dashboard by ID, including its layout, Klips, and sharing settings.
`integration__klipfolio__klipfolio_list_metrics`	`klipfolio.klipfolio_list_metrics`	Read	List all metrics accessible to the authenticated user in Klipfolio. Returns metric IDs, names, and associated data sources.
`integration__klipfolio__klipfolio_get_metric`	`klipfolio.klipfolio_get_metric`	Read	Get details for a specific Klipfolio metric by ID, including its formula, data bindings, and formatting.
`integration__klipfolio__klipfolio_list_datasources`	`klipfolio.klipfolio_list_datasources`	Read	List all data sources accessible to the authenticated user in Klipfolio. Returns data source IDs, names, and connector types.
`integration__klipfolio__klipfolio_get_datasource`	`klipfolio.klipfolio_get_datasource`	Read	Get details for a specific Klipfolio data source by ID, including its connector type, refresh settings, and configuration.
`integration__klipfolio__klipfolio_get_current_user`	`klipfolio.klipfolio_get_current_user`	Read	Get the authenticated Klipfolio user's profile information, including name, email, and role.

Related Klipfolio Pages

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