Skip to main content
Glama
719,354 tools. Updated 2026-10-29 13:44

"A service for finding GitHub users on LinkedIn" matching MCP tools:

  • <summary>Attach a file from the user's library to a queued outreach email or LinkedIn message. Only attach when the user explicitly asks to attach a specific file to someone's message — never on your own initiative. attachment_id comes from list_attachments. Name the queued message by exactly one handle: recipient_email for a queued email (pending or awaiting approval); target_provider_id for a queued LinkedIn message, or target_identifier for one whose profile is still resolving — both as shown on the row in manage_linkedin_invite_queue's status read. On LinkedIn only messages carry files, not connection requests or InMails, and LinkedIn takes fewer file types than email; a file the channel can't send is refused with the reason. The same file can be attached to several messages.</summary> <returns> <description>The attached file's name and every file now on that message, shaped `{'attached': True, 'filename', 'attachments': [{'id', 'filename', 'mime_type', 'size'}]}`.</description> </returns>
    ConnectorOAuth
  • LinkedIn posts matching a keyword, ranked by LinkedIn's own search. Use when: "what is being said about X on LinkedIn", finding the people posting about a category. Not for: one company's posts, use linkedin_get_company_posts. Finding people to contact, use leads_search_people. Returns: List, ranked. rows[]: posts with author and author_followers, created_at, text (cut at 2000 characters), likes, comments, shares, saves, views, media, duration_s, links, transcript and top_comments[]. top_comments are up to 10 commenters per post with their profile URLs, so one page names the people engaging with a topic; transcript is what a video post says. media is video only for a video stream; a photo, a document carousel or a GIF reads image. null or empty = the platform does not publish it. created_at is approximate: the platform shows an age such as "3 weeks ago", so it is exact only to that unit. Cost: 1 credit per page. Cached 6 hours. Example: {"query": "rfp automation", "since": "week"}
    ConnectorAPI key
  • The comments LinkedIn shows on one post, each with the commenter's profile URL. Use when: pulling the people who engaged with a post: a competitor's launch, a thought leader in your category, your own post. Each author_url goes straight into linkedin_get_profile or leads_get_person. Not for: every comment on a busy post (LinkedIn shows up to 10 to a logged-out reader, so a post with 200 comments returns 10). Reactions, which LinkedIn does not show at all. Many posts at once, use linkedin_search_posts, whose rows carry the same commenters in top_comments. Returns: List. rows[]: one comment each: author (the profile's slug, the part after /in/ or /company/), author_url (on www.linkedin.com), text (cut at 2000 characters). LinkedIn gives no time, likes or replies for a comment, so those are null. meta.cursor is always null: there is no next page. Cost: 1 credit. Cached 6 hours. Example: {"url": "https://www.linkedin.com/posts/aagupta_what-you-need-to-know-ai-agents-activity-7354600338621906944-RvXR"}
    ConnectorAPI key
  • Default tool for finding people on LinkedIn from criteria (company, role, department). With a ready search URL use search_linkedin_navigator; for one known profile URL use upsert_linkedin_contact. Search LinkedIn people. RECOMMENDED FOR PROSPECTING: set decisionMakers:true, provide company, departments and limit 20-30. Salesbot resolves the company, performs ONE company-scoped provider search (Sales Navigator also applies seniority), then ranks the returned senior employees locally by department. This is broader and safer than retrying exact titles. Use title/titles only when an exact role is required. EXISTING CONNECTIONS reads only the local cache and consumes zero search quota. The workspace setting selects Standard/Classic or Sales Navigator automatically. Respect retry_after; never immediately retry a protected or timed-out request. On LINKEDIN_PROVIDER_TIMEOUT use search_google_xray, then retry LinkedIn only after the stated delay.
    ConnectorAPI key
  • Use for general web research (company info, news, job portals). For LinkedIn profiles use search_linkedin_people; to read one company's own site use read_company_website. General-purpose Google search — returns organic results for any query. Unlike search_google_xray (LinkedIn-only), this searches the entire web. Useful for finding job postings on portals (jobs.cz, prace.cz, profesia.sk, indeed.com), company info, news, or any other web content. Results are NOT saved to contacts — use this for research and discovery. Capped at 4 calls per minute to protect the Serper/Google budget.
    ConnectorAPI key
  • Give noticed a LinkedIn or GitHub URL for a contact missing a profile (an email-only person from list_profile_gaps). Pass person_id + the url. If that profile is already in noticed it matches + merges them into one record (a contested match is held for an admin); if it's new, noticed queues it to fetch + enrich, then match. Use to ENRICH a thin contact — not to merge two existing records (that's accept_identity_match / suggest_identity_match).
    Connector
    Destructive
    No auth

