vet_a_studio — Game Dev Outsourcing Directory MCP Prompt

vet_a_studio is one of 3 prompts on the Game Dev Outsourcing Directory MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke vet_a_studio from your client

• Claude Code Game Dev Outsourcing Directory Prompt/vet_a_studio run in your project directory
• Claude Desktop Game Dev Outsourcing Directory Prompt/vet_a_studio ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Game Dev Outsourcing Directory Prompt/vet_a_studio ~/.cursor/mcp.json
• VS Code Game Dev Outsourcing Directory Prompt/vet_a_studio .vscode/mcp.json
• Zed Game Dev Outsourcing Directory Prompt/vet_a_studio ~/.config/zed/settings.json
• Windsurf Game Dev Outsourcing Directory Prompt/vet_a_studio ~/.codeium/windsurf/mcp_config.json
• Cline Game Dev Outsourcing Directory Prompt/vet_a_studio ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Game Dev Outsourcing Directory Prompt/vet_a_studio ~/.gemini/settings.json
• Grok Game Dev Outsourcing Directory Prompt/vet_a_studio .mcp.json (in your project root)
• ChatGPT Game Dev Outsourcing Directory Prompt/vet_a_studio Settings → Connectors → Advanced → Developer mode
• Claude.ai Game Dev Outsourcing Directory Prompt/vet_a_studio Settings → Connectors → Add custom connector
• LangChain Game Dev Outsourcing Directory Prompt/vet_a_studio pip install langchain-mcp-adapters

Other prompts on this server

• shortlist_studios
• compare_outsourcing_regions

Game Dev Outsourcing Directory also offers 4 resources — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, 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 prompt's arguments.