Declarative custom capability with inbound MCP and outbound HTTP adapters

[jlouvel]

As an integration engineer, I need to rightsize my AI context to solve issues like:
￭ Data and tools overload confuse LLM
￭ Context rot builds over time
￭ Token cost for discovery and usage

By declaring a Naftiko capability, I get those benefits:
￭ Curate data and tool focuses LLM
￭ Specialize capability per use case
￭ Optimized token consumption

[eskenazit]

I am expecting a lot of needed decisions and back and forth on tools expositions, ergo put the size to L

[jlouvel]

In addition of our pending support for "tools" exposition, we should also add the ability to declare exposed "resources" and "prompts" in the Naftiko Spec and via the MCP server adapter

[jlouvel]

I have also added support for "stdio" transport in addition to "streaming HTTP" transport.

[jlouvel]

Pending:

• Add support for MCP resources
• Add support for MCP prompts

[jlouvel]

Plan to add support for MCP resources and prompts:
https://github.com/naftiko/framework/blob/feat/spec-gaps/src/main/resources/specs/mcp-resources-prompts-proposal.md

[jlouvel]

Implementation added based on reviewed proposal
#114