harness-mcp-inventory

Audits MCP server configurations across OpenCode and Cursor files for drift and inline secrets.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill harness-mcp-inventory-maicongambini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-mcp-inventory
Source: https://github.com/MaiconGambini/opencode-harness-guide/tree/main/skills/harness-mcp-inventory
Command: npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill harness-mcp-inventory-maicongambini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? MCP server configurations often spread across multiple files (OpenCode config, project-level MCP files, Cursor mcp.json), causing drift, duplication, and accidentally committed inline secrets. This Skill inventories all of them in one pass so you can spot inconsistencies and credential leaks before they become incidents. ## Core Features & Use Cases - Config Discovery: Locates MCP configuration across OpenCode, project MCP files, and Cursor mcp.json. - Drift and Duplication Detection: Reports whether MCPs are present and where definitions diverge between locations. - Secret Detection: Flags inline secret-bearing keys and outputs redacted remediation steps only. - Use Case: Before merging a branch, run the inventory to confirm no API keys were pasted directly into mcp.json and that all environments reference the same MCP servers. ## Quick Start Ask the agent to run the harness MCP inventory audit and report any drift, duplication, or inline secrets across my MCP configuration files.

Frequently Asked Questions about harness-mcp-inventory

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

FAQPage Schema
How do I audit MCP server configurations across multiple tools?

Run the harness-mcp-inventory script with node .opencode/scripts/harness-mcp-inventory.mjs. It scans OpenCode config, project MCP files, and Cursor mcp.json, then reports config locations and whether MCPs are present in each.

How to detect secrets committed in mcp.json files?

The inventory script flags inline secret-bearing keys found in MCP configuration files. It outputs redacted remediation steps only, so credentials are never printed in full during the audit.

Does this work with both OpenCode and Cursor MCP configs?

Yes, the audit covers OpenCode configuration, project-level MCP files, and Cursor mcp.json in a single run. It reports each config location separately so you can compare them for drift.

What is MCP configuration drift and why does it matter?

Drift occurs when MCP server definitions diverge between config locations, causing inconsistent tool availability across environments. The inventory detects duplication and divergence so you can reconcile definitions before they cause runtime failures.

Does the audit expose my API keys in its output?

No, the report redacts secret values and provides remediation steps only. It identifies which keys contain inline secrets without printing the credentials themselves.