Skip to main content
Glama
741,519 tools. Updated 2026-11-04 05:16

"A platform for collaboration and communication - Feishu" matching MCP tools:

  • Connect a custom domain to a site. IMPORTANT: between this call and a working domain stands A PERSON. You get DNS records — show them to the user and explain they go in at their domain registrar. Do not wait for readiness: DNS propagates in minutes to an hour, the platform re-checks on its own, and you check later via `check_domain`. Spinning here burns time and context for nothing. The address can be passed as-is: the platform reduces `https://shop.example.com/page` to `shop.example.com` itself.
    ConnectorOAuth
  • Connect a custom domain to a site. IMPORTANT: between this call and a working domain stands A PERSON. You get DNS records — show them to the user and explain they go in at their domain registrar. Do not wait for readiness: DNS propagates in minutes to an hour, the platform re-checks on its own, and you check later via `check_domain`. Spinning here burns time and context for nothing. The address can be passed as-is: the platform reduces `https://shop.example.com/page` to `shop.example.com` itself.
    ConnectorAPI key
  • List Fonteum’s public-record source catalog with available authority, vertical, cadence, official URL, and separately dated platform coverage. Catalog presence does not prove loaded, fresh, or complete coverage. Use for source discovery, coverage questions, or choosing a dataset before a lookup.
    ConnectorNo auth
  • Preview deletion by default. Only the owner can permanently delete the project and its story/collaboration records. Keep dry_run=true until the user approves the stated impact; then set dry_run=false, confirmed=true, and expected_title from the preview. Preserves world/library assets.
    Connector
    Destructive
    No auth
  • List and filter the CRM contacts (people who have written to or interacted with the connected accounts), each with `id`, `name`, `email`, `tags`, `subscribed` and `platform`, plus `count` with the total that matched before the limit. Use it to find a person or a segment; for one person's channels, custom fields and notes use get_contact, and for their messages list_conversations. Returns 40 by default and at most 200: if `count` is higher, narrow with tag, search, platform or accountId. The `id` is what get_contact, update_contact, set_contact_field and enroll_in_sequence take.
    ConnectorOAuth
  • Retrieve active subscriber device records, assigned segment tags, platform breakdown counts (Web VAPID, Android FCM, iOS APNs), or full CSV/JSON backup export for zero-downtime migration. Use this tool to inspect audience size, platform distribution, export subscriber tokens (export_format="csv" or "json"), or obtain a subscriber_id before calling update_subscriber_tags; do not use it to view campaign click metrics (use get_campaign_analytics instead) or modify/import subscribers (use update_subscriber_tags instead). Read-only operation requiring PUSHNOTIF_API_KEY with 0 credit cost; filter by app_id and optional tag to narrow results. Returns JSON { total_active, platform_breakdown: { web, android_fcm, ios_apns }, subscribers: [{ id, app_id, platform, tags, created_at }], export_data }.
    ConnectorNo auth

Matching MCP Servers

  • F
    license
    A
    quality
    D
    maintenance
    In-memory MCP server for cooperative collaboration between separate agents, enabling topic-based messaging and coordination via tools like create_topic, join_topic, send_message, read_messages, and check_in.
    8
    -
  • A
    license
    Not graded
    quality
    D
    maintenance
    MCP server that provides email communication tools (send email, health check, list providers) via SMTP, accessible over HTTP/SSE for remote AI clients like Claude Desktop.
    6 npm
    MIT

