(DEMO): TDD and MCP capability

[jona42-ui]

This issue mainly is to demo MCP-driven capabilites for TDD

I got a chance to familiarise myself with the concepts of TDD . And I had a previlege to go through TDD using the JSON-LD playground, and it was interesting to me and i blogged by findings here,

As I went on I wanted to see how best to integrate MCP capabilities too just for the start.
Basically, what I did was a basic CRUD operation on TDs via MCP tools, simply querying TDs and providing response as context to the LLM

Screencast.from.2026-03-03.23-51-25.webm

Not so interesting, but I was curious to experiment with the capability of the MCP tools and TDD using flask and streamlit and open ai ; using the example TDs that I interacted with lask week using the JSON-LD playground.

I am interested to explore how TDD can be used to interact with Things when using MCP and the Thing supported protocols or maybe I am missing something? I would like your guidance and where this have to live? stand alne gateway or within the domus api?

thanks in advance.
cc @wiresio / @relu91 / @egekorkan ... sorry for tagging you it could make alot of noice in your inbox.

[wiresio]

I am currently a bit busy, but will observe this and give feedback.

[jona42-ui]

I am currently a bit busy, but will observe this and give feedback.

alright @wiresio will be waiting

[jona42-ui]

I am currently a bit busy, but will observe this and give feedback.

Hi @wiresio

I am still waiting for your feedback specifically on my doubts concerning the overall architecture specifically for the TDD api interaction with things. Does this imply we will have a wot consumer library or we need to make our custom implementations for some specific protocols? for a standalone service or we need to simulate the protocols some how .
sorry if it looks obvious

[wiresio]

Hi @jona42-ui,

sorry for the late reply and thanks for your summary of first Domus TDD impressions!

Think of Domus as a database for TDs for you can store, manage, and query them. It is not a TD runtime and should not be one. However, combining the WoT Scripting API as implemented in node-wot with Domus would make a lot of sense.

You certainly know about our planned GSoC project. Since you are interested in these activities, please feel free to apply. Would be great if we'd continue our discussions there.

[jona42-ui]

Hi @jona42-ui,

sorry for the late reply and thanks for your summary of first Domus TDD impressions!

Think of Domus as a database for TDs for you can store, manage, and query them. It is not a TD runtime and should not be one. However, combining the WoT Scripting API as implemented in node-wot with Domus would make a lot of sense.

You certainly know about our planned GSoC project. Since you are interested in these activities, please feel free to apply. Would be great if we'd continue our discussions there.

thank you @wiresio for the feedback that makes alot of sense
Sure much interested, I will go ahead to continue our discussion there and subsequently make a draft proposal

[wiresio]

Let's continue discussing here.