screen_token — solmachina x402 MCP Prompt
screen_token
is one of 2 prompts on the
solmachina x402
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke screen_token from your client
- Claude Code solmachina x402 Prompt/screen_token run in your project directory
- Claude Desktop solmachina x402 Prompt/screen_token ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor solmachina x402 Prompt/screen_token ~/.cursor/mcp.json
- VS Code solmachina x402 Prompt/screen_token .vscode/mcp.json
- Zed solmachina x402 Prompt/screen_token ~/.config/zed/settings.json
- Windsurf solmachina x402 Prompt/screen_token ~/.codeium/windsurf/mcp_config.json
- Cline solmachina x402 Prompt/screen_token ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI solmachina x402 Prompt/screen_token ~/.gemini/settings.json
- Grok solmachina x402 Prompt/screen_token .mcp.json (in your project root)
- ChatGPT solmachina x402 Prompt/screen_token Settings → Connectors → Advanced → Developer mode
- Claude.ai solmachina x402 Prompt/screen_token Settings → Connectors → Add custom connector
- LangChain solmachina x402 Prompt/screen_token pip install langchain-mcp-adapters
Other prompts on this server
solmachina x402 also offers 4 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.