Can I use SpeedCurve as a CLI?

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

Can I expose SpeedCurve through MCP?

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

Where are SpeedCurve credentials stored?

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

Can I deny write access for SpeedCurve MCP tools?

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

analytics

SpeedCurve CLI for CI

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

7 functions 6 read 1 write API key auth

Submit SpeedCurve feedback View package source

SpeedCurve CLI for CI

Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status.

Use this shape when a pipeline needs to read or update an external service. The SpeedCurve CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# SpeedCurve CLI for CI
kosmokrator integrations:configure speedcurve --set api_key="$SPEEDCURVE_API_KEY" --enable --read allow --write ask --json
kosmo integrations:call speedcurve.speedcurve_list_sites '{}' --json

Discovery Before Execution

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

kosmo integrations:docs speedcurve --json
kosmo integrations:docs speedcurve.speedcurve_list_sites --json
kosmo integrations:schema speedcurve.speedcurve_list_sites --json
kosmo integrations:search "SpeedCurve" --json
kosmo integrations:list --json

Useful SpeedCurve CLI Functions

Function	Type	Parameters	Description
`speedcurve.speedcurve_list_sites`	Read	none	List all monitored sites in SpeedCurve. Returns site IDs, names, and URLs that you can use to query test results.
`speedcurve.speedcurve_get_site`	Read	site_id	Get detailed information about a specific SpeedCurve site, including its URLs, test settings, and latest test results.
`speedcurve.speedcurve_list_tests`	Read	site_id, url_id, browser, region, days	List recent synthetic test results from SpeedCurve. Optionally filter by site, browser, or region.
`speedcurve.speedcurve_get_test`	Read	test_id	Get detailed results for a specific SpeedCurve synthetic test run, including Core Web Vitals, filmstrip data, and waterfall metrics.
`speedcurve.speedcurve_list_deployments`	Read	site_id, limit	List recent deployments in SpeedCurve and their performance impact. Shows how each deploy affected Core Web Vitals and load times.
`speedcurve.speedcurve_create_deployment`	Write	site_id, note, detail	Register a new deployment in SpeedCurve to trigger synthetic performance tests. Use this when deploying code changes to track their performance impact.
`speedcurve.speedcurve_get_current_user`	Read	none	Get details about the currently authenticated SpeedCurve user. Useful for verifying API credentials and checking 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 SpeedCurve CLI Pages

Cron Jobs SpeedCurve CLI for cron jobs. Shell Scripts SpeedCurve CLI for shell scripts. Headless Automation SpeedCurve CLI for headless automation. Coding Agents SpeedCurve CLI for coding agents.