request_device_auth — mkdshare.DEV MCP Tool
request_device_auth
(request device auth) is one of 11 tools on the
mkdshare.DEV
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call request_device_auth from your client
- Claude Code mkdshare.DEV request_device_auth run in your project directory
- Claude Desktop mkdshare.DEV request_device_auth ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor mkdshare.DEV request_device_auth ~/.cursor/mcp.json
- VS Code mkdshare.DEV request_device_auth .vscode/mcp.json
- Zed mkdshare.DEV request_device_auth ~/.config/zed/settings.json
- Windsurf mkdshare.DEV request_device_auth ~/.codeium/windsurf/mcp_config.json
- Cline mkdshare.DEV request_device_auth ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI mkdshare.DEV request_device_auth ~/.gemini/settings.json
- Grok mkdshare.DEV request_device_auth .mcp.json (in your project root)
- ChatGPT mkdshare.DEV request_device_auth Settings → Connectors → Advanced → Developer mode
- Claude.ai mkdshare.DEV request_device_auth Settings → Connectors → Add custom connector
- LangChain mkdshare.DEV request_device_auth pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mkdshare https://mkdshare.dev/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.