configuring-diva-mcp

Configure diva-mcp API credentials by patching the plugin's .mcp.json file.

6|Updated May 11, 2026
One-click install
npx skills add https://github.com/divalto/divalto-ia-devkit --skill configuring-diva-mcp-divalto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: configuring-diva-mcp
Source: https://github.com/divalto/divalto-ia-devkit/tree/main/plugins/divalto-devkit/skills/configuring-diva-mcp
Command: npx skills add https://github.com/divalto/divalto-ia-devkit --skill configuring-diva-mcp-divalto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? The divalto-devkit plugin ships with a template .mcp.json that has no authentication headers, so the diva-mcp server returns 401 errors until the partner's API credentials (site, environment, API key) are written into the X-Api-Key header. This Skill interactively collects those values and persists them for all future Claude Code sessions. ## Core Features & Use Cases - Credential collection and injection: Asks the partner for site, environment, and API key, builds the X-Api-Key header in the <site>-<env>@<apikey> format, and patches .mcp.json atomically with a .bak backup. - Robust .mcp.json discovery: Locates the real plugin install path, including versioned marketplace cache directories under ~/.claude/plugins/cache and marketplaces. - Shell-expansion protection: Passes API keys containing $$ or ! via stdin or file instead of argv, preventing bash from corrupting the key. - Use Case: After installing the plugin from the marketplace, a partner runs this Skill, answers three questions, restarts Claude Code, and the mcp__diva-mcp__* tools respond without 401 errors. ## Quick Start Ask Claude to configure your diva-mcp API key by saying "configure diva-mcp" and answer the three questions about your site, environment, and API key.

Frequently Asked Questions about configuring-diva-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure the diva-mcp API key after installing the plugin?

Run the configuring-diva-mcp skill, which locates your .mcp.json, asks for your site code, environment (PROD/TEST/DEV), and API key, then writes the X-Api-Key header. Restart Claude Code afterward so the new configuration is loaded.

Why does diva-mcp return 401 Unauthorized on all tools?

A 401 usually means the API key is expired, rotated, or the X-Api-Key header format is wrong. Verify the header matches `<site>-<env>@<apikey>` exactly, confirm the key is still active with Divalto, then rerun the skill with correct values.

How do I pass an API key containing $$ without it getting corrupted?

Pass the key via stdin using `printf '%s' '<key>' | py scripts/write_credentials.py --apikey-stdin ...` or via --apikey-file. Under bash, $$ in argv is expanded to the shell PID before Python sees it, truncating the key.

Where is the .mcp.json file when the plugin is installed via marketplace?

Marketplace installs live under ~/.claude/plugins/cache/<owner>/divalto-devkit/<version>/.mcp.json or ~/.claude/plugins/marketplaces/<owner>/plugins/divalto-devkit/.mcp.json. The locate_mcp_json.py script finds the newest version automatically.

Why don't the mcp__diva-mcp__* tools appear after configuring and restarting?

Check main.log for 'shadowing' or 'remote: 0' markers, which mean Claude Code neutralized the remote MCP server. Also verify settings.json has no UTF-8 BOM from PowerShell edits, and follow the post-install-checks reference for the version-dependent workaround.

Do I need to restart Claude Code after writing credentials?

Yes, a full restart is mandatory because .mcp.json is only parsed at startup with no runtime reload. Close all Claude processes via the task manager, not just the window, then relaunch and test with a simple tool call.