.dev — TLD Bench MCP Resource
.dev
is one of 5 resources on the
TLD Bench
MCP server. Connect the server and your client can attach it as context.
by client
How to attach .dev from your client
- Claude Code TLD Bench Resource/.dev run in your project directory
- Claude Desktop TLD Bench Resource/.dev ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TLD Bench Resource/.dev ~/.cursor/mcp.json
- VS Code TLD Bench Resource/.dev .vscode/mcp.json
- Zed TLD Bench Resource/.dev ~/.config/zed/settings.json
- Windsurf TLD Bench Resource/.dev ~/.codeium/windsurf/mcp_config.json
- Cline TLD Bench Resource/.dev ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TLD Bench Resource/.dev ~/.gemini/settings.json
- Grok TLD Bench Resource/.dev .mcp.json (in your project root)
- ChatGPT TLD Bench Resource/.dev Settings → Connectors → Advanced → Developer mode
- Claude.ai TLD Bench Resource/.dev Settings → Connectors → Add custom connector
- LangChain TLD Bench Resource/.dev pip install langchain-mcp-adapters
Other resources on this server
TLD Bench also offers 1 prompt — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 6 November 2026.
A listing does not declare its resources, 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 resource's type and contents.