Connect Claude Code, VS Code, or a JetBrains IDE to Sandsmedia's expert developer-content catalogue.
| Your tool | Jump to |
|---|---|
| Claude Code (terminal, Cursor, VS Code extension, IntelliJ) | Claude Code setup |
| VS Code + GitHub Copilot | VS Code setup |
| JetBrains IDE + GitHub Copilot | JetBrains setup |
Run this in any terminal with Claude Code installed:
claude mcp add --transport http --scope local developer-intelligence-mcp https://mcp.sandsmedia.com/mcp
--scope local adds it to this project only — see Choosing an edition below to add ?app=devmio or ?app=devmionl to the URL for a non-default edition.
Send any prompt — the first tool call opens a browser sign-in window. Sign in with your entwickler.de account. Run /mcp to confirm developer-intelligence-mcp is connected with 6 tools.
In the root of your project, create a file called .mcp.json with the following content:
{
"mcpServers": {
"developer-intelligence-mcp": {
"type": "http",
"url": "https://mcp.sandsmedia.com/mcp",
"tools": [
"*"
]
}
}
}
For a non-default edition, see Choosing an edition below.
.vscode/mcp.json? Recent VS Code versions offer to migrate it to .mcp.json — accept, and the server keeps working. Older VS Code versions only read .vscode/mcp.json; there, use the same content with "servers" in place of "mcpServers".
Open the Copilot Chat panel using ⌃⌘I (Mac) or Ctrl+Alt+I (Windows/Linux).
At the bottom of the chat input, use the mode dropdown to switch to Agent mode.
How this works depends on which chat mode your VS Code uses. Recent VS Code versions with Workbench: Enable Experiments switched on use the new Copilot chat mode; otherwise it's Local mode.
Copilot chat mode: skip the Start button in .mcp.json — there it shows Error with no reason, which is a VS Code quirk, not a problem with the server. Instead, ask a question in the chat and the server starts by itself. To sign in, open .mcp.json, click Authentication Required above the server, then Authenticate. VS Code opens a browser window — sign in with your entwickler.de account there.
Local mode: click Start first (in .mcp.json, or via the tools icon (🔧) in the chat input bar) and sign in with your entwickler.de account in the browser window that opens. Then open a new chat — a chat that was already open before the server started doesn't see the tools.
Once connected, developer-intelligence-mcp will appear as active in the tools panel. Test it by asking Copilot:
What sessions are there on React performance?
If it returns results from the catalogue, you're all set.
Uses the GitHub Copilot plugin path — not JetBrains AI Assistant or Junie. The Copilot plugin has no OAuth sign-in window, so it authenticates with your email and password directly in the config instead.
Open Copilot Chat → MCP settings (the control that edits mcp.json, not "Auto Approve for Sampling") and paste:
{
"servers": {
"developer-intelligence-mcp": {
"type": "http",
"url": "https://mcp.sandsmedia.com/mcp",
"requestInit": {
"headers": {
"x-email": "YOUR-ENTWICKLER-EMAIL",
"x-password": "YOUR-PASSWORD"
}
}
}
}
}
With mcp.json open, click Start on the status line. Confirm it shows Running with 6 tools.
Copilot Chat → Agent mode → ask a dev question. The first time a tool runs, Copilot asks permission — choose "Always Allow tools from developer-intelligence-mcp".
| Edition | Language | Setup |
|---|---|---|
| entwickler.de | German | default — no change needed |
| devmio | English | add ?app=devmio to the URL |
| devmio.nl | English (Netherlands) | add ?app=devmionl to the URL |
E.g. for VS Code/JetBrains, the "url" becomes https://mcp.sandsmedia.com/mcp?app=devmio; for Claude Code, append the same to the URL in the claude mcp add command.
By default Copilot only uses the MCP tools when you explicitly ask it to. To make it use them automatically for any programming question, add an instructions file to your project telling it when to reach for the catalogue instead of answering from general knowledge — see .github/copilot-instructions.md for GitHub Copilot, or the equivalent workspace-instructions file for other assistants (e.g. CLAUDE.md for Claude Code, AGENTS.md for OpenAI Codex, .cursor/rules for Cursor).
| Problem | Fix |
|---|---|
| Browser sign-in window doesn't open (VS Code) | Click the server name in the tools panel and choose Restart. |
| "Invalid email or password" | Check your entwickler.de credentials. You can verify them at entwickler.de. |
| Server shows as "Error" | In VS Code's Copilot chat mode, the Start button in .mcp.json shows "Error" with no reason — that's expected; ask a question in the chat instead and the server starts by itself. Otherwise, click the server name in the tools panel to see the full error log. Most commonly a network issue or an expired token — try Restart. |
| Asked to sign in again | Expected after 30 days of inactivity, or if the server connection was removed and re-added. |
| No tools appearing (VS Code / JetBrains) | Make sure you are in Agent mode, not Ask or Edit mode. In VS Code's Local mode, open a new chat after starting the server — a chat opened before that doesn't see the tools. |
.mcp.json not picked up (VS Code) |
Ensure the file is saved as .mcp.json in the root of the folder you have open, not a subfolder. On older VS Code versions, use .vscode/mcp.json with "servers" instead. |
Tools not showing in /mcp (Claude Code) |
A newly added server isn't visible in a session that was already running — restart Claude Code. |