Data as of
Just Prompt for VS Code: Setup & Config
VS Code: Just Prompt lets an MCP assistant consult several language models and preserve their answers.
What you can do with Just Prompt in VS Code
Keep model comparison, saved answers, and a panel's final decision within one MCP workflow.
- Compare independently generated answers to one prompt without switching assistant integrations.
- Ask a designated decision model to weigh a panel's responses.
Before you start: Just Prompt in VS Code
- Python and uv
- Local checkout with dependencies prepared using uv sync
- Credentials for chosen hosted providers, or an Ollama endpoint
This is the minimal README launch, not uv sync alone, which only prepares dependencies. The dot refers to the checkout directory; use the checkout's path if the client starts elsewhere. Provider values can be supplied by environment or .env. The optional --default-models argument chooses fallback models.
Just Prompt VS Code configuration
Choose VS Code configuration scope
For Just Prompt, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.
Add Just Prompt to VS Code
Use the just-prompt entry below in servers. Keep Just Prompt's documented stdio connection fields and your other VS Code entries.
Check Just Prompt in VS Code
Just Prompt: Start in VS Code’s MCP controls; inspect output and trust prompts.
Config file · Workspace: .vscode/mcp.json
{
"servers": {
"just-prompt": {
"type": "stdio",
"command": "uv",
"args": [
"--directory",
".",
"run",
"just-prompt"
],
"env": {
"OPENAI_API_KEY": "<credential if selecting OpenAI models>",
"ANTHROPIC_API_KEY": "<credential if selecting Anthropic models>",
"GEMINI_API_KEY": "<credential if selecting Gemini models>",
"GROQ_API_KEY": "<credential if selecting Groq models>",
"DEEPSEEK_API_KEY": "<credential if selecting DeepSeek models>",
"OLLAMA_HOST": "<address of the Ollama instance to consult>"
}
}
}
}Just Prompt tools available to VS Code
Just Prompt's stored tool list documents 6 tools; compare it with VS Code's connected tool list, because the stored list is not a live check.
- ceo_and_board
Look for ceo_and_board among VS Code's agent-mode tools after starting Just Prompt through the MCP controls.
Gather a panel's model responses, ask a designated model for a decision, and save the resulting files.
- prompt_from_file_to_file
Look for prompt_from_file_to_file among VS Code's agent-mode tools after starting Just Prompt through the MCP controls.
Read a local prompt by absolute path and write model answers to Markdown output files.
- prompt_from_file
Look for prompt_from_file among VS Code's agent-mode tools after starting Just Prompt through the MCP controls.
- prompt
Look for prompt among VS Code's agent-mode tools after starting Just Prompt through the MCP controls.
Submit text directly to a chosen model set, falling back to configured models when omitted.
- list_models
Look for list_models among VS Code's agent-mode tools after starting Just Prompt through the MCP controls.
- list_providers
Look for list_providers among VS Code's agent-mode tools after starting Just Prompt through the MCP controls.
Troubleshooting Just Prompt in VS Code
- Make uv available in the workspace, container, or remote environment hosting Just Prompt. Start through VS Code's MCP controls; inspect output and trust prompts.
- For Just Prompt, keep ANTHROPIC_API_KEY, DEEPSEEK_API_KEY, GEMINI_API_KEY, GROQ_API_KEY, OLLAMA_HOST, OPENAI_API_KEY out of version control; VS Code documents input variables and secret handling.
- Just Prompt uses stdio here: VS Code must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
- Known limitation: File-based operations require absolute prompt and output paths.
- Known limitation: Each hosted backend needs its own usable credential.
- Known limitation: Reasoning suffixes are tied to documented models and provider-specific limits.
- General VS Code troubleshooting lives in the /clients/vscode guide.
Just Prompt — details. VS Code guide