ki-binding

Synchronize MCP server, skill, and agent configurations across Claude surfaces via mcps.yaml.

Updated May 29, 2026
One-click install
npx skills add https://github.com/knowledgeislands/ki-agentic-harness --skill ki-binding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ki-binding
Source: https://github.com/knowledgeislands/ki-agentic-harness/tree/main/skills/ki-binding
Command: npx skills add https://github.com/knowledgeislands/ki-agentic-harness --skill ki-binding

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ki-bootstrap, ki-mcp, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The ki-binding skill manages and maintains consistent configuration and functionality of MCP servers, skills, and agents across different surfaces such as Claude Code, Claude Desktop, Claude Cowork, and claude.ai web. It solves the issue of configuration drift between different surfaces by ensuring all are synchronized with a single source, mcps.yaml.

Core Features & Use Cases

  • Configuration Management: Consistently applies the single source configuration file, mcps.yaml, to various surfaces.
  • Audit: Audits configurations to ensure surfaces align with the single source and surfaces are configured correctly.
  • Integration: Integrates with the ki-bootstrap and ki-mcp skills for full setup and configuration.
  • Use Case: When configuring a new surface to run MCP servers, skills, and agents, ki-binding helps ensure all components are correctly set up and synchronized.

Quick Start

Use the ki-binding skill to configure and audit the mcps.yaml for Claude Code.

Frequently Asked Questions about ki-binding

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

FAQPage Schema
How do I synchronize MCP server configuration across Claude Code, Claude Desktop, and claude.ai web?

You maintain consistent MCP server configuration across Claude surfaces by applying a single source file, `mcps.yaml`. This prevents configuration drift and ensures all environments align correctly.

What causes configuration drift between Claude Desktop and Claude Code when running agents?

Configuration drift between Claude surfaces happens when settings are modified independently across applications. Using a single source file, `mcps.yaml`, prevents this drift by auditing and synchronizing all surfaces to one authoritative configuration.

How do I audit MCP server and agent configurations to ensure they match the source file?

You audit MCP servers and agents by comparing active surface settings against the single source `mcps.yaml` file. This verifies that all surfaces align correctly and identifies any configuration drift to ensure consistent setup.

Do I need ki-bootstrap and ki-mcp to manage cross-surface configuration for Claude applications?

Yes, ki-binding integrates with ki-bootstrap and ki-mcp for a complete setup. These dependencies provide the foundational environment and MCP server management required to apply and maintain the `mcps.yaml` configuration across all surfaces.

Can I use a single configuration file to manage skills and agents across different Claude surfaces?

Yes, you can use the `mcps.yaml` file as a single source to manage skills and agents across different Claude surfaces. The configuration management process applies this file consistently to Claude Code, Claude Desktop, and claude.ai web.

What is the best way to configure a new surface to run MCP servers without causing inconsistencies?

The best way to configure a new surface is to apply the existing `mcps.yaml` single source file. This ensures all MCP servers, skills, and agents are correctly set up and synchronized, preventing inconsistencies from the start.