Can I use deps.dev as a CLI?

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

Can I expose deps.dev through MCP?

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

Where are deps.dev credentials stored?

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

Can I deny write access for deps.dev MCP tools?

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

data

deps.dev CLI for AI Agents

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

deps.dev CLI Setup

deps.dev can be configured headlessly with `kosmokrator integrations:configure deps-dev`.

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 deps-dev --enable --read allow --write ask --json
kosmokrator integrations:doctor deps-dev --json
kosmokrator integrations:status --json

Credentials

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

No credentials are required.

Command Patterns

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

Generic CLI call

kosmo integrations:call deps-dev.deps_dev_package '{}' --json

Provider shortcut

kosmo integrations:deps-dev deps_dev_package '{}' --json

Discovery

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

Discovery commands

kosmo integrations:docs deps-dev --json
kosmo integrations:docs deps-dev.deps_dev_package --json
kosmo integrations:schema deps-dev.deps_dev_package --json
kosmo integrations:search "deps.dev" --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.

`deps-dev.deps_dev_package`

Retrieve package metadata and available versions.

Read read

Parameters: none

Generic call

kosmo integrations:call deps-dev.deps_dev_package '{}' --json

Shortcut

kosmo integrations:deps-dev deps_dev_package '{}' --json

`deps-dev.deps_dev_version`

Retrieve metadata for one package version.

Read read

Parameters: none

Generic call

kosmo integrations:call deps-dev.deps_dev_version '{}' --json

Shortcut

kosmo integrations:deps-dev deps_dev_version '{}' --json

`deps-dev.deps_dev_requirements`

Retrieve declared dependency requirements for one version.

Read read

Parameters: none

Generic call

kosmo integrations:call deps-dev.deps_dev_requirements '{}' --json

Shortcut

kosmo integrations:deps-dev deps_dev_requirements '{}' --json

`deps-dev.deps_dev_dependencies`

Retrieve the resolved dependency graph for one version.

Read read

Parameters: none

Generic call

kosmo integrations:call deps-dev.deps_dev_dependencies '{}' --json

Shortcut

kosmo integrations:deps-dev deps_dev_dependencies '{}' --json

`deps-dev.deps_dev_project`

Retrieve project metadata for a source repository.

Read read

Parameters: none

Generic call

kosmo integrations:call deps-dev.deps_dev_project '{}' --json

Shortcut

kosmo integrations:deps-dev deps_dev_project '{}' --json

`deps-dev.deps_dev_project_package_versions`

Retrieve package versions built from a source project.

Read read

Parameters: none

Generic call

kosmo integrations:call deps-dev.deps_dev_project_package_versions '{}' --json

Shortcut

kosmo integrations:deps-dev deps_dev_project_package_versions '{}' --json

`deps-dev.deps_dev_advisory`

Retrieve one OSV advisory from deps.dev.

Read read

Parameters: none

Generic call

kosmo integrations:call deps-dev.deps_dev_advisory '{}' --json

Shortcut

kosmo integrations:deps-dev deps_dev_advisory '{}' --json

`deps-dev.deps_dev_query`

Query package versions by content hash, version key, or both.

Read read

Parameters: none

Generic call

kosmo integrations:call deps-dev.deps_dev_query '{}' --json

Shortcut

kosmo integrations:deps-dev deps_dev_query '{}' --json

Function Schemas

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

deps-dev.deps_dev_package 0 parameters

Schema command

kosmo integrations:schema deps-dev.deps_dev_package --json

Parameter	Type	Required	Description
No parameters.

deps-dev.deps_dev_version 0 parameters

Schema command

kosmo integrations:schema deps-dev.deps_dev_version --json

Parameter	Type	Required	Description
No parameters.

deps-dev.deps_dev_requirements 0 parameters

Schema command

kosmo integrations:schema deps-dev.deps_dev_requirements --json

Parameter	Type	Required	Description
No parameters.

deps-dev.deps_dev_dependencies 0 parameters

Schema command

kosmo integrations:schema deps-dev.deps_dev_dependencies --json

Parameter	Type	Required	Description
No parameters.

deps-dev.deps_dev_project 0 parameters

Schema command

kosmo integrations:schema deps-dev.deps_dev_project --json

Parameter	Type	Required	Description
No parameters.

deps-dev.deps_dev_project_package_versions 0 parameters

Schema command

kosmo integrations:schema deps-dev.deps_dev_project_package_versions --json

Parameter	Type	Required	Description
No parameters.

deps-dev.deps_dev_advisory 0 parameters

Schema command

kosmo integrations:schema deps-dev.deps_dev_advisory --json

Parameter	Type	Required	Description
No parameters.

deps-dev.deps_dev_query 0 parameters

Schema command

kosmo integrations:schema deps-dev.deps_dev_query --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.