Opfor — MCP Server Target Configuration

Configure an MCP server target for adversarial security evaluation. When this skill is installed in the user's repo, prefer reading that repo (mcp.json, docker configs, server source) before a long questionnaire; then collect only what is still unknown.

1. Target Information

Ask the user about their MCP server (or pre-fill from repo scan when obvious):

• Name — what do they call it? (e.g., "File Server", "Database MCP")
• Transport — how to connect? (stdio or url)
• Command/URL — for stdio: the launch command (e.g., npx @myorg/server); for url: the SSE/HTTP endpoint (e.g., http://localhost:3000/sse)
• Args — command-line arguments (stdio only)
• Env — environment variables needed (e.g., DB_PATH=/tmp/test.db)

2. Transport Type

Ask the user which transport their server uses. Discover available options by scanning ./targets/ for .md files. Default to stdio.