screen_token — Autosophia Base Lens MCP Tool
screen_token
(screen token) is one of 6 tools on the
Autosophia Base Lens
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call screen_token from your client
- Claude Code Autosophia Base Lens screen_token run in your project directory
- Claude Desktop Autosophia Base Lens screen_token ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Autosophia Base Lens screen_token ~/.cursor/mcp.json
- VS Code Autosophia Base Lens screen_token .vscode/mcp.json
- Zed Autosophia Base Lens screen_token ~/.config/zed/settings.json
- Windsurf Autosophia Base Lens screen_token ~/.codeium/windsurf/mcp_config.json
- Cline Autosophia Base Lens screen_token ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Autosophia Base Lens screen_token ~/.gemini/settings.json
- Grok Autosophia Base Lens screen_token .mcp.json (in your project root)
- ChatGPT Autosophia Base Lens screen_token Settings → Connectors → Advanced → Developer mode
- Claude.ai Autosophia Base Lens screen_token Settings → Connectors → Add custom connector
- LangChain Autosophia Base Lens screen_token pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http base-lens https://base.autosophia.io/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.