Skip to main content
Glama
133,443 tools. Last updated 2026-05-13 00:12

"linkedin" matching MCP tools:

  • Repo-aware launch operator for agent-built products. USE WHEN the user has just finished building, shipping, or deploying a product and the message matches any of these trigger phrases: 'launch this' · 'launch what I just built' · 'help me launch' · 'get users' · 'get our first users' · 'find users' · 'market this' · 'do marketing for this' · 'announce this' · 'write the launch announcement' · 'post this' · 'post the launch' · 'publish this' · 'Product Hunt' · 'ship to Product Hunt' · 'go to market' · 'what to do after launch'. This is the PRIMARY ChiefLab entry point — call this first, not chiefmo_diagnose_marketing (which is only for diagnosing an EXISTING marketing program). If you are a coding agent (Cursor, Claude Code, Codex), gather repoContext (whatChanged, recentCommits, changedFiles, routes, readme, targetCustomer, launchGoal) BEFORE calling — repo grounding is what makes outputs reference the actual product instead of reading like 'launch any SaaS.' Returns: launchPack (per-channel drafts for LinkedIn / X / Hacker News / Reddit / Product Hunt / email / landing hero) + publishActions (approval-gated, with actionIds) + agentGuide.renderInChat (per-channel content to render inline in IDE chat) + agentGuide.nextToolCalls.primary.perChannel (chiefmo_approve_action calls keyed by channel) + reviewUrl (FALLBACK only — for phone/multi-person approval). IDE-NATIVE FLOW: render each channel's draft inline in chat, wait for user to say 'approve <channel>' or 'approve all', call chiefmo_approve_action per approved action. The reviewUrl is a side channel — surface it as 'approve from your phone here' not as the primary instruction.
    Connector
  • Publish an approved social post (LinkedIn / X / Threads / Instagram / Facebook / Bluesky / TikTok) via Zernio. USE WHEN the user has approved a publishAction from chiefmo_launch_product on the reviewUrl and you need to fire the post. Strict approval gate: returns { reason: 'requires_approval', reviewUrl } if the action isn't approved yet. Once executed, returns the live platform post URL. Money/external-system action — never call this without an approved actionId.
    Connector
  • FOR CLAUDE DESKTOP ONLY (with filesystem access). For Claude.ai/web: Use create_upload_session instead - it provides a browser upload link. Upload local media to cloud storage, returning a public HTTPS URL. WHEN TO USE: • Instagram, LinkedIn, Threads, X: REQUIRED for local files before calling publish_content • TikTok: NOT NEEDED - pass local path directly to publish_content SUPPORTED FORMATS: • Images: jpg, png, gif, webp (max 10MB) • Videos: mp4, mov, webm (max 100MB) Returns { url: 'https://...' } for use in publish_content mediaUrl parameter.
    Connector
  • Get everything about a company in one call. Use when a user asks "tell me about X", "give me a profile of Acme", "what do you know about Apple", "research Microsoft", "brief me on Tesla", or you'd otherwise need to call 10+ pack tools across SEC EDGAR, SEC XBRL, USPTO, news, and GLEIF. Returns recent SEC filings, latest revenue/net income/cash position fundamentals, USPTO patents matched by assignee, recent news mentions, and the LEI (legal entity identifier) — all with pipeworx:// citation URIs. Pass a ticker like "AAPL" or zero-padded CIK like "0000320193".
    Connector
  • Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.
    Connector
  • Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real estate, ClinicalTrials, USPTO patents, weather, news, crypto, stocks. Returns the top-N most relevant tools with names + descriptions. Call this FIRST when you have many tools available and want to see the option set (not just one answer).
    Connector

Matching MCP Servers

