Skip to main content
Glama
Sign In
gtm-api: LinkedIn MCP Server

gtm-api: LinkedIn MCP Server

by gtm-api
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to gtm-api: LinkedIn MCP Server

No user-submitted related servers found.

    Related Servers

    • linkedin-mcp

      rzere
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that lets AI agents operate a real LinkedIn account in plain English with safety controls and approval queues.
      15 npm
      1
      MIT
    • LinkMCP

      LinkMCPofficial

      linkmcp-io
      A
      license
      Not graded
      quality
      A
      maintenance
      Hosted LinkedIn MCP server that connects your own LinkedIn account to any MCP client, providing 33 tools for research, search including Sales Navigator, profiles, inbox, posts, connections, and email or mobile finding. Enables AI-driven prospecting, outreach, engagement, and recruiting workflows with built-in rate limits and account safety.
      3
      MIT

    • LinkedIn Buddy

      sigvardt
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for LinkedIn automation that enables AI agents to perform LinkedIn actions (search, inbox, feed, jobs, etc.) safely with human-like evasion and two-phase commit preview.
      3 npm
      3
      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.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools form an explicit, non-overlapping discovery→inspection→invocation pipeline, and each description states its position in that sequence. There is no realistic way to confuse listing toolsets, listing tools in a toolset, and invoking a tool.

    Naming Consistency4/5

    All names are snake_case verb_noun pairs (list_toolsets, get_toolset_tools, call_tool), which is predictable and readable. The only minor wrinkle is that the object noun shifts between 'toolsets' and 'tool', though the intent is obvious from context.

    Tool Count4/5

    Three tools is at the low end, but for a dynamic gateway that proxies an unbounded catalog, a small fixed surface is exactly right and each tool earns its place. Nothing is redundant or missing at the plumbing layer.

    Completeness4/5

    Discovery, schema retrieval (lite vs verbose), and execution including the preview→confirm commit_token flow and team_sid override are all covered. Minor gaps: no cross-toolset keyword search and no dedicated authorization/introspection tool, so an agent must walk toolsets sequentially to find a capability.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Resources