A
licenseA
qualityB
maintenanceEnables automated LinkedIn growth by posting, commenting, and managing connections through Claude Code, with daily scheduled tasks for inbox replies and connection requests.
17
MIT
Iridium
Ownership verified
Server Details
LinkedIn outreach, commenting, scheduling, and data via Claude and human approval gates.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
C2.2/5.0
Tool DescriptionsD
Average 2.5/5 across 42 of 42 tools scored. Lowest: 1/5.
Server CoherenceB
Disambiguation2/5
Many tools have overlapping purposes, especially the draft management tools (e.g., approve_draft vs approve_comment_draft, list_drafts vs list_comment_drafts) which create ambiguity. The four LinkedIn connection methods are all distinct but could be confusing. Overall, an agent would struggle to consistently pick the right tool.
Naming Consistency4/5
The naming convention is largely consistent snake_case with verb_noun pattern (e.g., approve_comment_draft, get_linkedin_profile). Minor deviations like cancel_scheduled (verb_adjective) and schedule_manual_dm (longer noun phrase) but no style mixing. Very readable.
Tool Count3/5
42 tools is on the high side for a LinkedIn automation server. While the scope is broad, many tools are redundantly split by draft type (comment, content, general). The count feels heavy but not extreme; a more consolidated design would improve coherence.
Completeness3/5
Core workflows (connection, prospect discovery, outreach, commenting, scheduling, account management) are covered, but there are notable gaps: no ability to manually create a draft, no permanent delete for drafts, no immediate send message (only scheduled), and no sequence management beyond creation. The surface is workable but incomplete.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityCmaintenanceEnables running the entire LinkedIn sales motion inside Claude Code, including content creation, audience warming, outreach, and booking calls.6MIT
- Alicense-qualityCmaintenanceAI-powered LinkedIn automation server for content generation, profile/company data extraction, and connection request automation, integrating with MCP clients like Claude Desktop.MIT
- AlicenseBqualityDmaintenanceIntegrates with Claude to enable LinkedIn post creation, profile optimization, content generation, and analytics through natural language.13131MIT