@neottia/claude-code-adapter

@neottia/claude-code-adapter projects Neottia commands, Agent Skills, custom agents, and project MCP configuration for Claude Code. It implements HarnessAdapter from @neottia/harness-adapter and does not read files, write files, run commands, or authenticate MCP servers.

Install

pnpm add @neottia/claude-code-adapter @neottia/harness-adapter

Use

import { claudeCodeHarnessAdapter } from "@neottia/claude-code-adapter";

claudeCodeHarnessAdapter.planHostConfiguration({
  kind: "mcp.local",
  scope: "project",
  server: {
    name: "neottia-issues",
    command: ["node", "issues-server.js"],
  },
});

The adapter returns an operation for .mcp.json#/mcpServers. The distribution package applies that operation only after review and preserves unrelated server entries. Runtime package declarations map the four Neottia modules to their exact generic MCP packages and launch them with npx.

Paths

Project assets use these paths:

• commands: .claude/commands/<id>.md
• skills: .claude/skills/<id>/SKILL.md
• agents: .claude/agents/<id>.md
• MCP configuration: .mcp.json

Global commands, skills, and agents use the same directories under ~/.claude. The adapter does not edit ~/.claude.json, so MCP plans support project scope only.

Limits

Claude Code plugins require directories with manifests and components. The shared extension request contains one TypeScript source file, so the adapter rejects extension projection instead of inventing a plugin package. Runtime packages use project-scoped MCP instead of Claude Code plugins. Global runtime package activation remains unsupported because the adapter does not edit ~/.claude.json.

Command projection supports description, argument hint, and model metadata. Custom agents support model, effort, and maximum turns. The portable per-tool allow, ask, and deny map has no exact Claude Code agent-file representation, so permission metadata returns a diagnostic.

The declaration leaves testedHostVersions empty. Repository tests cover deterministic paths, frontmatter, exact npm-backed MCP operation shapes, shared adapter conformance, SDLC compilation, CLI installation, and packed external-consumer output without executing a Claude Code binary.

See the Claude Code setup guide and adapter contract.