Can I use AddEvent as a CLI?

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

Can I expose AddEvent through MCP?

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

Where are AddEvent credentials stored?

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

Can I deny write access for AddEvent MCP tools?

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

productivity

AddEvent CLI for AI Agents

Use the AddEvent CLI from KosmoKrator to call AddEvent tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

AddEvent CLI Setup

AddEvent can be configured headlessly with `kosmokrator integrations:configure addevent`.

Install, configure, and verify

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure addevent --set access_token="$ADDEVENT_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmokrator integrations:doctor addevent --json
kosmokrator integrations:status --json

Credentials

Authentication type: Bearer token bearer_token. Configure credentials once, then reuse the same stored profile from scripts, coding CLIs, Lua, and MCP.

Key	Env var	Type	Required	Label
`access_token`	`ADDEVENT_ACCESS_TOKEN`	Secret `secret`	yes	API Key
`url`	`ADDEVENT_URL`	URL `url`	no	API Base URL

Command Patterns

The generic command is stable across every integration. The provider shortcut is shorter for humans.

Generic CLI call

kosmo integrations:call addevent.addevent_list_events '{"page":1,"page_size":1,"calendar_id":"example_calendar_id","sort_by":"example_sort_by","sort_order":"example_sort_order"}' --json

Provider shortcut

kosmo integrations:addevent addevent_list_events '{"page":1,"page_size":1,"calendar_id":"example_calendar_id","sort_by":"example_sort_by","sort_order":"example_sort_order"}' --json

Discovery

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

Discovery commands

kosmo integrations:docs addevent --json
kosmo integrations:docs addevent.addevent_list_events --json
kosmo integrations:schema addevent.addevent_list_events --json
kosmo integrations:search "AddEvent" --json
kosmo integrations:list --json

Automation Contexts

The same configured command surface works in these environments. The command does not change unless the host wrapper, credentials, or permissions change.

CI Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status. Cron Jobs Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config. Shell Scripts Call integration functions from shell scripts with stable JSON input and output. Headless Automation Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers. Coding Agents Let coding agents discover schemas and execute integration functions through CLI commands or MCP.

CLI Functions

Every function below can be called headlessly. Commands are highlighted, copyable, and scroll horizontally when payloads are long.

`addevent.addevent_list_events`

Search calendar events from AddEvent. Supports page, page_size, calendar_id, sort_by, and sort_order parameters.

Read read

Parameters: page, page_size, calendar_id, sort_by, sort_order

Generic call

kosmo integrations:call addevent.addevent_list_events '{"page":1,"page_size":1,"calendar_id":"example_calendar_id","sort_by":"example_sort_by","sort_order":"example_sort_order"}' --json

Shortcut

kosmo integrations:addevent addevent_list_events '{"page":1,"page_size":1,"calendar_id":"example_calendar_id","sort_by":"example_sort_by","sort_order":"example_sort_order"}' --json

`addevent.addevent_get_event`

Get details for a specific AddEvent calendar event by ID.

Read read

Parameters: id

Generic call

kosmo integrations:call addevent.addevent_get_event '{"id":"example_id"}' --json

Shortcut

kosmo integrations:addevent addevent_get_event '{"id":"example_id"}' --json

`addevent.addevent_create_event`

Create a new calendar event in AddEvent. Requires title and datetime_start. Optionally set calendar_id, datetime_end, timezone, location, description, RSVP, color, and custom data.

Write write

Parameters: title, datetime_start, datetime_end, calendar_id, timezone, all_day_event, location, description, organizer_name, organizer_email, color, rsvp_enabled, custom_data

Generic call

kosmo integrations:call addevent.addevent_create_event '{"title":"example_title","datetime_start":"example_datetime_start","datetime_end":"example_datetime_end","calendar_id":"example_calendar_id","timezone":"example_timezone","all_day_event":true,"location":"example_location","description":"example_description"}' --json

Shortcut

kosmo integrations:addevent addevent_create_event '{"title":"example_title","datetime_start":"example_datetime_start","datetime_end":"example_datetime_end","calendar_id":"example_calendar_id","timezone":"example_timezone","all_day_event":true,"location":"example_location","description":"example_description"}' --json

`addevent.addevent_update_event`

Update an existing AddEvent event. Only fields provided in attributes are changed.

Write write

Parameters: id, attributes

Generic call

kosmo integrations:call addevent.addevent_update_event '{"id":"example_id","attributes":"example_attributes"}' --json

Shortcut

kosmo integrations:addevent addevent_update_event '{"id":"example_id","attributes":"example_attributes"}' --json

`addevent.addevent_delete_event`

Delete an AddEvent event by ID. This action is permanent.

Write write

Parameters: id

Generic call

kosmo integrations:call addevent.addevent_delete_event '{"id":"example_id"}' --json

Shortcut

kosmo integrations:addevent addevent_delete_event '{"id":"example_id"}' --json

`addevent.addevent_list_calendars`

Search AddEvent calendars. Supports page, page_size, calendar_ids, sort_by, and sort_order.

Read read

Parameters: page, page_size, calendar_ids, sort_by, sort_order

Generic call

kosmo integrations:call addevent.addevent_list_calendars '{"page":1,"page_size":1,"calendar_ids":"example_calendar_ids","sort_by":"example_sort_by","sort_order":"example_sort_order"}' --json

