veterical-workspace-v1 — Veterical Vet Clinic MCP Resource
veterical-workspace-v1
is one of 6 resources on the
Veterical Vet Clinic
MCP server. Connect the server and your client can attach it as context.
by client
How to attach veterical-workspace-v1 from your client
- Claude Code Veterical Vet Clinic Resource/veterical-workspace-v1 run in your project directory
- Claude Desktop Veterical Vet Clinic Resource/veterical-workspace-v1 ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Veterical Vet Clinic Resource/veterical-workspace-v1 ~/.cursor/mcp.json
- VS Code Veterical Vet Clinic Resource/veterical-workspace-v1 .vscode/mcp.json
- Zed Veterical Vet Clinic Resource/veterical-workspace-v1 ~/.config/zed/settings.json
- Windsurf Veterical Vet Clinic Resource/veterical-workspace-v1 ~/.codeium/windsurf/mcp_config.json
- Cline Veterical Vet Clinic Resource/veterical-workspace-v1 ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Veterical Vet Clinic Resource/veterical-workspace-v1 ~/.gemini/settings.json
- Grok Veterical Vet Clinic Resource/veterical-workspace-v1 .mcp.json (in your project root)
- ChatGPT Veterical Vet Clinic Resource/veterical-workspace-v1 Settings → Connectors → Advanced → Developer mode
- Claude.ai Veterical Vet Clinic Resource/veterical-workspace-v1 Settings → Connectors → Add custom connector
- LangChain Veterical Vet Clinic Resource/veterical-workspace-v1 pip install langchain-mcp-adapters
Other resources on this server
Read from the server itself, by connecting to it and calling resources/list on 2 October 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.