Can I use Devin as a CLI?

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

Can I expose Devin through MCP?

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

Where are Devin credentials stored?

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

Can I deny write access for Devin MCP tools?

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

Devin CLI for Cron Jobs

Use the Devin CLI for cron jobs with headless JSON commands, schema discovery, credentials, and permission controls.

5 functions 3 read 2 write API key auth

Submit Devin feedback View package source

Devin CLI for Cron Jobs

Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config.

Use the headless CLI from cron when an operation should run without an interactive agent session. The Devin CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Devin CLI for Cron Jobs
kosmokrator integrations:configure devin --set api_key="$DEVIN_API_KEY" --enable --read allow --write ask --json
kosmo integrations:call devin.devin_create_session '{"prompt":"example_prompt","idempotency_key":"example_idempotency_key"}' --json

Discovery Before Execution

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

kosmo integrations:docs devin --json
kosmo integrations:docs devin.devin_create_session --json
kosmo integrations:schema devin.devin_create_session --json
kosmo integrations:search "Devin" --json
kosmo integrations:list --json

Useful Devin CLI Functions

Function	Type	Parameters	Description
`devin.devin_create_session`	Write	prompt, idempotency_key	Create a new Devin AI session. Provide a task prompt describing what you want Devin to do. Optionally provide an idempotency key to prevent duplicate sessions.
`devin.devin_get_session`	Read	session_id	Retrieve details and current status of a Devin session. Use this to check progress on a task, view the session state, or get the output.
`devin.devin_list_sessions`	Read	none	List all Devin sessions. Returns an overview of all sessions including their IDs, statuses, and creation times.
`devin.devin_send_message`	Write	session_id, message	Send a message to an existing Devin session. Use this to provide additional instructions, ask questions, or guide the AI during an active session.
`devin.devin_get_current_user`	Read	none	Get information about the currently authenticated Devin user. Use this to verify the API connection and identify which account is being used.

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 Devin CLI Pages

CI Devin CLI for CI. Shell Scripts Devin CLI for shell scripts. Headless Automation Devin CLI for headless automation. Coding Agents Devin CLI for coding agents.