Matching MCP Connectors

  • List incoming Instagram collaboration invites: posts from other accounts that invited this profile as a collaborator. Each invite has media_id, media_owner_username, caption and media_url (omitted for videos with copyrighted or licensed audio). Paginate with after = next_cursor (null on the last page). Accept or decline with instagram_collaboration_invite_accept / _decline. To send invites, pass collaborators to post_publish. Only works for Instagram profiles connected through Facebook Login — Instagram Login profiles get 422.
    ConnectorOAuth
  • Get per-platform engagement (views / likes / comments / shares) as a time series over the trailing window_days (default 28, up to 365). Omit account_id to aggregate across all connected accounts, or pass one from list_accounts; optionally filter to a single platform. post_limit (≤100) fixes how many recent posts form the baseline. granularity buckets the series server-side ('daily' default, 'weekly', or 'raw' for every scrape). Read `series` (a clean per-platform list of typed points) — `metrics` is the legacy column/data matrix kept for back-compat. NB: follower counts here are latest-only; for audience growth over time use get_follower_history.
    ConnectorOAuth
  • Re-queue publishing for a post's FAILED platforms. platformIds takes platformId values from list_post_results, platform names such as "BLUESKY" (every failed row of that platform), or can be omitted to retry every failed row. Only rows with status FAILED are reset to PENDING and retried with the same content. A value matching neither a row id nor a platform of the post fails with "Unknown retry target"; with nothing failed among the matches the call fails with "No failed platforms to retry". The post moves to PUBLISHING and the retry is asynchronous, so check list_post_results for the outcome. Read each errorMessage first and retry once the cause is fixed (reconnected account, replaced media), not for a platform-side restriction, which will just fail again. Content cannot change on retry.
    Connector
    Destructive
    OAuth
  • List EveryInfra's data platforms and capabilities (106 platforms / 573 capabilities: search, detail, comments, profiles and more). Use it before everyinfra_call_api to get the platform/action, required and optional params, the per-call row limit (max_limit, or page_size for page-based actions) and the price. Pass a platform to also get allowed values, returned fields and what they mean. Free. Data collection only — for AI chat use everyinfra_chat.
    ConnectorNo auth
  • Delete a post from iHatePosting. ONE SEND AT A TIME: a SCHEDULED post going to several accounts is stored as one post PER SEND, so deleting one cancels only that platform and leaves the rest scheduled — pass the `postId` that create_post returned on that particular send, or the id of the row list_posts shows for it. There is no need to cancel a whole multi-platform post to drop one platform from it. A DRAFT IS DIFFERENT: until it is scheduled, a draft is ONE post holding every platform it is aimed at (all its sends share one postId), so deleting it removes every platform — to drop one platform from a draft, use update_post with the remaining accountIds instead. The reply's `platformsRemoved` names every platform the delete took; for one send of a group, `stillScheduled` lists the sends still going out and `otherSends` the rest of the group (already published or failed), each with its status; their `scheduledAt` is UTC (it ends in Z) and `scheduledLocal` is the same moment in the account owner's timezone — report that one. THIS DOES NOT UNPUBLISH ANYTHING: a post that has already gone out stays live on the network, and deleting it here only removes iHatePosting's record of it. For that reason a published post is refused unless you pass force: true, and you should only do that after telling the user in words that the platform post will remain. A post that is publishing at this moment is never deletable, forced or not — the worker is mid-flight on it. Deleting a scheduled post stops it going out.
    Connector
    Destructive
    No auth
  • Aggregate performance for one connected channel, or for every channel at once. Returns impressions, reach, likes, comments and engagement rate for the period, the change against the preceding period of the same length, and the follower series. Omit `platform` for a team-wide total; pass `platform` (plus `channelName` or `providerId` from list_connected_accounts when that platform has more than one account connected) to scope it. `providerId` still identifies the account after its handle changes. `period` is 7d, 30d, 90d or all, defaulting to 30d. Use this for "how did LinkedIn do this month?"; use get_post_metrics for a single post and get_best_time_to_post for scheduling.
    ConnectorAPI key
  • Metrics for this workspace's published posts. Returns a summary totalled across every published post (post count, overall totals, totals per platform), plus the newest posts in detail, each with one entry per platform it went to: impressions, reach, views, likes, comments, shares and saves. A metric is null when that platform does not report it; supported=false means nothing can be read for that target (no analytics for the platform, or no post id yet). Values are the last stored reading, not a live fetch, and fetchedAt says when it was taken. Use this to answer whether posts worked. It covers published posts only: use list_posts for drafts and scheduled posts, get_post for one post's details, and get_link_in_bio for visits to the link-in-bio page.
    ConnectorAPI key
  • Compute INSPIRE-HEP's citation summary for one author or for any literature query: h-index, citation totals, average citations per paper, and paper counts per citation bucket (0, 1–9, 10–49, 50–99, 100–249, 250–499, 500+), each for all citeable papers and for published papers, plus citations received per year. Pass exactly one of author (a BAI, ORCID, INSPIRE ID, or author recid — resolve a name with cern_inspire_search_authors first) or query (any INSPIRE literature query: a topic, collaboration, institution, or "a <BAI>"). Document type and subject filters narrow every figure. year_from and year_to narrow the summary to papers from those years, and exclude_self_citations recounts it without self-citations; any of them leaves out citations per year, which INSPIRE cannot narrow that way.
    ConnectorNo auth
  • Identify a game from a description of what the user remembers (plot, look, platform, era). Returns ranked candidates with a reason each, a `confidence`, and `find_game_url`: imho.run's /find-game page with the description filled in (the user presses the button; nothing runs by itself). Pass what the user said about the platform, the release years and the camera as `platform`, `year_min` / `year_max` and `perspective` instead of leaving them only in the text. When `confidence` is not high or no result fits, give the user `find_game_url` so they can add details there. Slow (LLM) and rate-limited: use it only when the user does not know the title; for games similar to a known game use games_like or recommend. Games rated for adults only (explicit sexual content) are not covered; filtering is best effort.
    ConnectorNo auth
  • List Agentropolis platform features with status (live, partial, stub, planned), endpoint and guardrails: badges, the x402 relay, seller claims and analytics, sponsored placement, market data, billing. Use it to check whether a platform capability exists before relying on it; it describes Agentropolis itself, not listings. Read-only, no parameters. Stub endpoints answer HTTP 501; payments_enabled shows whether Agentropolis charges for anything (currently false).
    ConnectorNo auth
  • Changes an existing Audience in place: it keeps its id, its Minds keep theirs (except copies below), and no Mind is deleted. Covers composition and trait edits, a population pivot, adding members, an exact chart selection (`distributions`), new sources and going deeper (`deepen`), and re-runs its research grounding. Owner, or verified Minds staff with existing direct Audience admin collaboration or an active owner-issued support grant. Staff support is limited to composition amendments: no growth, new sources, Go deeper or shared-Mind waiver. Asynchronous: the result is an accepted operation with its id, not a completed change. Queues behind another edit of the Audience and waits for a Study run on its members. Members shared with other Audiences are replaced here by copies with new ids. Reusing requestKey with identical input retries safely.
    Connector
    Destructive
    API key
  • Find the data sources an account can put on a dashboard, across every platform it has connected. Use when: the user wants a source on a dashboard and you have no sourceId for it — search first, then pass what comes back to add_data_source_to_dashboard. Searches two things. Sources DashThis already holds are found straight away, whatever the platform. Sources that exist on the platform but nobody has picked yet are found only once the search names ONE connection — asking every connection would mean calling every platform — so pass 'connection' (or an 'integration' the account has only one connection to) when the first search comes up short. Returns: each source with its connectionId and providerKey, plus a sourceId when it is already set up; and the connections searched, so you can narrow to one. Rules: this creates nothing and changes nothing. If several sources could be meant, put them to the user and let them choose — never guess, because the wrong one puts another client's numbers on a report. Then: name the source, its platform and its connection when you report back — one client often has several accounts on the same platform — and its status when it is in error.
    ConnectorOAuth
  • List the SYSTEMIC PATTERNS the platform tracks: issues that have recurred AND been remediated repeatedly, grouped by whoever can fix them at source. ALWAYS call this before diagnosing a recurring problem, and whenever the user asks why something keeps happening, keeps coming back, or has happened before. Each entry carries occurrence / distinct-cluster / distinct-day counts, how many times an agent remediated it, and an interpretation field stating what the row means for your answer - read that field before replying. A pattern with status 'escalated' has ALREADY been reported for a permanent fix (to the Ankra platform team as a support ticket, or to a stack profile's owner as a change request): say so and cite escalation_reference instead of re-diagnosing, and never report it again. Scope 'platform' means the defect arrives with every cluster Ankra provisions; 'stack_profile' means one profile version ships it to every deployment of that profile; 'local' is confined to one cluster and is never reported upstream. Read-only.
    ConnectorOAuth
  • Prepare ONE private message to an event host or a community, not an event RSVP. Supply eventId or collectiveId (exactly one; a community-owned event routes to its community either way), stable requestId, explicit replyEmail, message and topic question/tickets/refund/volunteering/accessibility/collaboration, or topic community for a community page. Use only facts the person wants included, never private memories/transcripts by default. Returns the exact message, recipient label, email-sharing disclosure, requestId and reviewHash. Sends nothing. In SocialLoop chat, immediately stage send_host_contact alone with these returned values; the system shows the exact review and collects one approval. Do not ask a separate informal confirmation first. Draft expires in 30 minutes; changed content or a confirmed expired draft needs a new requestId.
    ConnectorNo auth
  • Add a platform (or another account on a platform) to a Note that is already scheduled, so it posts there at the same time as the Note's other versions. Use this, not schedule_note, whenever the writer wants an already scheduled Note to also go to X, LinkedIn, Bluesky, Threads, Instagram, Facebook, TikTok or Pinterest: schedule_note would create a separate Note. Pass the id of any scheduled version of the Note (from list_scheduled_items, list_notes or schedule_note) and the platform. Without content the text is taken from the Note's versions (the same platform's version, else the longest that fits) and, if every version is too long, shortened to fit with adjustedPlatforms and warnings returned; content you pass is sent as written and must fit the platform's limit. When the writer has several accounts on the platform, name one with accountId (list_social_accounts; list_instagram_destinations for Instagram; list_linkedin_destinations for LinkedIn, with linkedInOrganizationUrn for a Company Page); without one the call is refused with the accounts to choose from. Ask the writer, never pick. Refused when the Note already goes to that platform or account (or posted there in the last day), when its time has passed or changed, or for Substack. Returns the new version(s) and their scheduled time. Safe to retry: pass a clientRequestId and reuse it only when retrying the same add (same Note and time, platform, account and content); a repeat returns the version already added (replayed: true), and the id reused for any other add is refused. Personal account only.
    ConnectorOAuth