paperclip-mcp
Related Servers
Alternatives to paperclip-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceLocal MCP server (stdio) exposing the entire Hetzner Cloud API as 201 typed tools, read and write20256 npmMIT
- AlicenseNot gradedqualityCmaintenanceTurns any API with an OpenAPI 3.0/3.1/3.2 spec into callable MCP tools: it generates a tool per supported operation, validates arguments, and forwards authenticated requests, served over stdio or local HTTP or embedded as a library. No hand-written tool per endpoint is required.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that exposes FortiCNAPP (formerly Lacework) API 2.0 operations as typed, auth-aware tools generated from the API spec at startup, supporting both local stdio and remote Streamable HTTP transports.MIT
- AlicenseNot gradedqualityCmaintenanceTurns any OpenAPI 3.0 or 3.1 document (local file or URL) into typed MCP tools served over stdio, so AI assistants can invoke upstream HTTP API endpoints directly. Handles authentication headers, request validation, and bounded responses for clients like Claude Desktop, Cursor, and VS Code.536 npmMIT
- AlicenseNot gradedqualityCmaintenanceServes any OpenAPI 3.x/Swagger 2.x API as a local MCP server over stdio, converting every operation into a tool that proxies requests to the upstream API with configurable headers and fixed parameters.6 npm1MIT

agnara-mcpofficial
AlicenseNot gradedqualityCmaintenanceEnables MCP clients to discover and invoke Agnara capabilities over stdio, with schema-projected tools and fail-closed authorization.MIT
TDQS
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.