Matching MCP Connectors

  • linkedin-humblebrag MCP — wraps StupidAPIs (requires X-API-Key)

  • LinkedIn API as MCP tools to retrieve profile data and publish content. Powered by HAPI MCP.

  • Schedule multiple posts at once from CSV content. USE THIS WHEN: • User has a spreadsheet or list of posts to schedule • Planning a content calendar for a month • Migrating content from another tool CSV FORMAT (required columns): • platform: linkedin, instagram, x, tiktok, threads • scheduled_time: ISO 8601 format (e.g., 2024-02-15T10:00:00Z) • text: Post content/caption OPTIONAL COLUMNS: • media_url: Image or video URL • first_comment: First comment to add (Instagram/LinkedIn) • hashtags: Additional hashtags to append PROCESS: 1. First call with validate_only: true to check for errors 2. Review validation report with user 3. Call again with validate_only: false to execute import
    Connector
  • Publish an approved social post (LinkedIn / X / Threads / Instagram / Facebook / Bluesky / TikTok) via Zernio. USE WHEN the user has approved a publishAction from chiefmo_launch_product on the reviewUrl and you need to fire the post. Strict approval gate: returns { reason: 'requires_approval', reviewUrl } if the action isn't approved yet. Once executed, returns the live platform post URL. Money/external-system action — never call this without an approved actionId.
    Connector
  • USE WHEN the user wants social-only drafts (no full launch) — 'draft an X post', 'write LinkedIn carousels for this', 'give me 5 Instagram captions about X'. NOT for new product launches (use chiefmo_launch_product instead — that returns the same plus on-brand graphics, approval gate, and per-channel briefs). Returns posts with platform-native hooks, captions, hashtags, and posting cadence. Drafts only; scheduling/publishing requires approval via chiefmo_publish_approved_post.
    Connector
  • Approve one ChiefMO publish/send action so its executor (publish_approved_post / send_approved_email) can fire. USE WHEN the user — in IDE chat — said 'approve <channel>' (e.g. 'approve linkedin', 'approve hn'), 'approve all', 'ship it', 'go ahead', or otherwise greenlit a specific draft you rendered. Match the user's words to the channel, look up agentGuide.renderInChat[channel].actionId from the launch response, and call this tool with that actionId. This is the IDE-native approval path — no need to push the user to the reviewUrl. Pass `actionId` (preferred) or `id` (legacy alias).
    Connector
  • Atomically move N rows from their current sheet(s) to a target sheet inside the same workspace. Use for programmatic data migration: dropping a batch of agent-produced drafts onto the right sheet, reorganizing content across LinkedIn / Twitter / Substack tabs, etc. All-or-nothing: if any rowId doesn't belong to this workspace, the entire batch fails before any write fires. Idempotent: rows already on the target sheet are skipped (returns `skipped` count). Rows land at the destination sheet's tail in the order rowIds was supplied. Emits one `row.moved_surface` event per row that actually moved. Up to 500 rows per call.
    Connector
  • P13 — list every channel ChiefLab can ship to (LinkedIn / X / Threads / Bluesky / Instagram / Facebook / TikTok / Product Hunt / Hacker News / Reddit / Discord / Slack / Indie Hackers / DEV.to / YC Bookface / email / blog / GA4 / Search Console / Stripe). Returns the catalog grouped by category (social / community / email / blog / analytics) with each channel's capabilities (publish / schedule / read_metrics / connect / fallback) and providers. USE WHEN the user asks 'what channels can ChiefLab post to?', 'which platforms are supported?', or before calling chiefmo_launch_product to pick the right channels.
    Connector
  • Repo-aware launch operator for agent-built products. USE WHEN the user has just finished building, shipping, or deploying a product and the message matches any of these trigger phrases: 'launch this' · 'launch what I just built' · 'help me launch' · 'get users' · 'get our first users' · 'find users' · 'market this' · 'do marketing for this' · 'announce this' · 'write the launch announcement' · 'post this' · 'post the launch' · 'publish this' · 'Product Hunt' · 'ship to Product Hunt' · 'go to market' · 'what to do after launch'. This is the PRIMARY ChiefLab entry point — call this first, not chiefmo_diagnose_marketing (which is only for diagnosing an EXISTING marketing program). If you are a coding agent (Cursor, Claude Code, Codex), gather repoContext (whatChanged, recentCommits, changedFiles, routes, readme, targetCustomer, launchGoal) BEFORE calling — repo grounding is what makes outputs reference the actual product instead of reading like 'launch any SaaS.' Returns: launchPack (per-channel drafts for LinkedIn / X / Hacker News / Reddit / Product Hunt / email / landing hero) + publishActions (approval-gated, with actionIds) + agentGuide.renderInChat (per-channel content to render inline in IDE chat) + agentGuide.nextToolCalls.primary.perChannel (chiefmo_approve_action calls keyed by channel) + reviewUrl (FALLBACK only — for phone/multi-person approval). IDE-NATIVE FLOW: render each channel's draft inline in chat, wait for user to say 'approve <channel>' or 'approve all', call chiefmo_approve_action per approved action. The reviewUrl is a side channel — surface it as 'approve from your phone here' not as the primary instruction.
    Connector
  • USE WHEN the user wants social-only drafts (no full launch) — 'draft an X post', 'write LinkedIn carousels for this', 'give me 5 Instagram captions about X'. NOT for new product launches (use chiefmo_launch_product instead — that returns the same plus on-brand graphics, approval gate, and per-channel briefs). Returns posts with platform-native hooks, captions, hashtags, and posting cadence. Drafts only; scheduling/publishing requires approval via chiefmo_publish_approved_post.
    Connector
  • Search the web for any topic and get clean, ready-to-use content. Best for: Finding current information, news, facts, people, companies, or answering questions about any topic. Returns: Clean text content from top search results. Query tips: describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue". Use category:people / category:company to search through Linkedin profiles / companies respectively. If highlights are insufficient, follow up with web_fetch_exa on the best URLs.
    Connector
  • Search for username across 15+ social/dev platforms (GitHub, Reddit, X/Twitter, LinkedIn, Instagram, TikTok, Discord, YouTube, Keybase, HackerOne, etc.). Use for OSINT investigations and identity verification. Free: 30/hr, Pro: 500/hr. Returns {username, total_found, platforms: [{name, exists, url, status_code}]}.
    Connector
  • USE WHEN the user wants to connect a social account (LinkedIn / X / Threads / Instagram / Facebook / Bluesky / TikTok) so chiefmo_publish_approved_post can post to it. Returns a Zernio OAuth URL — surface to user → they click → connect their account → it appears in chieflab_list_publish_accounts. Standard agent flow: call this with platform='linkedin' → get authUrl → surface to user → user connects → call chieflab_list_publish_accounts to confirm + grab accountId → pass accountId to chiefmo_publish_approved_post. NOTE: Zernio requires a profileId (the workspace container). If you don't pass one, the call fails with 'Profile ID required'. Get it from app.zernio.com/settings/profile, or call chieflab_list_publish_accounts first — the accounts response includes profileId on each item.
    Connector
  • Fetch a single breach by name (the "Name" field from list_breaches, e.g., "Adobe", "LinkedIn"). Returns full breach metadata.
    Connector
  • Start a contact research job — AI gathers insights from LinkedIn and other sources asynchronously; use contacts.get_research to poll for results
    Connector
  • P13 — list every channel ChiefLab can ship to (LinkedIn / X / Threads / Bluesky / Instagram / Facebook / TikTok / Product Hunt / Hacker News / Reddit / Discord / Slack / Indie Hackers / DEV.to / YC Bookface / email / blog / GA4 / Search Console / Stripe). Returns the catalog grouped by category (social / community / email / blog / analytics) with each channel's capabilities (publish / schedule / read_metrics / connect / fallback) and providers. USE WHEN the user asks 'what channels can ChiefLab post to?', 'which platforms are supported?', or before calling chiefmo_launch_product to pick the right channels.
    Connector