Agent Connectors MCP server
Related Servers
Alternatives to Agent Connectors MCP server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to list, search, inspect, and recommend publicly available, ready-to-use AI products and interactive experiences through a read-only remote MCP endpoint.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to browse a read-only catalog of published products and their documented interfaces, listing entries, fetching one by stable ID, and searching names, descriptions, and limitations with optional protocol filters. It also exposes the versioned manifest as a resource and a prompt that helps clients match a task to catalog entries without inventing unsupported capabilities.MIT
- AlicenseNot gradedqualityBmaintenanceProvides read-only access to Mediawork's public directory of post-production and distribution vendors, FAQ, blog, and subscription plans through standardized MCP tools for searching and fetching records.MIT
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server that lets clients search and retrieve AI agent listings and categories from the AgenticList directory.MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables users to search and discover over 500 AI agent endpoints and x402 APIs directly from MCP-compatible clients like Claude and Cursor. It provides tools to query endpoints by keyword, category, or capability while offering access to detailed provider statistics.-
- AlicenseBqualityAmaintenanceEnables any MCP client to search, read, and install free Aura components, agent skills, images/clips, and DESIGN.md systems straight from the public catalogue over stdio, with no account, OAuth, or API key needed. It also returns install plans, token starters, starter kits, and trending/category data so agents can assemble landing pages and UI sections in a few calls.3549 npm6MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: search_tools returns multiple catalogue matches, get_tool fetches a single listing by slug, and list_categories enumerates categories. The descriptions even explicitly clarify that search/get do not run servers, further separating read-only lookup semantics.
All three names follow a clean verb_noun snake_case pattern (search_tools, get_tool, list_categories). No mixed conventions or vague verbs.
Three tools is a reasonable, well-scoped surface for a read-only directory/lookup server, with no redundancy. It is on the thin side and could justify one more browsing tool, but nothing is gratuitous.
Search, single-slug lookup, and category enumeration cover the basic browse flow, but list_categories only returns counts with no obvious tool to fetch listings within a category (unless search supports that filter). This leaves a potential browse-by-category dead end, though agents can likely work around it via search.