MCP-First Design
Design capabilities first for MCP clients, then map them to underlying APIs for a clean AI-native integration model.
Take Me to the Repo
Define MCP exposure with server-level description and tool-level contracts -- name, description, input and output parameters. Support MCP transports (HTTP streaming and Standard IO) so the same capability can run in remote server mode or local IDE and agent mode.
Wire tools to one or many consumed operations via call or orchestrated steps, without changing upstream APIs. Start with the AI-native interface and work backward to the implementation.
The Naftiko Fleet — six components, all at v1.0.0-alpha3
Spec-Driven Integration (SDI) ties every component to a single declarative YAML spec — authored once, linted by Polychro, executed by Ikanos, authored in Crafter, governed by Warden, orchestrated by Skipper, and documented in Shipyard.
Shipyard
The documentation hub and public front door for the Fleet. Tutorials, concepts, editions. Soon: a hosted Playground and AI-assisted Ask Navi search across the corpus.
Ikanos
The OSS capability engine. Runs a Naftiko spec as a multi-protocol server — REST, MCP, and Skill from the same definition. Apache 2.0.
Polychro
The OSS deterministic AI-era linter for YAML, JSON, and Markdown specs. The new Spectral for SDI. Apache 2.0.
Crafter
The capability builder for VS Code and most AI IDEs. Visual + spec-driven authoring with inline governance and live topology.
Warden
Capability governance and policy enforcement for Backstage. Scorecards, scaffolding, fleet explorer, impact tracing.
Skipper
Fleet-wide orchestration for Kubernetes — across teams, regions, and compliance domains. Continuous compliance and FinOps tagging.
Start small, scale smart
Design for AI first. Map to APIs second.
Chart your next course
API-First Design
