thingctx 0.1.1__tar.gz

thingctx-0.1.1/LICENSE

@@ -0,0 +1,204 @@
+Copyright 2026 The thingctx Authors
+
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

thingctx-0.1.1/NOTICE

@@ -0,0 +1,5 @@
+thingctx
+Copyright 2026 The thingctx Authors
+
+Licensed under the Apache License, Version 2.0 (see LICENSE).
+Each contributor holds copyright over their contributions.

thingctx-0.1.1/PKG-INFO

@@ -0,0 +1,216 @@
+Metadata-Version: 2.4
+Name: thingctx
+Version: 0.1.1
+Summary: Drive any agent against any W3C WoT Thing, over any transport. No per-integration server.
+Author: The thingctx Authors
+License: Apache-2.0
+Keywords: llm,wot,web-of-things,thing-description,mcp,tool-calling,agents
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: License :: OSI Approved :: Apache Software License
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Provides-Extra: llm
+Requires-Dist: litellm>=1.0; extra == "llm"
+Provides-Extra: http
+Requires-Dist: httpx>=0.25; extra == "http"
+Provides-Extra: mqtt
+Requires-Dist: paho-mqtt>=2.0; extra == "mqtt"
+Provides-Extra: validate
+Requires-Dist: jsonschema>=4.0; extra == "validate"
+Provides-Extra: mcp
+Requires-Dist: mcp>=1.0; extra == "mcp"
+Provides-Extra: all
+Requires-Dist: litellm>=1.0; extra == "all"
+Requires-Dist: httpx>=0.25; extra == "all"
+Requires-Dist: paho-mqtt>=2.0; extra == "all"
+Requires-Dist: jsonschema>=4.0; extra == "all"
+Requires-Dist: mcp>=1.0; extra == "all"
+Provides-Extra: dev
+Requires-Dist: pytest>=7; extra == "dev"
+Requires-Dist: pytest-asyncio>=0.21; extra == "dev"
+Requires-Dist: jsonschema>=4.0; extra == "dev"
+Requires-Dist: mcp>=1.0; extra == "dev"
+Requires-Dist: httpx>=0.25; extra == "dev"
+Requires-Dist: ruff>=0.6; extra == "dev"
+Dynamic: license-file
+
+# thingctx
+
+**One standard description, and your model can read context from and take
+actions on a real device, sensor, tool, or service, directly. No
+per-integration server.**
+
+thingctx uses the [W3C Web of Things](https://www.w3.org/WoT/) standard as a
+uniform interface between an AI application and the systems it needs to
+reach. Point it at a Thing Description and it drives the actual Thing the
+description names, over that Thing's own transport. The description is how
+you integrate; the device or service is what you act on. The integration is
+a document, not a server you run.
+
+A "Thing" here is anything with a callable interface, not just hardware: a
+sensor or a robot, but equally a REST API, a database, a SaaS product, an
+internal service. A Thing Description (TD) is plain JSON that names that
+system's `actions` (things to do), `properties` (state to read or write),
+and `events` (things to subscribe to), plus the transport for each (HTTP,
+MQTT, local, and more). thingctx reads it, hands the actions to your model
+as tools, and calls each against the real system over the transport the TD
+names. The system's own endpoints are the server; you write nothing on the
+server side.
+
+A whole TD can be this small (a weather API, no hardware in sight):
+
+```json
+{
+  "@context": "https://www.w3.org/2022/wot/td/v1.1",
+  "id": "urn:example:weather:v1",
+  "title": "Weather",
+  "securityDefinitions": { "bearer_sc": { "scheme": "bearer" } },
+  "security": ["bearer_sc"],
+  "properties": {
+    "temperature": { "type": "number", "readOnly": true,
+      "forms": [{ "href": "https://api.example.com/temp" }] }
+  },
+  "actions": {
+    "forecast": {
+      "input": { "type": "object", "properties": { "city": { "type": "string" } } },
+      "forms": [{ "href": "https://api.example.com/forecast", "htv:methodName": "POST" }]
+    }
+  }
+}
+```
+
+That document is the integration. Point an agent at it:
+
+```python
+import thingctx
+
+host = await thingctx.from_url("https://api.example.com/.well-known/wot")
+print(await host.chat("what's the forecast for Cairo, and the current temperature?"))
+```
+
+The model picks the actions; thingctx routes each to its transport.
+
+## Install
+
+```bash
+pip install thingctx[all]      # litellm + httpx + paho-mqtt + jsonschema + mcp
+# or pick extras: thingctx[llm] thingctx[http] thingctx[mqtt] thingctx[validate] thingctx[mcp]
+```
+
+## Drive it directly, no server, no MCP
+
+When you own the agent loop, integrate the Thing straight into it: read a
+description, get the tool specs to hand your model, route each call back to
+the Thing. Nothing in between.
+
+```python
+import thingctx
+
+client = thingctx.ThingClient.from_registry(
+    thingctx.from_arg("http://device.local/.well-known/wot"))   # a URL, folder, or TDD
+specs, invoke = client.as_tools()        # specs for your model; invoke(name, args) runs a call
+
+await invoke("pump.set_speed", {"rpm": 1500})
+await client.read_property("pump.rpm")
+```
+
+The description and the Thing's own endpoints are the whole integration.
+Add a Thing by pointing at one more description.
+
+## Reach a closed agent: the MCP bridge
+
+The direct path works when you write the loop yourself, because you can pass
+the tool specs straight to your model. But some agents are closed: you
+cannot give their model tools directly, only through MCP (Claude Desktop, the
+Claude CLI, Copilot). For those, thingctx ships a bridge: one generic
+MCP server that turns a registry of descriptions (a folder, a URL, or a
+W3C Thing Description Directory) into MCP tools, with no per-integration
+server.
+
+```bash
+pip install "thingctx[mcp,http]"
+thingctx-mcp ./examples/registry/        # a folder, a URL, or a TD Directory
+```
+
+```json
+{ "mcpServers": { "things": { "command": "thingctx-mcp",
+  "args": ["./examples/registry/"] } } }
+```
+
+thingctx is not an MCP server for the Web of Things. The integration is the
+description; MCP is just one way to deliver it, to an agent where direct
+tool calling is not available.
+
+## Why not MCP
+
+To expose a system over MCP you write a server, deploy it, and keep it
+running, one per integration. N systems means N processes to operate. A Thing
+Description is a static file: write it (or generate it), check it into git,
+or serve it from a URL. There is no process to run, nothing to keep alive.
+thingctx reads the document and calls the endpoints it names. Integration
+becomes data, not a service, and data scales to a fleet for free.
+
+A messy device (binary protocol, a session dance) gets one thin connector
+that exposes a clean WoT face; the TD describes *that*. Either way you
+write no server per agent integration. The connector is consumed the same way
+by an LLM, an MCP client, or anything else.
+
+For comparison, see [`examples/01_mcp_baseline.py`](examples/01_mcp_baseline.py)
+(MCP, a server per integration) and
+[`examples/02_thingctx_baseline.py`](examples/02_thingctx_baseline.py)
+(thingctx, no server). Both drive the same pump; every result is asserted
+equal to calling the system directly.
+
+## ThingClient: the core
+
+The core is stdlib only, with no dependency on any agent framework.
+`ThingClient` has no LLM and no opinion on what chose the action. It reads
+properties, writes them, and streams events, and routes each call to the
+transport the TD's form names, so one client can read over HTTP and
+subscribe over MQTT without you wiring either:
+
+```python
+await client.read_property("pump.rpm")          # e.g. an HTTP GET
+await client.write_property("pump.target_rpm", 1500)
+async for evt in await client.subscribe("pump.overheat"):   # e.g. an MQTT topic
+    ...                              # evt is the payload, e.g. {"temp": 98}
+```
+
+A text LLM, a vision model, or your own code can drive it; `invoke` is the
+same. (`thingctx.from_url(...)` returns a ready `LLMHost` if you just want a
+loop out of the box.)
+
+## Where the TDs live: a registry
+
+A registry is wherever your descriptions come from: a folder of files, a
+URL, or a **Thing Description Directory** (TDD). It is a general source, not
+tied to any one consumer. `ThingClient`, the MCP bridge, and the LLM loop all
+build from the same registry.
+
+```python
+client = thingctx.ThingClient.from_registry(thingctx.from_arg("./examples/registry/"))
+```
+
+The TDD is not a thingctx invention. It is the
+[W3C WoT Discovery](https://www.w3.org/TR/wot-discovery/) standard (a final
+Recommendation): a service that serves a whole fleet of Things from a
+`/things` endpoint, with optional search. thingctx reads from any compliant
+TDD. Point `from_arg` at its URL.
+
+## Authentication
+
+The TD declares the scheme (`bearer`, `basic`, `apikey`); the secret is
+supplied to the invoker at runtime, never in the TD. So a TD is safe to
+commit and share.
+
+```python
+thingctx.HttpInvoker(credentials={"my_token": "secret"})  # key = the scheme name
+```
+
+## License
+
+Apache-2.0. Copyright 2026 The thingctx Authors.

thingctx-0.1.1/README.md

@@ -0,0 +1,176 @@
+# thingctx
+
+**One standard description, and your model can read context from and take
+actions on a real device, sensor, tool, or service, directly. No
+per-integration server.**
+
+thingctx uses the [W3C Web of Things](https://www.w3.org/WoT/) standard as a
+uniform interface between an AI application and the systems it needs to
+reach. Point it at a Thing Description and it drives the actual Thing the
+description names, over that Thing's own transport. The description is how
+you integrate; the device or service is what you act on. The integration is
+a document, not a server you run.
+
+A "Thing" here is anything with a callable interface, not just hardware: a
+sensor or a robot, but equally a REST API, a database, a SaaS product, an
+internal service. A Thing Description (TD) is plain JSON that names that
+system's `actions` (things to do), `properties` (state to read or write),
+and `events` (things to subscribe to), plus the transport for each (HTTP,
+MQTT, local, and more). thingctx reads it, hands the actions to your model
+as tools, and calls each against the real system over the transport the TD
+names. The system's own endpoints are the server; you write nothing on the
+server side.
+
+A whole TD can be this small (a weather API, no hardware in sight):
+
+```json
+{
+  "@context": "https://www.w3.org/2022/wot/td/v1.1",
+  "id": "urn:example:weather:v1",
+  "title": "Weather",
+  "securityDefinitions": { "bearer_sc": { "scheme": "bearer" } },
+  "security": ["bearer_sc"],
+  "properties": {
+    "temperature": { "type": "number", "readOnly": true,
+      "forms": [{ "href": "https://api.example.com/temp" }] }
+  },
+  "actions": {
+    "forecast": {
+      "input": { "type": "object", "properties": { "city": { "type": "string" } } },
+      "forms": [{ "href": "https://api.example.com/forecast", "htv:methodName": "POST" }]
+    }
+  }
+}
+```
+
+That document is the integration. Point an agent at it:
+
+```python
+import thingctx
+
+host = await thingctx.from_url("https://api.example.com/.well-known/wot")
+print(await host.chat("what's the forecast for Cairo, and the current temperature?"))
+```
+
+The model picks the actions; thingctx routes each to its transport.
+
+## Install
+
+```bash
+pip install thingctx[all]      # litellm + httpx + paho-mqtt + jsonschema + mcp
+# or pick extras: thingctx[llm] thingctx[http] thingctx[mqtt] thingctx[validate] thingctx[mcp]
+```
+
+## Drive it directly, no server, no MCP
+
+When you own the agent loop, integrate the Thing straight into it: read a
+description, get the tool specs to hand your model, route each call back to
+the Thing. Nothing in between.
+
+```python
+import thingctx
+
+client = thingctx.ThingClient.from_registry(
+    thingctx.from_arg("http://device.local/.well-known/wot"))   # a URL, folder, or TDD
+specs, invoke = client.as_tools()        # specs for your model; invoke(name, args) runs a call
+
+await invoke("pump.set_speed", {"rpm": 1500})
+await client.read_property("pump.rpm")
+```
+
+The description and the Thing's own endpoints are the whole integration.
+Add a Thing by pointing at one more description.
+
+## Reach a closed agent: the MCP bridge
+
+The direct path works when you write the loop yourself, because you can pass
+the tool specs straight to your model. But some agents are closed: you
+cannot give their model tools directly, only through MCP (Claude Desktop, the
+Claude CLI, Copilot). For those, thingctx ships a bridge: one generic
+MCP server that turns a registry of descriptions (a folder, a URL, or a
+W3C Thing Description Directory) into MCP tools, with no per-integration
+server.
+
+```bash
+pip install "thingctx[mcp,http]"
+thingctx-mcp ./examples/registry/        # a folder, a URL, or a TD Directory
+```
+
+```json
+{ "mcpServers": { "things": { "command": "thingctx-mcp",
+  "args": ["./examples/registry/"] } } }
+```
+
+thingctx is not an MCP server for the Web of Things. The integration is the
+description; MCP is just one way to deliver it, to an agent where direct
+tool calling is not available.
+
+## Why not MCP
+
+To expose a system over MCP you write a server, deploy it, and keep it
+running, one per integration. N systems means N processes to operate. A Thing
+Description is a static file: write it (or generate it), check it into git,
+or serve it from a URL. There is no process to run, nothing to keep alive.
+thingctx reads the document and calls the endpoints it names. Integration
+becomes data, not a service, and data scales to a fleet for free.
+
+A messy device (binary protocol, a session dance) gets one thin connector
+that exposes a clean WoT face; the TD describes *that*. Either way you
+write no server per agent integration. The connector is consumed the same way
+by an LLM, an MCP client, or anything else.
+
+For comparison, see [`examples/01_mcp_baseline.py`](examples/01_mcp_baseline.py)
+(MCP, a server per integration) and
+[`examples/02_thingctx_baseline.py`](examples/02_thingctx_baseline.py)
+(thingctx, no server). Both drive the same pump; every result is asserted
+equal to calling the system directly.
+
+## ThingClient: the core
+
+The core is stdlib only, with no dependency on any agent framework.
+`ThingClient` has no LLM and no opinion on what chose the action. It reads
+properties, writes them, and streams events, and routes each call to the
+transport the TD's form names, so one client can read over HTTP and
+subscribe over MQTT without you wiring either:
+
+```python
+await client.read_property("pump.rpm")          # e.g. an HTTP GET
+await client.write_property("pump.target_rpm", 1500)
+async for evt in await client.subscribe("pump.overheat"):   # e.g. an MQTT topic
+    ...                              # evt is the payload, e.g. {"temp": 98}
+```
+
+A text LLM, a vision model, or your own code can drive it; `invoke` is the
+same. (`thingctx.from_url(...)` returns a ready `LLMHost` if you just want a
+loop out of the box.)
+
+## Where the TDs live: a registry
+
+A registry is wherever your descriptions come from: a folder of files, a
+URL, or a **Thing Description Directory** (TDD). It is a general source, not
+tied to any one consumer. `ThingClient`, the MCP bridge, and the LLM loop all
+build from the same registry.
+
+```python
+client = thingctx.ThingClient.from_registry(thingctx.from_arg("./examples/registry/"))
+```
+
+The TDD is not a thingctx invention. It is the
+[W3C WoT Discovery](https://www.w3.org/TR/wot-discovery/) standard (a final
+Recommendation): a service that serves a whole fleet of Things from a
+`/things` endpoint, with optional search. thingctx reads from any compliant
+TDD. Point `from_arg` at its URL.
+
+## Authentication
+
+The TD declares the scheme (`bearer`, `basic`, `apikey`); the secret is
+supplied to the invoker at runtime, never in the TD. So a TD is safe to
+commit and share.
+
+```python
+thingctx.HttpInvoker(credentials={"my_token": "secret"})  # key = the scheme name
+```
+
+## License
+
+Apache-2.0. Copyright 2026 The thingctx Authors.

thingctx-0.1.1/pyproject.toml

@@ -0,0 +1,59 @@
+[build-system]
+requires = ["setuptools>=68", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "thingctx"
+version = "0.1.1"
+description = "Drive any agent against any W3C WoT Thing, over any transport. No per-integration server."
+readme = "README.md"
+requires-python = ">=3.10"
+license = { text = "Apache-2.0" }
+authors = [{ name = "The thingctx Authors" }]
+keywords = ["llm", "wot", "web-of-things", "thing-description", "mcp", "tool-calling", "agents"]
+classifiers = [
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "License :: OSI Approved :: Apache Software License",
+]
+# Core is stdlib-only. Everything else is an opt-in extra so the
+# package stays light and dependency-free at its core.
+dependencies = []
+
+[project.optional-dependencies]
+# The LLM loop (any provider via litellm).
+llm = ["litellm>=1.0"]
+# Transports.
+http = ["httpx>=0.25"]
+mqtt = ["paho-mqtt>=2.0"]
+# Validate TDs against the official W3C WoT TD 1.1 schema.
+validate = ["jsonschema>=4.0"]
+# Expose a Thing (or a whole fleet of TDs) to any MCP client.
+mcp = ["mcp>=1.0"]
+# Everything.
+all = ["litellm>=1.0", "httpx>=0.25", "paho-mqtt>=2.0", "jsonschema>=4.0", "mcp>=1.0"]
+dev = ["pytest>=7", "pytest-asyncio>=0.21", "jsonschema>=4.0", "mcp>=1.0", "httpx>=0.25", "ruff>=0.6"]
+
+[project.scripts]
+# Serve a Thing (or a whole fleet of TDs) to any MCP client.
+thingctx-mcp = "thingctx.integrations.mcp:main"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+thingctx = ["data/*.json"]
+
+[tool.pytest.ini_options]
+markers = ["network: hits the network; deselect with -m 'not network'"]
+asyncio_mode = "auto"
+testpaths = ["tests"]
+
+[tool.ruff]
+line-length = 100
+target-version = "py310"
+
+[tool.ruff.lint]
+# pycodestyle errors, pyflakes, import sorting, pyupgrade, bugbear.
+select = ["E", "F", "I", "UP", "B"]

thingctx-0.1.1/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+