Shortcut

kosmo integrations:addevent addevent_list_calendars '{"page":1,"page_size":1,"calendar_ids":"example_calendar_ids","sort_by":"example_sort_by","sort_order":"example_sort_order"}' --json

`addevent.addevent_get_calendar`

Retrieve an AddEvent calendar by ID.

Read read

Parameters: id

Generic call

kosmo integrations:call addevent.addevent_get_calendar '{"id":"example_id"}' --json

Shortcut

kosmo integrations:addevent addevent_get_calendar '{"id":"example_id"}' --json

`addevent.addevent_create_calendar`

Create a new AddEvent calendar. Requires title; optional fields include timezone, weekday_begin, description, internal_name, calendar_color, and custom_data.

Write write

Parameters: title, timezone, weekday_begin, description, internal_name, calendar_color, custom_data

Generic call

kosmo integrations:call addevent.addevent_create_calendar '{"title":"example_title","timezone":"example_timezone","weekday_begin":"example_weekday_begin","description":"example_description","internal_name":"example_internal_name","calendar_color":1,"custom_data":"example_custom_data"}' --json

Shortcut

kosmo integrations:addevent addevent_create_calendar '{"title":"example_title","timezone":"example_timezone","weekday_begin":"example_weekday_begin","description":"example_description","internal_name":"example_internal_name","calendar_color":1,"custom_data":"example_custom_data"}' --json

`addevent.addevent_list_timezones`

List timezones supported by the AddEvent Calendar and Events API.

Read read

Parameters: none

Generic call

kosmo integrations:call addevent.addevent_list_timezones '{}' --json

Shortcut

kosmo integrations:addevent addevent_list_timezones '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

addevent.addevent_list_events 5 parameters

Schema command

kosmo integrations:schema addevent.addevent_list_events --json

Parameter	Type	Required	Description
`page`	integer	no	Page number for pagination (default: 1).
`page_size`	integer	no	Number of events per page (default: 10, max: 20).
`calendar_id`	string	no	Filter events by calendar ID.
`sort_by`	string	no	Sort field supported by AddEvent.
`sort_order`	string	no	Sort direction.

addevent.addevent_get_event 1 parameters

Schema command

kosmo integrations:schema addevent.addevent_get_event --json

Parameter	Type	Required	Description
`id`	string	yes	The AddEvent event ID.

addevent.addevent_create_event 13 parameters

Schema command

kosmo integrations:schema addevent.addevent_create_event --json

Parameter	Type	Required	Description
`title`	string	yes	Event title.
`datetime_start`	string	yes	Event start date/time, e.g. "2026-04-10 09:00:00".
`datetime_end`	string	no	Event end date/time. Defaults to one hour after datetime_start when omitted by AddEvent.
`calendar_id`	string	no	Calendar ID. Defaults to the account default calendar when omitted.
`timezone`	string	no	Event timezone, e.g. "America/New_York" or "floating".
`all_day_event`	boolean	no	Whether this is an all-day event.
`location`	string	no	Event location or meeting URL.
`description`	string	no	Event description. Plain text and simplified HTML are supported by AddEvent.
`organizer_name`	string	no	Organizer name. Requires organizer_email when provided.
`organizer_email`	string	no	Organizer email. Requires organizer_name when provided.
`color`	integer	no	Event color ID from 1 to 20.
`rsvp_enabled`	boolean	no	Whether RSVP is enabled for the event.
`custom_data`	object	no	Custom key/value data to attach to the event.

addevent.addevent_update_event 2 parameters

Schema command

kosmo integrations:schema addevent.addevent_update_event --json

Parameter	Type	Required	Description
`id`	string	yes	The AddEvent event ID.
`attributes`	object	yes	Event fields to update, using AddEvent v2 field names.

addevent.addevent_delete_event 1 parameters

Schema command

kosmo integrations:schema addevent.addevent_delete_event --json

Parameter	Type	Required	Description
`id`	string	yes	The AddEvent event ID.

addevent.addevent_list_calendars 5 parameters

Schema command

kosmo integrations:schema addevent.addevent_list_calendars --json

Parameter	Type	Required	Description
`page`	integer	no	Page number for pagination (default: 1).
`page_size`	integer	no	Number of calendars per page (default: 10, max: 20).
`calendar_ids`	array	no	Optional calendar IDs to filter by.
`sort_by`	string	no	Sort field.
`sort_order`	string	no	Sort direction.

addevent.addevent_get_calendar 1 parameters

Schema command

kosmo integrations:schema addevent.addevent_get_calendar --json

Parameter	Type	Required	Description
`id`	string	yes	The AddEvent calendar ID.

addevent.addevent_create_calendar 7 parameters

Schema command

kosmo integrations:schema addevent.addevent_create_calendar --json

Parameter	Type	Required	Description
`title`	string	yes	Calendar title.
`timezone`	string	no	Default calendar timezone.
`weekday_begin`	string	no	Calendar week start day.
`description`	string	no	Calendar description.
`internal_name`	string	no	Internal calendar name.
`calendar_color`	integer	no	Calendar color ID from 1 to 20.
`custom_data`	object	no	Custom key/value data to attach to the calendar.

addevent.addevent_list_timezones 0 parameters

Schema command

kosmo integrations:schema addevent.addevent_list_timezones --json

Parameter	Type	Required	Description
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.