check_access — Liro MCP Tool Read-only
check_access
(check access) is one of 10 tools on the
Liro
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_access from your client
- Claude Code Liro check_access run in your project directory
- Claude Desktop Liro check_access ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Liro check_access ~/.cursor/mcp.json
- VS Code Liro check_access .vscode/mcp.json
- Zed Liro check_access ~/.config/zed/settings.json
- Windsurf Liro check_access ~/.codeium/windsurf/mcp_config.json
- Cline Liro check_access ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Liro check_access ~/.gemini/settings.json
- Grok Liro check_access .mcp.json (in your project root)
- ChatGPT Liro check_access Settings → Connectors → Advanced → Developer mode
- Claude.ai Liro check_access Settings → Connectors → Add custom connector
- LangChain Liro check_access pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http liro https://liro.dev/api/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 9 November 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.