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 Headless Automation

Use the AddEvent CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 6 read 1 write Bearer token auth

Submit AddEvent feedback View package source

AddEvent CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The AddEvent CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# AddEvent CLI for Headless Automation
kosmokrator integrations:configure addevent --set access_token="$ADDEVENT_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call addevent.addevent_list_events '{"limit":1,"page":1,"category":1}' --json

Discovery Before Execution

Agents and scripts can inspect AddEvent docs and schemas before choosing a function.

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

Useful AddEvent CLI Functions

Function	Type	Parameters	Description
`addevent.addevent_list_events`	Read	limit, page, category	List calendar events from AddEvent. Supports pagination with limit and page parameters, and optional filtering by category ID.
`addevent.addevent_get_event`	Read	id	Get details for a specific AddEvent calendar event by ID.
`addevent.addevent_create_event`	Write	title, start_date, end_date, location, description, category_id	Create a new calendar event in AddEvent. Requires a title, start date, and end date. Optionally add a location, description, and category.
`addevent.addevent_list_categories`	Read	none	List all event categories in AddEvent. Use category IDs to organize and filter events.
`addevent.addevent_list_groups`	Read	limit, page	List event groups from AddEvent. Groups are collections of related events. Supports pagination with limit and page parameters.
`addevent.addevent_get_group`	Read	id	Get details for a specific AddEvent event group by ID.
`addevent.addevent_get_current_user`	Read	none	Get the profile of the currently authenticated AddEvent user. Useful for verifying credentials and displaying account information.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related AddEvent CLI Pages

CI AddEvent CLI for CI. Cron Jobs AddEvent CLI for cron jobs. Shell Scripts AddEvent CLI for shell scripts. Coding Agents AddEvent CLI for coding agents.