How do I install the MCP skill?

Run npx skillmds@latest add abzhaw/mcp in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with MCP?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

abzhaw (@abzhaw) published this skill. Their other Agent Skills are listed on their SkillMD profile.

MCP by abzhaw — Agent Skill

Name: MCP
Rating: 4.666666666666667 (3 reviews)
Author: abzhaw

File contents

MCP Skill – Server Operations

Use this when you need to stand up, restart, or debug MCP servers that live inside this workspace.

Tooling

node / npm
mcporter CLI (npm i -g mcporter)
curl, jq for quick HTTP checks
Source lives under bridge/ (Julia relay) or future bridge-*/ folders

Typical Workflow

Install deps (per server folder):
```
cd bridge
npm install
```
Start the server:
```
npm start
```
Logs appear with [bridge] prefixes.

Register with mcporter:

mcporter config add julia-bridge http://127.0.0.1:3001 --transport http

Health check:

mcporter call julia-bridge.bridge_health

Expose tools: ensure each MCP method is documented via a skill (skills/julia-bridge/*.yml).

Adding a New MCP Server

mkdir bridge-<name> and npm init -y.
Add server.js using @modelcontextprotocol/sdk (StreamableHTTP or SSE transport).
Define tools with Zod schemas (registerTool). Always return structured content when specifying an outputSchema.
Provide HTTP helper endpoints (e.g., /health, /queues) if needed.
Document operations in a dedicated skill folder (skills/<name>/).
Update agents/ to include the new skills.

Debugging Checklist

Symptom	Action
`HTTP 404` from mcporter	Server not routing `/mcp` correctly – verify Streamable HTTP handler.
`Output validation error`	Ensure tool response includes `structuredContent` matching the `outputSchema`.
Hang on start	Run `node server.js` directly to catch stack traces.
Multiple servers needed	Run each in its own terminal or use `tmux` (`skills/tmux`).

Heartbeats & Queues (Bridge Example)

/heartbeat/<peer> to update status.
/queues/<target> to inspect or debug stuck messages.
/inbound for Julia → OpenClaw posts.

Logging & Memory

Capture major incidents in memory/YYYY-MM-DD.md.
If a new pattern emerges, add a heuristic in HEURISTICS.md (e.g., “restart mcporter config when endpoint changes”).

Related Skills

skills/julia-bridge – specific procedures for the Julia relay
skills/agents – wiring MCP tools into agent manifests
skills/agents-system – fleet-wide maintenance

---name: mcpdescription: Operate, debug, and extend local MCP servers (bridge, future services) using mcporter + Node tooling.---# MCP Skill – Server OperationsUse this when you need to stand up, restart, or debug MCP servers that live inside this workspace.## Tooling- `node` / `npm`- `mcporter` CLI (`npm i -g mcporter`)- `curl`, `jq` for quick HTTP checks- Source lives under `bridge/` (Julia relay) or future `bridge-*/` folders## Typical Workflow1. **Install deps** (per server folder): ```bash cd bridge npm install ```2. **Start the server:** ```bash npm start ``` Logs appear with `[bridge]` prefixes.3. **Register with mcporter:** ```bash mcporter config add julia-bridge http://127.0.0.1:3001 --transport http ```4. **Health check:** ```bash mcporter call julia-bridge.bridge_health ```5. **Expose tools:** ensure each MCP method is documented via a skill (`skills/julia-bridge/*.yml`).## Adding a New MCP Server1. `mkdir bridge-<name>` and `npm init -y`.2. Add `server.js` using `@modelcontextprotocol/sdk` (StreamableHTTP or SSE transport).3. Define tools with Zod schemas (`registerTool`). Always return structured content when specifying an `outputSchema`.4. Provide HTTP helper endpoints (e.g., `/health`, `/queues`) if needed.5. Document operations in a dedicated skill folder (`skills/<name>/`).6. Update `agents/` to include the new skills.## Debugging Checklist| Symptom | Action || --- | --- || `HTTP 404` from mcporter | Server not routing `/mcp` correctly – verify Streamable HTTP handler. || `Output validation error` | Ensure tool response includes `structuredContent` matching the `outputSchema`. || Hang on start | Run `node server.js` directly to catch stack traces. || Multiple servers needed | Run each in its own terminal or use `tmux` (`skills/tmux`). |## Heartbeats & Queues (Bridge Example)- `/heartbeat/<peer>` to update status.- `/queues/<target>` to inspect or debug stuck messages.- `/inbound` for Julia → OpenClaw posts.## Logging & Memory- Capture major incidents in `memory/YYYY-MM-DD.md`.- If a new pattern emerges, add a heuristic in `HEURISTICS.md` (e.g., “restart mcporter config when endpoint changes”).## Related Skills- `skills/julia-bridge` – specific procedures for the Julia relay- `skills/agents` – wiring MCP tools into agent manifests- `skills/agents-system` – fleet-wide maintenance

Frequently asked questions

MCP