VSCode extensions for MCP and blogging

Best VSCode extensions for MCP servers and blogging

Here are **top VS Code extensions** tailored for your two main workflows — running and developing for MCP-style servers **and** writing/blogging (Markdown + static site). I’ve grouped them by category with notes on what makes each useful for you, given your interests in journaling platforms, blogging, and dev work. --- ### 🛠 For “MCP servers” / server-side / dev workflows By “MCP” I’m interpreting as either **Model Context Protocol** (for LLM server orchestration) *or* more generally “server/dev tool” — you can apply many of these to your journaling + local-LLM projects too. - entity["software", "MCP Server Runner", 0]: This extension allows you to manage and run MCP-servers (local model context servers) from within VS Code — configure multiple servers, start/stop them, view logs. citeturn0search1 - *Why it’s useful for you:* since you’re hosting local models (e.g., for journaling platform) and maybe orchestrating them, having a VS Code integration helps you monitor and control the server from your editor. - entity["software", "Blockception VSCode Minecraft Bedrock Development Extension", 0]: While this is specifically for Minecraft Bedrock add-on development (JSON, .mcfunction, Molang support) it shows the kind of tooling available if you ever extend into “server mod / game server” space. citeturn0search5 - *Why relevant:* even if you’re not doing Minecraft, the pattern of “helper extensions for domain-specific scripting + JSON + function files” gives you ideas for building your own dev workflow for e.g. local model orchestration, writing custom prompts, etc. - entity["software", "Java Extension Pack", 0] for VS Code (implied out of the “Minecraft Essentials Extension Pack”) : If you do any Java development (e.g., server plugins) then this is useful. citeturn0search12turn0search28 - *Tip:* Even though IntelliJ/Eclipse dominate for Java, VS Code can work if set up properly. citeturn0search32 - Generic server/dev tooling: terminal, Task runner, log viewer — ensure you have “**Integrated Terminal**”, “**Tasks**” configured in `.vscode/tasks.json`, enable “**Log file viewer**” or “Output” panel for server logs. - **Settings tip:** For your journaling platform + local LLM work: set up a VS Code “workspace” that includes your backend (Django), your front-end (React), your local model orchestration agents (e.g., SmolAgents), maybe a `docker-compose` file. Then create tasks for “Start server”, “Start model”, “Open logs”. --- ### ✍️ For Blogging / Markdown / Static Site Writing Since you’re working on a blog (markdown files, pictures, Netlify, Jekyll etc) these are essential to streamline writing, previewing, linting, formatting, and publishing. - entity["software", "Markdown All in One", 0]: A comprehensive Markdown extension: provides keyboard shortcuts, table of contents generation, auto-preview and more. citeturn0search13 - entity["software", "Markdown Editor", 0] (by zaaack): A full-featured WYSIWYG editor for Markdown inside VS Code. citeturn0search11 - entity["software", "Markdown Paste", 0] + entity["software", "Paste Image", 0]: These help you drag/paste images into markdown and link them properly — especially useful since your blog uses markdown + pictures. (Mentioned in recommended extension lists) citeturn0search25turn0search10 - entity["software", "markdownlint", 0]: Linting your Markdown (style, formatting) helps keep consistent writing style across posts. citeturn0search26turn0search31 - Optional: entity["software", "Foam", 0] or entity["software", "Dendron", 0] (Markdown-/note-taking oriented): Since you like journaling and persona work, a note-taking / personal knowledge management extension may be helpful (though outside strictly “blog publishing”). citeturn0search22 --- ### ✅ My Recommended Shortlist Given your dual interest (server/dev + blogging), here are **my top 5** picks (install first) to cover both sides well: 1. Markdown All in One 2. Markdown Paste (or Paste Image) 3. markdownlint 4. MCP Server Runner 5. (If working in Java or Minecraft dev) Java Extension Pack OR Minecraft Plugin Development extension You can later add more specialized ones once your environment grows (e.g., auto-publish to Netlify, preview Jekyll site, integrate with Git, etc). --- ### 🔍 Extra Tips & Configuration for Your Setup - For your journaling platform: use a workspace folder with `.vscode/settings.json` to set default preview for `.md` files, set up tasks like “Build site” (for Jekyll/Netlify) and “Run backend”. - Configure **Markdown All in One** to automatically generate Table of Contents, live preview side-by-side, keyboard shortcuts (see settings). - Use **markdownlint** with a `.markdownlint.json` to enforce your writing style (since you’re working on personas, consistent style matters). - For server logs: In VS Code you can configure the “Output” or “Terminal” to auto-scroll, or use an extension like “Log File Highlighter” to view logs cleanly (not listed above, but you might find helpful). - If you ever integrate LLM/agent orchestration inside VS Code (calls to your local LLM via CLI), consider a task that runs your agent graph and watchers to restart when JSON/graph changes. - For image/link handling in blog markdown: use relative paths, set up a VS Code snippet for blog front-matter (which you already might be doing). You can use the “Emmet” like snippet support in VS Code for front-matter boilerplate. --- If you like, I can **compile a full list of ~20 VS Code extensions** (with categories: dev/servers, markdown/blogging, Git/CI/CD, productivity) tailored to your stack (Netlify + Jekyll + Django + local LLM). Would you like me to pull that together?