Skip to main content
Glama
792,863 tools. Updated 2026-11-17 03:29

"DeskCrew - Workspace or Office Crew Management Platform" matching MCP tools:

  • Search Flevy's marketplace of consulting frameworks, PowerPoint templates, Excel financial models, business toolkits, and management case studies. Use this whenever a user needs a best-practice framework, methodology, template, financial model, or real-world case example on any business or management topic (strategy, digital transformation, supply chain, pricing, operational excellence, M&A, etc.). Returns up to 10 relevance-ranked recommendations across two content types: "document" (premium documents authored by management consultants) and "case_study" (management case studies). ALWAYS include each recommended item's url as a clickable link when you mention it in your reply — never reference a document without its link, because the link is the only way the user can open it. Each result carries a content_id for get_content_details. Filters: topic (single, or "topics" for documents covering ALL of several topics), author (list more documents from an author seen in results), filetype (including tier1_consulting_deck for McKinsey-style strategy decks), content_type. Topic-filtered responses also list related_topics to pivot to. Provide at least one of query, topic(s), or author; use list_topics to map user phrasing to a canonical topic.
    ConnectorNo auth
  • Replaces the video or image behind a not-yet-published post (draft, ready, scheduled or failed) with another upload from the same workspace, like the dashboard's "Replace media". The post keeps its schedule, captions, first comments and platform settings; only the media file changes. Set `apply_to_batch: true` to also swap every other post in the same batch (same media, same status and, for scheduled posts, the same scheduled time), which is what you want when one upload was scheduled to several platforms at once. Upload the new file first with create_video_upload_from_url or create_video_upload + finalize_video_upload, then pass its id here. Refuses text posts, carousels, and posts that are queued, processing or published. Platform compatibility of the new file is not re-checked, so pick media that suits every platform in the batch.
    Connector
    Destructive
    OAuth
  • Returns the user's default workspace (id, uniqueName, name, description) so you can use it as the `workspace_id` argument for other tools without prompting. Behavior: - Read-only. Takes no parameters. - Picks the default by priority: explicit user default > first owned workspace with activity > invited workspace. Same logic the web app uses to auto-select. - When no workspace is reachable, returns an object with null fields (does NOT error). This happens when the user has no accessible workspaces (owned or invited), or when a workspace-scoped session reaches none of the user's workspaces. - An account that has not finished setting up gets null fields and an `onboarding_url`, even if it already belongs to a workspace. Prefer onboarding_start, which sets the account up from inside the agent; otherwise relay that link and wait for the user to confirm they finished before retrying. When to use this tool: - Start of a conversation when the user hasn't named a workspace — avoids asking which one to use. - Whenever you need a `workspace_id` and the user implied "my workspace" or didn't specify. When NOT to use this tool: - The user names a specific workspace — use workspace_list to find it by name. - You already have a `workspace_id` and just want its details — use workspace_get. - Enumerating every accessible workspace — use workspace_list.
    ConnectorOAuth
  • Copy one or more of your personal knowledge items into an organisation workspace. The originals stay in your personal twin unchanged — this creates copies in the workspace so all members can retrieve them. IMPORTANT: This is a sharing action. Always confirm the items and target workspace with the user before calling this with multiple items. Items you do not own, or that are already in the workspace, are reported as failed per-item rather than aborting the whole batch. If you belong to exactly one workspace you can omit workspace_id; otherwise call list_workspaces first to get the ID.
    ConnectorOAuth
  • Mint a PROJECT-scoped management token (`er_mcp_`) for MCP and REST; it cannot authenticate relay traffic. Use it after create_project to configure a fresh project, or for any project you already own. Attenuated by design: the scopes must be a subset of THIS management token's own grant (`read` is always included), expiry is mandatory (1–90 days, default 30, never "never"), and the minted management token (being project-scoped) can never mint management tokens itself. `spend` is human-granted only: no management token, of any scope, can mint one carrying it. Mint a spend-scoped token from the project's panel instead. Requires an ACCOUNT-scoped management token and the `config` scope. Returns the plaintext exactly once; only its hash is stored.
    ConnectorNo auth
  • Update an existing memory by ID. Use mode replace (default) to patch fields, or append to extend content. Re-embeds only when content changes. The target workspace is always the one the memory itself belongs to (echoed in resolved_workspace); optionally pass workspace: <name> as a safety confirmation — the call fails if the memory is not actually in that workspace.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    A
    quality
    B
    maintenance
    Enables AI agents to perform helpdesk tasks over MCP, including ticket management, knowledge base search, and reply drafting, with optional pay-per-action USDC settlement and human approval workflows.
    23
    2
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Provides live wait times and office details for all 60 Oregon DMV field offices by scraping the ODOT website, with no authentication required.
    294 npm
    MIT

