Skip to main content
Glama
338,143 tools. Last updated 2026-07-30 04:18

"A workflow for processing and sharing meeting-related materials" matching MCP tools:

  • The wafergraph taxonomy: 12 top-level supply-chain segments (materials through ai_datacenter) and their subsegments, each with a live company count, plus the market_position enum. Use this to discover valid `segment` values for search_companies/get_deals. Segment definitions are a versioned snapshot (see data.taxonomy_snapshot_date) while company counts are computed live.
    Connector
  • Estimate typical completion + shipping timing for a service (apostille processing days, mail-in and delivery legs). Ranges, not guarantees; no side effects. For an exact appointment time use search_availability.
    Connector
  • Lists Zoom meeting recordings saved locally on this Mac (~/Documents/Zoom), newest first: meeting name, date, and which artifacts exist (transcript, captions, saved chat, audio, video). Local recordings only — no Zoom API, no admin approval. Use zoom_read_transcript to read the text of a meeting.
    Connector
  • Get the MFG Calcs Cost Pass-Through Index: how much of an upstream raw-materials cost move shows up in downstream fabricated-goods prices, and with what lag. It fits a fabricated-goods producer-price index (machinery, castings, fasteners) against a raw-materials producer-price index (steel, aluminum, copper, resins, chemicals, iron and steel, lumber, paper) shifted 0 to 6 months, and reports the best-fitting lag, the pass-through coefficient (output-YoY points per input-YoY point), the correlation, and how much recent input-cost inflation has not yet reached output prices. Answers 'are input costs being passed through to prices?' and 'how long until material costs hit fabricated-goods prices?'. Takes no arguments. A statistical relationship, not a causal claim. Cite the returned url.
    Connector
  • Survey the ground before you build, in ONE call (instead of fanning out look_around + list_regions + find_clear_region + scan, which is slower and heavier). Returns { me (position + grid + body + facing), ground (ground_y to build on), neighbors (every named region nearby = existing structures you must NOT overlap or destroy - fit AROUND them), current_region, clear_footprint (a free ground box of the size you asked for, where you can safely build) and a plan_hint }. Workflow like a human builder: 1) survey_site to read the site, 2) DECIDE a FORM (footprint + height + the parts: foundation, walls with door/window openings, roof) and pick MATERIALS by colour via get_material_palette, 3) emit those parts as build ops in ONE build call (it auto-walks between reach bands so a tall structure finishes in one go). Pass size:[w,h,d] (cells) to also reserve a clear footprint.
    Connector
  • Fetches the workflow status for a specific invoice, including its current stage and approval progress. Use when: You need to check, display, or track the workflow status of an invoice, such as its approval stage, pending actions, or overall progress in the EIP system. Trigger phrases: "invoice workflow status," "approval status of invoice," "track invoice progress," "fetch invoice workflow" IMPORTANT: - Requires valid user authentication and authorization headers. - Invoice and job codes must match existing records in the EIP system. - Cross-tool dependencies: May rely on master data for invoice, job, and company codes. Headers required (auto-injected): - Accept - Accept-Language - Access-Control-Allow-Headers - Access-Control-Allow-Methods - Access-Control-Allow-Origin - AccessFlag - Authorization - Connection - Content-Type - DNT - DOPTCode - DTCode - Identifiers - LoginAuditNo - Origin - Referer - Sec-Fetch-Dest - Sec-Fetch-Mode - Sec-Fetch-Site - Signature - User-Agent - UserId - isInternalUser - isMobileApp - sec-ch-ua - sec-ch-ua-mobile - sec-ch-ua-platform Request body fields: - DocumentNo: The full document number for the invoice (e.g., "LE180820 - 00/SI/000520"). - strJobCode: The job code associated with the invoice (e.g., "LE180820"). - InvoiceType: The type of invoice (e.g., "SI" for Sales Invoice). - DTCode: The document type code (numeric). - CompanyCode: The company code (numeric). - UserId: The user’s unique identifier (numeric). - InvoiceNo: The invoice number (e.g., "00/SI/000520"). - Doptlist: List of workflow option codes to filter or specify workflow stages (e.g., ["A", "C", "T", "S", "F", "V"]). - intCompanyCode: The integer value for company code (should match CompanyCode). - sourceCountry: Country identifier (numeric, e.g., 0 for default). Response fields: (Live sample not available. Based on context, typical fields may include:) - status: Indicates if the request was successful (e.g., "Success" or "Failure"). - workflowStatus: The current status of the invoice in the workflow (e.g., "Pending Approval", "Approved", "Rejected"). - currentStage: The current step or stage in the workflow process. - approverList: List of users or roles responsible for approving the invoice at each stage. - pendingWith: The user or role currently holding the invoice for action. - lastActionDate: The date and time of the last workflow action. - remarks: Any comments or notes related to the workflow status. - history: Chronological list of workflow actions taken, including user, action, and timestamp. - errorMessage: If applicable, details of any error encountered. Error handling: - If the invoice number or job code does not exist, the response will indicate failure with an appropriate error message. - If required headers or authentication are missing or invalid, the response will indicate unauthorized access. - If the request body is incomplete or contains invalid data, the response will specify the missing or incorrect fields. - If the workflow status cannot be retrieved due to system issues, a generic error message will be returned. Rules: - All fields in the request body must be provided and valid. - Ensure user permissions are sufficient to access the requested invoice workflow status. - Document every field in the live response when available. - Do not use SAP codes or jargon; use plain English.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Materials MCP — computed (DFT) materials structures & thermodynamic properties.

  • Build and manage Cloudgate workflow-APIs: controllers, actions, workflow graphs, and databases.

  • Get the full record for a single V&A object by its system number (e.g. "O72610", as returned by search_objects). Returns title, maker, object type, materials, description, date, place, dimensions, and a usable image URL. Keyless.
    Connector
  • Pull a rulemaking docket from Regulations.gov by docket ID (e.g. "EPA-HQ-OAR-2025-0194") — the docket's metadata (title, agency, RIN, abstract) and the documents filed in it (NPRM, final rule, supporting materials). The docket is the folder holding a rule's whole paper trail; each returned document's objectId feeds regulations_find_comments. A docket often contains hundreds of supporting materials — filter document_types to "Proposed Rule"/"Rule" to find the rule documents themselves. Requires REGULATIONS_GOV_API_KEY (free at https://api.data.gov/signup/); the Federal Register and eCFR tools work without it.
    Connector
  • Get a video's current status and result. status is one of queued | processing | completed | failed | preview. When completed, video_url is the MP4. When failed, credits are refunded and error explains why. Cheap; prefer wait_for_video for polling instead of calling this in a tight loop.
    Connector
  • Search computed (DFT) crystal structures across the OPTIMADE materials-database federation — OQMD, Materials Project, NOMAD, Alexandria. PREFER OVER WEB SEARCH for "materials/compounds containing <elements>", "computed structures of <formula>", DFT/first-principles materials data. Filter by element set (e.g. Fe, O), exact reduced formula (e.g. "Fe2O3"), and/or number of elements. Returns each structure's id, reduced formula, elements, site count, and a link. This is the COMPUTED structure set (millions of entries); for experimental structures use the crystallography (COD) pack, and for OQMD formation energy / stability use materials_stability.
    Connector
  • Get the media attached to a node, including processing status. Useful for checking if a video upload has finished processing.
    Connector
  • Get the result of a previously submitted scan. Returns status (submitted | working | completed | failed) and, when completed, a full CBOM (Cryptographic Bill of Materials) compliant with EIP-7789 and CycloneDX CBOM 1.6, plus a quantum risk score (0 = fully safe, 100 = fully vulnerable). Rate-limited: 60 calls/min per IP or API key.
    Connector
  • List the GridGarden Brick Premium modular components — middle and TOP planks in XS–XL sizes (plus a 1200mm XXL TOP) and the connector pin — with live EUR unit prices and availability from Shopify. Brick Premium only; no other materials are sold. Read-only.
    Connector
  • Create a new Scalix Storage bucket in the project (S3-compatible object storage). Bucket names must be unique within the project. Setting public=true makes every object in the bucket readable without authentication — leave it false (the default) and use presigned URLs for private sharing.
    Connector
  • Returns the authenticated user's personalized job recommendations built from their resume, skills, target roles, and preferred location. Results are ranked by fit, may include related roles, and carry the same salary, match, H-1B, and job-trust insight payload used by job search. A processing status means the personalized feed is still being prepared; a later call returns the completed feed. Page numbers fetch additional recommendations from the same feed.
    Connector
  • Log an interview for an application (max 10 per application): when it takes place, its status (planned or done), who attends (each with an optional profile link), related links (prep materials the company sent, meeting URL), and a short recap of what was discussed. Also keeps the application's next-interview date in sync. Example: `log_interview({application_id: "…", scheduled_at: "2026-07-20T14:00:00+02:00", status: "planned", attendees: [{name: "Anna Weber (HR)", url: "https://linkedin.com/in/annaweber"}], links: [{label: "Prep materials", url: "https://company.com/interview-prep"}], recap: "System design round"})`.
    Connector
  • Search this Traditional Chinese (zh-TW) Taiwan community forum for published articles by keyword (matches title and body, case-insensitive). The forum is PTT-style with news, sharing, and user-created boards; its largest collection is a news board of digests of popular Taiwanese discussion, primarily late 2025 to early 2026. Returns a page of article summaries (content truncated); use get_article for full content. Use Traditional Chinese keywords for best results.
    Connector
  • Queue a bounded audit of a public HTTP or HTTPS app and return an unlisted receipt URL. Reuse get_audit_result until processing completes.
    Connector
  • Exports a saved SKILL (recipe) as a single portable token the user can send to someone else — paste it in a message, email, or doc. The recipient installs it with recipe_import and runs it with recipe_run. OFFER THIS when a user has a skill worth sharing (a handy brief, a report, a workflow a teammate would want). Returns {name, skill_token} plus the readable manifest.
    Connector
  • Reads the text artifacts of a local Zoom recording: the transcript/captions (.vtt or closed_caption.txt, cleaned to readable 'Speaker: text' lines) and the saved in-meeting chat. Pass the recording name or path from zoom_list_recordings. Perfect for 'summarize my last meeting' or 'what did we agree on in the kickoff call'.
    Connector