PLS-MCP Server
Related Servers
Alternatives to PLS-MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceMCP server that exposes OneMap8 fleet tracking to AI clients, enabling natural-language queries about devices, positions, reports, geofences, drivers, and more. Includes 32 tools, permission scoping, and safety guardrails.-
- AlicenseAqualityFmaintenanceMCP server for industrial PLC integration, enabling AI to read tags, monitor alarms, and interact with Allen-Bradley ControlLogix PLCs via natural language.9MIT
- AlicenseNot gradedqualityDmaintenanceA powerful AI service platform that provides complete MCP tool calling capabilities and RAG knowledge base functionality, enabling users to connect to multiple MCP servers and perform intelligent document search.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceThis MCP server enables AI agents to read MQTT and Sparkplug B data via tools like list_topics, get_latest, and read_all, providing read-only access to latest sensor values.1MIT
- AlicenseAqualityCmaintenanceAn MCP server that enables AI models to query FOFA, 360 Quake, and Hunter cyberspace mapping platforms for asset discovery and security research. It supports natural language parameter configuration and provides comprehensive search tools for retrieving IP, port, and domain data.321 PyPI7MIT
- AlicenseCqualityDmaintenanceMCP server for the AIRIOT IoT platform, enabling AI assistants to manage data tables, records, devices, alarms, files, and more through natural language.602 npm1MIT
TDQS
Scored across 66 tools
Most tools have clear, distinct purposes (e.g., list_tags vs. get_tag_location). However, some query overlap exists, such as list_personnel and search_personnel, and list_alarms with get_unread_alarms, which could cause minor confusion.
Tool names use different prefixes (list_, get_, pls_, search_, export_) with no uniform pattern. While management tools consistently use pls_<action>_<entity>, the mix of get_ and list_ for queries reduces consistency.
66 tools is high but justified by the complex domain (CRUD for many entities, queries, batch operations, diagnostics). Still, it exceeds the typical well-scoped range, making the surface feel heavy.
Core CRUD and query operations for main entities (tags, personnel, vehicles, etc.) are present. However, missing operations like marking alarms read, managing departments (CRUD), and a dedicated list_buildings tool leave notable gaps.