baselinker-mcp
Related Servers
Alternatives to baselinker-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceFree, minimal REST API wrapper as an MCP server that lets your AI agent call any API.MIT
- AlicenseNot gradedqualityFmaintenanceFree Polish VAT invoice generation MCP server with PDF output and preview. No API key required.61 npm1MIT
- AlicenseBqualityCmaintenanceA free, open-source MCP server that connects AI assistants to the Tiendanube/Nuvemshop API so they can manage products, variants, stock, orders, fulfillment, customers, coupons, shipping, payments, content and webhooks from plain-language requests. It exposes 191 tools across 39 API resources, with a read-only mode, honest tool annotations and rate-limit-aware, context-friendly responses.1911MIT
- AlicenseAqualityBmaintenanceMCP server for discovering and calling 400+ practical APIs through six compact tools, with free catalog search and pay-per-call x402 execution on Base.6197 npmMIT
- AlicenseCqualityDmaintenanceOpen-source MCP server for Olist/Tiny ERP API V2, exposing 92 REST endpoints as individual tools with input schemas and write protection.92MIT
- AlicenseBqualityBmaintenanceLightweight ClickUp MCP server for task management with 37 tools and token-optimized responses to reduce API verbosity.40146 npm4MIT
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one discovers available API methods and the other invokes them. There is no overlap or ambiguity in selecting between them.
Both tools share the baselinker_ prefix and use snake_case, but baselinker_call is a bare verb while baselinker_list_methods follows a verb_noun pattern. This is a minor inconsistency rather than a chaotic naming scheme.
At two tools, this is slightly below the typical 3-15 range, but each tool earns its place for a generic API bridge: one for discovery and one for execution. The count is minimal without feeling incomplete.
The generic baselinker_call provides access to every BaseLinker API method, so there are no missing CRUD or lifecycle operations. The baselinker_list_methods tool covers the discovery gap that would otherwise leave agents guessing at method names.