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.
Build the Fleet You Need Today
Naftiko packages the open-source capability framework into a developer environment teams can actually ship with.
Capability Spec
Declarative YAML specification validated by JSON Schema that defines consumption, orchestration, exposure, governance, and deployment for each capability.
Framework
Java-based Docker runtime that interprets the capability spec and runs it as a live service. With CLI, VS Code, Backstage, and Docker Desktop extensions.
Fleet Coming in Q2
The governed layer where capabilities become discoverable, composable, observable, and cost-bounded across the organization.
Start small, scale smart
Design for AI first. Map to APIs second.
Chart your next course
API-First Design