Matching MCP Connectors

  • Agent personas for Claude. 16 tools, 13 personas, 3 workflows. Zero extra API cost. Free.

  • Send real paper letters through Deutsche Post to Germany and 217 other countries.

  • Create a new ad group under a campaign. Every ad group belongs to one platform (body.platform, a platform id such as google-ads): only that platform receives it, its ads and its keywords. Leave it out on a campaign that runs on one platform; name it on a campaign that runs on several (400 AD_GROUP_PLATFORM_REQUIRED lists them). It is fixed once created — use copy_ad_group to run the same ads elsewhere. Returns the full updated/created object. Scoped to the active Space — see set_active_space to switch, or pass space_id to override for this one call.
    ConnectorAPI key
  • Return the connected organization, the credential in use, and the granted workspace + environment ("TEST" or "PRODUCTION") targets — exactly the values the required workspaceId/environment arguments on targeted tools accept. Always available; call this first, and again whenever a tool returns UNAUTHORIZED or NOT_FOUND unexpectedly, or after this connection's access changes — resources live per-workspace.
    ConnectorOAuth
  • Report which Zentrik workspace this connection is bound to, and the connecting user's role in it. Call this whenever the user asks which workspace, account, or environment this connection uses, or before concluding a workspace is empty or the connector is broken — confirm the binding first. Takes no arguments. One Zentrik connection is bound to exactly one workspace for its lifetime, so there is nothing to select or filter. Returns workspace.id and workspace.name, the workspace every tool call in this session reads from and writes to, and role, this connection's Zentrik workspace role. Role gates tool availability: Viewer is read-only; Editor, Admin, and Owner can also use write-capable tools.
    ConnectorOAuth
  • Select one workspace for free Seller access. Ask the seller to name the workspace from spellbook_workspaces_list and confirm that choice before this call. Never pick a workspace from list order or an active-workspace default. The signed-in person must own it. Re-read spellbook_workspace_plan_status after this call for the access state and observed usage.
    Connector
    Destructive
    No auth
  • Rename the organization and/or workspace after Roost or Roost Audit has been paid. Pass `orgName`, `workspaceName`, or both. Requires a workspace-paired session. Fails on free Hatch workspaces — call `checkout` with grant `workspace_subscription` (Roost) or `agentic_pro` (Roost Audit) first, then `poll_checkout`. Does not rename a hatch URL; use `convert` for that. Returns `{ workspaceId, workspaceName, orgId, orgName, plan }`.
    ConnectorNo auth
  • Suggest a grade look for a project — read-only, no cost. With image_id, includes the image prompt; without it, uses only the colorist crew brief. Returns a recommended look name with a reason and alternatives; apply it with lab_grade(look: …) once the user agrees.
    ConnectorOAuth
  • Change the caller's own voyages: create, update, delete, replace the full crew set (set_crew, PUT semantics), set or clear the charter (set_charter — a null charter clears it), announce the trip to its crew by email (announce), and turn its public link on or off (create_share, revoke_share). A trip spans at most 365 calendar days, first and last included; longer is trip_too_long (422). An update that moves the trip's dates so that a diary entry would fall outside them is refused with diary_outside_trip (409), whose details list those dates; first rewrite those entries on days inside the new dates and delete them (diary_write), or pick dates that keep them. Charter price/deposit are integer minor units plus an ISO 4217 currency code — never a float. Inviting a crew member to the app is person_write's `invite`/`accept_invitation`: an invitation is person-scoped, and accepting one shares every trip of that owner whose crew that person is on, past and future. `announce` mails the trip's particulars to crew who have a linked account and have not switched that category off in Settings; it reports how many actually went out, and is rate-limited per trip and per recipient address. `create_share` turns on a public, read-only, no-login link to one of the caller's OWN trips and returns its URL (idempotent — one link per trip, calling it again returns the same URL); `revoke_share` turns it off. The public view is redacted — no charter, crew shown as initials only, no owner details — but anyone with the link can open it, so the URL is semi-public. IDs are 6-character case-sensitive alphanumeric strings. Timestamps are UTC ISO 8601. Distances are integer meters. Durations are integer seconds.
    Connector
    Destructive
    OAuth
  • Create a new API key in one of your workspaces. Requires admin access in that workspace. The plaintext key is shown exactly once in the response. It is never retrievable again after this call, so save it immediately. Not available when this MCP connection is itself authenticated with an API key (headless mode): a leaked agent key must not be able to mint more keys. Mint keys from an interactive (OAuth) session or the console instead. workspace: optional workspace id, workspace name, or `org-name/workspace-name` when the same name occurs in two of your orgs (defaults to your default; use list_workspaces to discover them). name: a label for the key, shown in the workspace's key list later. scopes: key capabilities: ["ingest"] (default) to send telemetry, add "read" (["ingest", "read"] or ["read"]) for a key that can also be used as the Authorization bearer for headless MCP connections. The alert-management capabilities (alerts:manage, channels:manage) are deliberately NOT mintable here — an admin issues those in the console, because a key minted by an agent never expires by default and would be an unbounded credential to leak. Example: > Create an API key so this agent can send traces. ```json { "name": "create_api_key", "arguments": { "name": "my-agent" } } ``` > Give it a key that can also read traces over MCP. ```json { "name": "create_api_key", "arguments": { "scopes": ["ingest", "read"] } } ```
    ConnectorAPI key
  • 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
  • List the Kooga workspaces this connection reaches, with the id to pass as workspaceId. Use it when the person names a shop or a site, or when a tool says a workspace is needed; a connection that reaches one workspace never needs it. Each workspace comes with its id, slug and name, the person's role, whether it is a store (a shop is connected) or a site, its plan, and a link to it in Kooga. These are the workspaces the person ticked when connecting this app and still owns or administers.
    ConnectorAPI key
  • Move a draft to another workspace (client) on this account, for a post saved in the wrong one. Finds the post by id in any workspace, not just the active one. Its tags are matched by name in the new workspace (or created there), its lane is cleared, and its author and reviewers are given access to the new workspace if they had none. Only drafts move: cancel a scheduled post first. A post set to go out on a channel that isn't in the new workspace is refused. Account admins only. Moving it back undoes it.
    ConnectorOAuth
  • List the Postemi workspaces this connection can act on, and which one it acts on now. Call this when the user asks what workspaces they have, mentions a brand or client that does not match the current workspace, or when a channel they name is missing from list_integrations. Every other tool works on the CURRENT workspace only; switch_workspace changes it for connections made by signing in (a connection made with an MCP key stays in its own workspace).
    ConnectorOAuth
  • Leads eines Instant Forms der letzten N Tage: je Lead id, created_time, campaign_id, adset_id, ad_id, is_organic, platform und answers ({Feldname: Antwort}). Personenbezogene Daten — nur, wenn der Workspace Meta-Lead-Daten im Portal freigegeben hat; sonst error=lead_data_disabled (Anzahl je Formular liefert meta_list_lead_forms auch ohne Freigabe). Setzt die Meta-Berechtigung leads_retrieval voraus. Das Formular muss zur gewählten Page des Werbekontos dieses Workspace gehören, sonst error=foreign_object (keine Leads). form_id: aus meta_list_lead_forms. page_id: wie bei meta_list_lead_forms. days: Zeitraum 1–90 (Default 30). limit: max. Leads (Default 100, max. 500); mehr vorhanden → {result, warning}. workspace: Slug des Kunden-Workspace (optional bei nur einem Workspace).
    ConnectorOAuth
  • Change this workspace’s display name (for example, replace the generated “xxx’s workspace” with a company or brand name). It appears in the web console, on invitation pages, on the workspace home page and on folder pages; up to 40 characters. ★ Display name only: the <workspace> part of https://<workspace>.24hw.cn stays the same (change that with set_workspace_slug), and links, pages and members are unchanged. ★ The company name on WeChat share cards comes from set_workspace_profile’s company_name, not from this name. ⚠️ Workspace owner only.
    ConnectorAPI key
  • Choose or clear this space's welcome page (space managers only) PUT /api/v1/space-welcome For multi-space accounts, call auth_verify, ask the user which space to use, and pass targetSpaceId. The welcome page is an ordinary Doc or HTML node that Home shows at the top for every member who can read it. To set one up, write the guide as a Doc or HTML node first (node_create), read it back, then pass its node id here. Choosing it requires workspace management access and the current expectedVersion; nodeId null clears it. Change it only when the user asks; a conflict means reload rather than overwrite.
    ConnectorAPI key