Skip to main content
Glama
Sign In
sindhujaIBM

linkedin-mcp

by sindhujaIBM
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to linkedin-mcp

No user-submitted related servers found.

    Related Servers

    • Social MCP

      veluralabs
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to publish, edit, delete, comment on, and analyze posts across LinkedIn, Facebook Pages, and Instagram professional accounts, including cross-posting and local scheduling. Runs locally with user-supplied credentials and no third-party token routing.
      34 npm
      MIT

    • Facebook MCP

      thenavidm
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to manage Facebook Pages through Meta's Graph API, including posting, scheduling, drafts, reading insights, and moderating comments.
      15
      41 npm
      2
      MIT

    • facebook-mcp-server

      awakenorigins
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage Facebook Pages through the Graph API, including creating posts, moderating comments, fetching page and post insights, and filtering negative feedback.
      MIT
    • SocialAPIs: Facebook & Instagram Data by SocialAPIsHub

      SocialAPIs: Facebook &official

      SocialAPIsHub
      A
      license
      A
      quality
      C
      maintenance
      Public Facebook & Instagram data for AI agents: pages, groups, posts, comments, search, Meta Ads Library, Marketplace, media downloads, Instagram profiles, posts, reels and locations. 12 read-only tools, 51 operations. Hosted at mcp.socialapis.io/mcp or npx @socialapis/mcp. Free tier with 200 requests/month, plans from $4.99/month.
      12
      392 npm
      2
      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

    A4.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a clearly different action and resource: posting to a profile, posting to a company page, commenting, listing recent posts, and fetching analytics. There is no meaningful overlap or ambiguity between the tools.

    Naming Consistency5/5

    All tool names follow the same snake_case verb-first convention, with clear patterns like post_to_* and get_*. The naming is predictable and makes the purpose of each tool immediately obvious.

    Tool Count5/5

    Five tools is well-scoped for a LinkedIn content publishing and engagement server. Each tool covers a distinct core operation without unnecessary bloat or missing essentials.

    Completeness4/5

    The set covers the main lifecycle for LinkedIn posting: create posts, comment, retrieve recent posts, and view analytics. Delete and update operations are absent, but they are not core to the apparent purpose of publishing and measuring engagement.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources