{"id":"doubleslashde-thingworx-mcp-server","name":"thingworx-mcp-server","homepage":null,"repo_url":"https://github.com/doubleSlashde/thingworx-mcp-server","category":"ai-ml","subcategories":[],"tags":["mcp","thingworx","iot","spring-boot","java","ai-tools","redis","caching","integration"],"what_it_does":"Provides a Spring Boot MCP server that exposes PTC ThingWorx entities (Things, Properties, Services, and Collections) as AI-friendly tools/endpoints. It uses ThingWorx REST API access with AppKey authentication and includes Redis-backed caching with runtime toggles, configurable via environment variables, and Docker support.","use_cases":["Building LLM/AI agents that can list ThingWorx Things and metadata","Enabling agents to read property values and invoke ThingWorx services","Rapid prototyping of an “AI-friendly” integration layer on top of ThingWorx","Local or cloud deployment of a tool server that fronts ThingWorx"],"not_for":["Production systems without review/hardening (repo describes itself as experimental)","Environments requiring strict enterprise compliance guarantees","Use cases needing advanced agent workflow management beyond tool invocation"],"best_when":"You want an MCP-compatible tool server to front ThingWorx for development/evaluation and you can supply a ThingWorx AppKey plus (optionally) a Redis cache.","avoid_when":"You cannot ensure secure handling of the AppKey and you do not control network exposure of the MCP server endpoints (e.g., open to the public).","alternatives":["Direct ThingWorx REST API integration from your agent/orchestration layer","Using an existing ThingWorx-to-MCP connector (if available internally)","Building a custom MCP server that wraps ThingWorx APIs with tighter security controls and explicit error/retry semantics"],"af_score":43.0,"security_score":34.5,"reliability_score":21.2,"package_type":"mcp_server","discovery_source":["github"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T20:02:40.101266+00:00","interface":{"has_rest_api":true,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":"http://localhost:8081/mcp","has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["ThingWorx AppKey via environment variable THINGWORX_APP_KEY"],"oauth":false,"scopes":false,"notes":"Auth for ThingWorx is described as AppKey authentication. The README does not describe any authentication/authorization mechanism for clients calling the MCP server itself."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing model described (open-source repository; cost depends on your deployment and infrastructure like Redis/ThingWorx)."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":43.0,"security_score":34.5,"reliability_score":21.2,"mcp_server_quality":60.0,"documentation_accuracy":40.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":70.0,"rate_limit_clarity":10.0,"tls_enforcement":20.0,"auth_strength":45.0,"scope_granularity":20.0,"dependency_hygiene":35.0,"secret_handling":50.0,"security_notes":"Uses ThingWorx AppKey provided via environment variable, which is a reasonable secret-distribution pattern. However, the README does not state whether the MCP server enforces TLS/HTTPS or authenticates clients of its own endpoints, nor does it describe rate limiting, scope granularity, or secure logging practices. Caching to Redis introduces additional risk if Redis is exposed or misconfigured.","uptime_documented":0.0,"version_stability":35.0,"breaking_changes_history":30.0,"error_recovery":20.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Repository is described as experimental; behavior/edge cases may require testing.","No documented retry/idempotency guidance is provided in the README.","MCP endpoint configuration exists but details about tool schemas, error formats, and rate limits are not shown in the provided README snippet."]}}