Pangolin MCP Connector
Related Servers
Alternatives to Pangolin MCP Connector
No user-submitted related servers found.
Related Servers
FlicenseNot gradedqualityBmaintenanceServes sigit.si account, repository, issue, pull request, code-search, session, hook, and billing operations to AI agents over stdio, reusing the token stored by the CLI login and defaulting repository tools to the checkout the agent is pointed at. Tool lists can be trimmed with read-only mode or toolset selection, and a hosted HTTP endpoint offers the same tools.6-- AlicenseCqualityBmaintenanceEnables MCP clients to inspect and manage Semaphore UI automation through its management API, covering projects, templates, tasks, logs, inventories, repositories, and related configuration. It works over stdio or Streamable HTTP with schema-validated tools, read-only mode, project allowlists, and a bounded task-wait helper.213MIT
- AlicenseBqualityBmaintenanceConnects MCP clients to a self-hosted Seafile server through the seahub HTTP API, exposing libraries, files, search, sharing, and optional admin operations over stdio or Streamable HTTP. It defaults to read-focused tools and gates writes behind confirmation, with token redaction and dry-run previews.4MIT

Evo CRM MCPofficial
AlicenseBqualityBmaintenanceEnables assistants to read and modify contacts, conversations, messages, pipelines, tasks, inboxes, and AI agents through the CRM REST API, using separate read-only or read-write tool sets. Runs over local stdio or stateless Streamable HTTP with token-based scope separation.17MIT- AlicenseNot gradedqualityBmaintenanceEnables AI agents and MCP clients to manage projects, merge requests, issues, pipelines, wiki, releases, tags, milestones, and more through stdio, SSE, or Streamable HTTP with PAT/OAuth authentication.226,557 npmMIT
- AlicenseAqualityCmaintenanceEnables managing a self-hosted media library through its HTTP API, with scoped toolsets, confirm-gated writes, dry-run previews, and read caching. Supports libraries, items, collections, playlists, podcasts, sessions, stats, tags, genres, and administrative operations.13MIT
TDQS
Scored across 6 tools
At the top level, the six tools split cleanly by domain (resources, sites, orgs, roles, targets, users), so an agent can usually pick the right tool. However, pangolin_resources is a 123-operation dispatcher containing near-identical parallel families (add_resource_users vs add_site_resource_users vs add_private_resource_users vs add_public_resource_users), and the private/public/site-resource variants are genuinely hard to distinguish without reading long descriptions.
Tool names follow one clean pattern: pangolin_<plural domain>, which is easy to predict. Inside the action lists the verb_noun convention mostly holds, but there are outliers such as regenerate_re_key_site_secret, get_org_site_resource_nice, list_org_site_resources_org_id, and update_org_create_invite that break the pattern.
Six tools is a reasonable surface count for a Pangolin connector, and grouping by domain avoids dozens of tiny tools. But each tool absorbs 3-123 operations, with pangolin_resources alone holding 123 actions, which pushes the effective selection burden far beyond what 6 tools suggests.
Coverage is broad: CRUD for resources, sites, orgs, roles, users, plus rules, targets, whitelist, access tokens, mTLS, AI providers/models, and site lifecycle (approve/reject/restart). Targets lack a create operation on their own toolset (created via the resource toolsets), which is a minor gap an agent can work around.