A
licenseNot graded
qualityD
maintenanceAn MCP server that allows Claude Desktop to remotely control Claude Code instances for executing commands and managing files.
179 npm
GPL 3.0
headlo-mcp
Officialby headlohq
Related Servers
Alternatives to headlo-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA modern MCP server that provides Claude Desktop with the ability to store and retrieve personal information locally.1MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that provides access to over 100 development skills for frontend, backend, integration, design, devops, and process categories via Claude Code and other MCP clients.-
- FlicenseBqualityDmaintenanceAn MCP server that enables Claude Desktop to communicate with A2A protocol agents, allowing Claude to access extended capabilities through agent interactions.322-
- AlicenseCqualityDmaintenanceAn MCP server that provides seamless integration with Claude Desktop for querying and managing timeseries data in GigAPI Timeseries Lake.76Apache 2.0
- AlicenseNot gradedqualityCmaintenanceA local MCP server for Claude Desktop with persistent task management, file operations, document generation, and PDF indexing.334 npm1MIT
TDQS
C2.8/5.0
Scored across 25 tools
Disambiguation4/5
Most tools have a clear and distinct resource+action purpose (e.g., create_record vs update_record, list_pages vs create_page). The main confusion risk is between list_page_modules and list_modules_editor, which differ only by auth context, and possibly get_module vs list_page_modules, though the singular/plural distinction helps.
Naming Consistency3/5
The dominant pattern is verb_noun (get_context, create_site, update_record), but there are notable deviations: 'cap_capture_expert' and 'cap_edit_expert' use a prefix and less predictable structure, and 'list_modules_editor' is inconsistent with 'list_page_modules'. Overall still readable but not uniform.
Tool Count4/5
25 tools is at the high end but well-justified given the server covers multiple domains: onboarding, sites, pages, collections, records, modules, and expert protocols. Each tool serves a distinct purpose, though the count feels slightly heavy for a single server.
Completeness2/5
There are significant lifecycle gaps: no delete or update for sites, no delete for pages, no delete for collections, and no get_collection or update_site. Records and modules have full CRUD, but the broader content model lacks essential operations that agents would likely need.
Maintenance
ActivityInactive
ResponsivenessNo issues