New:Microsoft Teams Notifications Are Now Available in Socket.Learn more →
Get Started

thunderphone

Package Overview
Dependencies
Maintainers
1
Versions
1
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

thunderphone

ThunderPhone thunderphone command line tools

latest
Source
npmnpm
Version
0.1.0
Version published
Weekly downloads
184
Maintainers
1
Weekly downloads
 
Created
Source

thunderphone

npx thunderphone login
npx thunderphone agents list --json
npx thunderphone init my-agent
npx thunderphone mcp setup --client cursor --api-key-env THUNDERPHONE_API_KEY

Node 18.18+. See thunderphone --help and command --help for options. Documentation: https://thunderphone.com/docs/guides/cli

API errors exit nonzero and print the API error body on stderr. --json emits JSON on stdout for success. Credential fields are redacted. Login prints only organization/profile metadata on stdout; verification instructions go to stderr. Secrets are stored in a mode-0600 credentials file under the platform-independent ~/.config/thunderphone directory (or XDG_CONFIG_HOME / THUNDERPHONE_CONFIG_DIR). THUNDERPHONE_API_KEY takes precedence over profiles. THUNDERPHONE_PROFILE and --profile select a stored profile; THUNDERPHONE_API_BASE_URL and --api-base-url override the API URL. A stored token is never forwarded to a different configured API URL. Logout removes local credentials, not the server grant.

Agent updates write drafts; deploy explicitly. Number assignment is inbound. Outbound calls need --from or THUNDERPHONE_FROM_NUMBER set to your connected carrier number. Scenario tests require --consent-to-charge because the API requires explicit billing consent. Imports accept a vendor JSON export path; inspect with imports get, then explicitly imports commit the returned UUID.

FAQs

Package last updated on 20 Sep 2026

Related posts