No user-submitted related servers found.
Scored across 592 tools
Although each tool maps to a unique API operation, the tool set is so large and densely populated with similar path-shaped names that agents will struggle to pick the right one. Many tools are truncated with opaque hash suffixes (e.g. pc_post_companies_by_company_id_teams_catalog_by_cata_b8530c21a4), and there are multiple overlapping 'list skills' and 'list secrets' variants across different scopes.
The dominant pc_<verb>_<path> snake_case convention is consistent and recognizable, but the pattern is undermined by inconsistent path-parameter naming (by_id vs by_company_id vs by_issue_id), hash-suffixed truncations, legacy routes, and two non-pc meta-tools (paperclip_list_operations, paperclip_call_operation). The structure is predictable in theory but noisy in practice.
592 tools is an extreme mismatch for an MCP server. Even if each one faithfully mirrors an API endpoint, the surface is far too large for an agent to browse and select from effectively, and it dwarfs the typical well-scoped server size.
The server covers an unusually broad domain with CRUD and lifecycle operations for companies, issues, projects, goals, routines, skills, secrets, adapters, plugins, environments, tools, and more, plus discovery helpers. Minor completeness blemishes exist, such as legacy error-returning tools and a few subresources without full lifecycle coverage, but for a full API surface the coverage is strong.