identify_unknown_plasmid — workbench MCP Prompt
identify_unknown_plasmid
is one of 4 prompts on the
workbench
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke identify_unknown_plasmid from your client
- Claude Code workbench Prompt/identify_unknown_plasmid run in your project directory
- Claude Desktop workbench Prompt/identify_unknown_plasmid ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor workbench Prompt/identify_unknown_plasmid ~/.cursor/mcp.json
- VS Code workbench Prompt/identify_unknown_plasmid .vscode/mcp.json
- Zed workbench Prompt/identify_unknown_plasmid ~/.config/zed/settings.json
- Windsurf workbench Prompt/identify_unknown_plasmid ~/.codeium/windsurf/mcp_config.json
- Cline workbench Prompt/identify_unknown_plasmid ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI workbench Prompt/identify_unknown_plasmid ~/.gemini/settings.json
- Grok workbench Prompt/identify_unknown_plasmid .mcp.json (in your project root)
- ChatGPT workbench Prompt/identify_unknown_plasmid Settings → Connectors → Advanced → Developer mode
- Claude.ai workbench Prompt/identify_unknown_plasmid Settings → Connectors → Add custom connector
- LangChain workbench Prompt/identify_unknown_plasmid pip install langchain-mcp-adapters
Other prompts on this server
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.