Skip to main content
Glama
freesolo-co

Clado MCP Server

by freesolo-co
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Clado MCP Server

No user-submitted related servers found.

    Related Servers

    • Linkd MCP Server

      automcp-app
      A
      license
      A
      quality
      D
      maintenance
      An unofficial Model Context Protocol server that enables programmatic access to LinkedIn data through tools like user search, company search, profile enrichment, and contact retrieval.
      7
      67 npm
      3
      ISC

    • LinkedIn MCP Server

      Hritik003
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables seamless interaction with LinkedIn for job applications, profile retrieval, feed browsing, and resume analysis through natural language commands.
      34
      -

    • LinkedIn MCP Server

      baptitse-jn
      F
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive Model Context Protocol server that enables AI assistants to interact with LinkedIn APIs for profile management, content creation, networking, messaging, and analytics.
      2
      -

    • EnrichB2B MCP Server

      moonlabsai
      F
      license
      Not graded
      quality
      D
      maintenance
      A server implementing the Model Context Protocol that enables users to retrieve LinkedIn profile information and activity data via EnrichB2B API, and generate text using OpenAI GPT-4 or Anthropic Claude models.
      1
      -

    • LinkedIn MCP Server

      anubisalpha
      A
      license
      Not graded
      quality
      D
      maintenance
      A ToS-compliant Model Context Protocol server for LinkedIn that uses the official API for OAuth 2.0 authentication, profile reading, and content posting.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 5 tools

    Disambiguation3/5

    The tools have some overlap in purpose, particularly between 'enrich_linkedin' and 'scrape_linkedin', which both retrieve LinkedIn profile data, though 'scrape_linkedin' includes posts and comments. 'retrieve_contacts' focuses on contact information, while 'linkedin_post_reactions' and 'search_for_users' are more distinct. Descriptions help differentiate them, but confusion could arise between the profile-focused tools.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (e.g., 'enrich_linkedin', 'scrape_linkedin', 'search_for_users'), which is clear and predictable. However, 'retrieve_contacts' uses 'retrieve' instead of a more aligned verb like 'get' or 'enrich', causing a minor deviation. Overall, the naming is mostly consistent and readable.

    Tool Count5/5

    With 5 tools, the count is well-scoped for a LinkedIn-focused server, covering key operations like profile enrichment, contact retrieval, post analysis, and user search. Each tool appears to serve a distinct purpose, and the number is neither too sparse nor overwhelming for the domain.

    Completeness4/5

    The tool set covers core LinkedIn data retrieval functions, including profile enrichment, contact information, post engagement, and user search. Minor gaps exist, such as the lack of tools for updating or managing data (e.g., no 'create_contact' or 'delete_profile'), but agents can likely work around these for typical lookup and analysis tasks.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing

    Resources