mache-usage

Start or locate a mache MCP server and return session details.

2|1|Updated Oct 3, 2025
One-click install
npx skills add https://github.com/jamestexas/agents --skill mache-usage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mache-usage
Source: https://github.com/jamestexas/agents/tree/main/skills/mache-usage
Command: npx skills add https://github.com/jamestexas/agents --skill mache-usage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill orchestrates the lifecycle of a mache MCP server for a given source path or database, starting or locating an active server and returning the port and session information to enable downstream tooling.

Core Features & Use Cases

  • Start or attach to a mache MCP server for local development or automation pipelines.
  • Build a .db from source if needed and keep the server ready for subsequent analysis tasks.
  • Serve as the base skill for diagram-gen-spec, diagram-gen-emergent, and review-prep workflows.

Quick Start

Provide a source path or .db file to start or attach to a mache MCP server.

Frequently Asked Questions about mache-usage

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

FAQPage Schema
How do I start a mache MCP server for local code analysis?

Starting a mache MCP server involves providing a source path or .db file, which triggers the lifecycle orchestration to launch or locate an active server and return the port with session details for downstream code analysis.

What is the best way to manage an MCP server lifecycle in an automation pipeline?

The best way to manage an MCP server lifecycle in automation pipelines is by enforcing argument parsing, server health checks, and session initialization to provide a stable interface for subsequent analysis tools.

Can I attach to an existing MCP server session instead of starting a new one?

Yes, you can attach to an existing MCP server session. The skill locates active servers before starting new instances, returning the active session port and details to enable immediate downstream tooling.

Does the mache server initialization support both directory sources and prebuilt databases?

Yes, mache server initialization supports both directory sources and prebuilt .db files. It automatically builds a database from source if needed to keep the server ready for subsequent analysis tasks.

Why do I need a running MCP server before generating diagrams or reviewing code?

A running MCP server is required because it provides the stable session interface needed by downstream workflows like diagram generation and code reviews to access and analyze the source path or database.

What to do if mache MCP server initialization fails health checks?

If mache MCP server initialization fails health checks, verify the provided source path or .db file is valid. The skill enforces these checks during the server lifecycle to ensure a stable session interface for subsequent tools.