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

@thunderphone/mcp

Package Overview
Dependencies
Maintainers
2
Versions
1
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@thunderphone/mcp

ThunderPhone thunderphone-mcp command line tools

latest
Source
npmnpm
Version
0.1.0
Version published
Maintainers
2
Created
Source

@thunderphone/mcp

npx -y @thunderphone/mcp
npx -y @thunderphone/mcp setup --client cursor --api-key-env THUNDERPHONE_API_KEY
npx -y @thunderphone/mcp setup --client claude-desktop --scope user

Node 18.18+. Starts a stdio bridge to https://api.thunderphone.com/v1/mcp. THUNDERPHONE_API_KEY wins; otherwise it uses the current thunderphone login profile and refreshes expiring tokens, or delegates OAuth to mcp-remote. Set THUNDERPHONE_PROFILE or --profile to choose a profile. THUNDERPHONE_MCP_URL overrides the remote endpoint. Stored tokens require a matching API origin. HTTP overrides are restricted to localhost.

Setup supports Claude Code, Codex, Cursor, VS Code, Gemini, Claude Desktop and Windsurf, preserving unrelated servers. Desktop and Windsurf require user scope. Desktop uses stdio; the other clients use direct HTTP. Without --api-key-env, direct HTTP configs rely on the client's OAuth support. Direct HTTP does not read CLI credentials; choose stdio to reuse device login. Desktop inherits environment variables from its launcher; CLI credentials avoid storing keys in its config.

No telemetry. Do not put key values on the command line. JSON-RPC owns stdout when serving; diagnostics go to stderr.

FAQs

Package last updated on 20 Sep 2026

Related posts