Run any Skill in Manus with one click

mcp-artifact

Stars1

Forks0

UpdatedApril 29, 2026 at 06:43

Validate, diagnose, and understand MCP server declarations and runtime behavior across Claude Code, Cursor, and Codex — transport types, declaration format, and vendor support.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

eyelock

eyelock/assistants

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

6 files

SKILL.md

readonly

name	mcp-artifact
description	Validate, diagnose, and understand MCP server declarations and runtime behavior across Claude Code, Cursor, and Codex — transport types, declaration format, and vendor support.

Use this skill when working with MCP server declarations — validating configuration, diagnosing startup or connection failures, or understanding what each vendor supports.

Declaration format (shared across vendors):

{
  "mcpServers": {
    "server-name": {
      "command": "npx",
      "args": ["-y", "@scope/server"],
      "env": {"KEY": "value"}
    }
  }
}

Transport types:

stdio: local process, command + args. Most widely supported.
HTTP/SSE: remote server via URL. Claude Code and Cursor support this; Codex does not.
streamable HTTP: Cursor-specific extension with OAuth support.

Diagnostic approach for MCP failures:

Check declaration file exists in the right location for the vendor (paths differ — see references/)
Check the server process starts: run the command manually
Check transport: stdio servers write to stderr for debug output
Check vendor support: some transports and features are vendor-specific
Use MCP Inspector for local stdio debugging (make mcp in eyelock/mcp-toolkit)

Plugin vs project declaration: file location differs by vendor — see references/. In Claude Code, --plugin-dir does NOT auto-activate MCP; requires /plugin enable.

For MCP spec details (tools, resources, prompts, sampling, elicitation, pagination, cancellation), see references/mcp-spec.md. For implementation patterns, see references/mcp-toolkit.md.

More from this repository

same repository

archive-media

eyelock/assistants

Copy processed MP3s and WAVs to NAS storage. Use after Apple Music import or when re-archiving corrected files.

2026-07-011

cleanup

eyelock/assistants

Move processed ZIPs to archive and clean up extraction folders. Use after album processing is complete.

2026-07-011

import-to-apple-music

eyelock/assistants

Copy finished MP3s into Apple Music via the auto-import folder and verify the album lands correctly. Use once metadata is finalized and the user wants tracks added to their library — e.g. "add this to Apple Music" or "import these tracks" — even if they don't say "auto-import" explicitly. Also use to diagnose a bad import, e.g. "it showed up as separate tracks instead of one album."

2026-07-011

manage-metadata

eyelock/assistants

Inspect and update MP3 tags: genre, artist, album, track count, compilation flag. Use when checking or fixing music file metadata — including diagnostic questions like "why do these show up as separate tracks" or "is this folder's metadata consistent," not just explicit tag-editing requests.

2026-07-011

process-album

eyelock/assistants

End-to-end processing of downloaded music purchases: extract ZIPs, verify metadata, import to Apple Music, archive to NAS, clean up. Use when processing new music downloads.

2026-07-011

reclaim-space

eyelock/assistants

Reclaim local disk by offloading cloud-backed Apple Music downloads. Audit iCloud status, build an offload playlist that protects your DJ crates and lossless files, then Remove Download. Use when the Mac is low on disk.

2026-07-011

name	mcp-artifact
description	Validate, diagnose, and understand MCP server declarations and runtime behavior across Claude Code, Cursor, and Codex — transport types, declaration format, and vendor support.

Use this skill when working with MCP server declarations — validating configuration, diagnosing startup or connection failures, or understanding what each vendor supports.

Declaration format (shared across vendors):

{
  "mcpServers": {
    "server-name": {
      "command": "npx",
      "args": ["-y", "@scope/server"],
      "env": {"KEY": "value"}
    }
  }
}

Transport types:

stdio: local process, command + args. Most widely supported.
HTTP/SSE: remote server via URL. Claude Code and Cursor support this; Codex does not.
streamable HTTP: Cursor-specific extension with OAuth support.

Diagnostic approach for MCP failures:

Check declaration file exists in the right location for the vendor (paths differ — see references/)
Check the server process starts: run the command manually
Check transport: stdio servers write to stderr for debug output
Check vendor support: some transports and features are vendor-specific
Use MCP Inspector for local stdio debugging (make mcp in eyelock/mcp-toolkit)

Plugin vs project declaration: file location differs by vendor — see references/. In Claude Code, --plugin-dir does NOT auto-activate MCP; requires /plugin enable.

For MCP spec details (tools, resources, prompts, sampling, elicitation, pagination, cancellation), see references/mcp-spec.md. For implementation patterns, see references/mcp-toolkit.md.