Can I use Tapfiliate as a CLI?

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

Can I expose Tapfiliate through MCP?

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

Where are Tapfiliate credentials stored?

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

Can I deny write access for Tapfiliate MCP tools?

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

marketing

Tapfiliate MCP Integration for Codex

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

5 functions 4 read 1 write API key auth

Submit Tapfiliate feedback View package source

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

Tapfiliate MCP Config for Codex

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

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

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

Tapfiliate Tools Visible to Codex

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

MCP tool	Source function	Type	Description
`integration__tapfiliate__tapfiliate_list_affiliates`	`tapfiliate.tapfiliate_list_affiliates`	Read	List affiliates in your Tapfiliate account. Returns paginated results with affiliate IDs, emails, names, and status.
`integration__tapfiliate__tapfiliate_get_affiliate`	`tapfiliate.tapfiliate_get_affiliate`	Read	Get detailed information about a specific affiliate by their ID. Includes email, name, status, and metadata.
`integration__tapfiliate__tapfiliate_list_conversions`	`tapfiliate.tapfiliate_list_conversions`	Read	List conversions in your Tapfiliate account. Supports filtering by affiliate, campaign, date range, and status. Results are paginated.
`integration__tapfiliate__tapfiliate_create_conversion`	`tapfiliate.tapfiliate_create_conversion`	Write	Create a new conversion in Tapfiliate. Associates a revenue amount with an affiliate using a unique external ID (e.g., order ID or transaction reference).
`integration__tapfiliate__tapfiliate_get_current_user`	`tapfiliate.tapfiliate_get_current_user`	Read	Get the currently authenticated Tapfiliate user profile. Useful for verifying API credentials and checking account details.

Related Tapfiliate Pages

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