Matching MCP Servers

Matching MCP Connectors

  • GitHub MCP — wraps the GitHub public REST API (no auth required for public endpoints)

  • Manage repositories, users, releases, and automate GitHub workflows

  • [Ids in: draftId: job id, from list_job_postings → jobPostings[].id. Ids out: jobId: job id.] Publish ONE job posting draft on LinkedIn. mode FREE publishes it without paying. mode PROMOTED or PROMOTED_PLUS SPENDS MONEY from the payment method on the LinkedIn account, up to the budget given (or LinkedIn's suggested budget when none is given) — state the amount to the user and get an explicit yes first. Once published the posting is public. If LinkedIn asks to verify your right to post for that company, the answer says so; send the code with solve_job_posting_checkpoint. Counts against a daily allowance (20 a day).
    Connector
    Destructive
    OAuth
  • Create a human drop page so ChatGPT or Claude users can upload laptop files (up to 20 per link) without dashboard login. Returns drop_url (https://www.poster.ly/drop/<token>). Send that URL to the user, wait, then call list_media. Accepts JPEG, PNG, GIF, WebP, MP4, MOV, WebM, and PDF up to 50MB (a PDF is for LinkedIn document posts); HEIC is not accepted. This is not the chat paperclip and not create_signed_upload.
    ConnectorAPI key
  • Search LinkedIn job postings, like the Jobs tab of LinkedIn: which companies are hiring for a role right now. Returns up to 25 postings per page with the title, the hiring company (name and numeric company_id), location, workplace type, salary when shown and listing date. Keywords take LinkedIn's syntax: "exact phrase", OR, AND, NOT. Filter by location, recency, workplace type, job type, experience level and company; paginate with start (0, 25, 50…). These are LinkedIn job offers, not Reach jobs (create_job / list_jobs). Use to find companies hiring for a role (a buying signal: a company hiring SDRs needs sales tooling, one hiring a Head of Data will buy data tools); then salesnav_build_search_url with current_company=[company_id] for the people who decide, or scrape_search on a classic people search filtered on that company. Not for Reach batch jobs (list_jobs). One LinkedIn call per page of up to 25 postings, each counted against the daily job_searches quota (default 50 pages); keep to a few pages. Read-only.
    ConnectorAPI key
  • Search LinkedIn job postings, like the Jobs tab of LinkedIn: which companies are hiring for a role right now. Returns up to 25 postings per page with the title, the hiring company (name and numeric company_id), location, workplace type, salary when shown and listing date. Keywords take LinkedIn's syntax: "exact phrase", OR, AND, NOT. Filter by location, recency, workplace type, job type, experience level and company; paginate with start (0, 25, 50…). These are LinkedIn job offers, not Reach jobs (create_job / list_jobs). Use to find companies hiring for a role (a buying signal: a company hiring SDRs needs sales tooling, one hiring a Head of Data will buy data tools); then salesnav_build_search_url with current_company=[company_id] for the people who decide, or scrape_search on a classic people search filtered on that company. Not for Reach batch jobs (list_jobs). One LinkedIn call per page of up to 25 postings, each counted against the daily job_searches quota (default 50 pages); keep to a few pages. Read-only.
    ConnectorOAuth
  • Suggest a GitHub repository (an AI agent, MCP server or AI developer tool) for listing on AgentIndex. No login or API key needed. The submission is queued for human review, usually within 1-3 days; it does not appear in search results immediately. Tools are listed only if the repository is public and has at least 100 stars. Check with search_tools first that the tool is not already listed. Returns {success, message, github_url}, or an isError result if the URL is not a GitHub repository URL or the submission service is unavailable.
    ConnectorNo auth
  • Records that an approved LinkedIn Article (channel linkedin_article) is live: pass its id and the https linkedin.com URL LinkedIn shows for it. The post becomes published with publishedAt now and externalUrl the URL, the same as a post Mark published, and Mark reads its LinkedIn metrics daily for 30 days, then weekly until 90 days, through the connected LinkedIn account. Mark never publishes an Article itself, since LinkedIn has no API for them; a person copies the approved Article into LinkedIn at its slot time (get_post handoff reads publish_by_hand, then publish_now), then this records it. Calling again with the same URL succeeds and changes nothing. Refused for a post that isn't approved, another channel, a URL that isn't on linkedin.com or has no urn:li:share: or urn:li:ugcPost: post URN (a /pulse/ address), or a published post with a different URL. To help the person copy it, get_post gives the headline (meta.title) and the Markdown body; the cover is the asset meta.cover.assetId names, whose URL get_asset returns. Only use it once the user says the Article is live. Related: get_post, get_asset, approve_posts, get_calendar.
    ConnectorOAuth
  • Link the GitHub repo a saved plan is being built in, and check it: detect_stack reads the repo and each planned service is marked found or not found yet (normal while building), services the repo uses that the plan doesn't are listed as drift, and when every planned service is found the plan is marked built. Pass id (a saved plan from list_saved_stacks) and repo the first time; after that, id alone checks the linked repo again. Private repos need the Kong Reviews GitHub App on that repo. How to present: say whether it is built; list what is not found yet as the next setup steps (from get_build_pack); for each drift service, ask the user whether to keep it (price it with diff_stack, or re-plan) or take it out of the code. Needs sign-in.
    ConnectorOAuth
  • Watch someone in your current workspace (or `workspace`), with or without a role. About once a day AyHire re-checks their public GitHub profile and activity, and each change you asked about shows on Home and in list_watches with the link where it was seen. `rules` (default: all): open_to_work (GitHub “available for hire” turns on, or bio/LinkedIn headline says #OpenToWork), job_change (the company on their GitHub profile changes; their LinkedIn employer when AyHire reads it), says_looking (bio/headline says looking for, seeking or available for new work), new_work (public activity after 30+ quiet days, a new public repo or a release). paid_checks=true also re-reads their LinkedIn every 14 days when AyHire already has it: a paid lookup, about $0.005 each, within AyHire's limits. Ask the user before turning it on. Watches are shared with the workspace's team. AyHire can't watch for posts (e.g. about leaving a job): it doesn't read them.
    ConnectorAPI key
  • Call this for network-wide numbers across all public Telegram groups tracked by Limzo (group count, messages, active users, replies, reactions, karma — 7-day and all-time) plus durable lifetime totals (messages analyzed, members tracked, spam messages removed) and the current top groups by Limzo Score. For finding a specific group, prefer list_groups.
    ConnectorNo auth
  • Call this for network-wide numbers across all public Telegram groups tracked by Limzo (group count, messages, active users, replies, reactions, karma — 7-day and all-time) plus durable lifetime totals (messages analyzed, members tracked, spam messages removed) and the current top groups by Limzo Score. For finding a specific group, prefer list_groups.
    ConnectorNo auth
  • Read-only public health probe for the IntoDNS.ai backend itself, not a target domain. Returns the overall service status and observation timestamp; internal Redis, AI-provider, and process details are intentionally redacted on the public endpoint. Use as a pre-flight check before batch jobs or to distinguish a service incident from a real DNS finding; use get_stats for public usage counters instead. Single unauthenticated GET with no destructive actions.
    ConnectorNo auth
  • Is anything I depend on broken right now? Checks every supported provider in parallel and returns a one-sentence summary plus per-service detail. Use this first: it answers the whole question in one call. Optionally narrow with ?services=github,npm. A provider whose status page cannot be read is reported as "unknown", never as healthy.
    ConnectorNo auth
  • Get remediation advice for a single finding as GitHub-flavored markdown. When AI Assist is enabled and within budget this is a suggestion written for this exact finding; otherwise it falls back to the static guidance-library text and says so in 'source'. Unlike the other reads this one can spend AI budget, which is why it is a separate tool. Use this for advice on one finding; for the whole library use list_security_guidance. Requires project context.
    ConnectorAPI key
  • Creates a DRAFT campaign from a sequence. With a LinkedIn Sales Navigator search it also starts finding + verifying leads for it; without one the draft holds the emails and leads can be added from Lead Finder or a CSV upload. Nothing sends — the campaign stays a draft until you review and launch it. Returns the new campaign id, plus a lead-finding job id when lead finding started.
    ConnectorNo auth
  • Returns who The Automators are: name, description, founding year, headquarters, service area, the public team (name, role, LinkedIn, bio), verified public profiles, the content licence (RSL 1.0) and headline track record. Use it to introduce the company or check a fact about it. It is not the place for pricing (get_pricing) or contact details (get_contact_options).
    ConnectorNo auth