Skip to main content
Glama
811,679 tools. Updated 2026-11-20 15:18

"An exploration of software project management principles and practices" 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
  • Create a new versioned shared file in the caller's org. Shared files default to private. Call ``file_publish`` to generate the public share URL (``/s/{share_token}``). Each ``file_update`` creates a new immutable version row. Pass ``work_id`` to attach it to a task and/or ``project_id`` to attach it to a project (same ``shared_files`` row; project attachments are ``kind=artifact`` only). ``content_format='diagram'`` takes either diagram schema: - ``teamshared.diagram/v1`` — ``body: {format: mermaid, text: "..."}``, rendered as Mermaid. Best for flowcharts, sequences, and ER sketches. - ``teamshared.diagram/v2`` — ``body: {format: scene, layers: [...], nodes: [...], edges: [...]}``, rendered as a layered 3D scene where each layer is a plane (infra / software / data by convention), each node sits on one layer, and edges may cross layers. ``kind`` (default ``system``), ``view`` (``layers``), ``mode`` (``authored``) and ``body.camera`` are optional. Every node needs ``id`` and ``layer``; ``shape`` is ``box`` | ``cylinder`` | ``sphere`` | ``cone``; edges are ``{from, to, label?, kind?}`` with ``kind`` one of ``sync`` | ``async`` | ``data`` | ``depends``. Omit ``x``/``z`` to get an automatic grid on the plane. Caps: 8 layers, 300 nodes, 600 edges, 256 KiB. Unknown keys are rejected.
    ConnectorNo auth
  • List the contrib classes that extend, implement or use a core class, interface or trait, one row per edge with file and line, paged. Example: "who subclasses FormBase". Call-site counts: list_symbol_users. The symbol's status: lookup_core_symbol. - target: with or without the leading backslash. An unknown target is refused with a pointer at lookup_core_symbol; a fragment there lists candidates. rel_kind: one of extends, implements, uses_trait. project: one machine name. - Development branches only. edge_count: every edge. project_count: projects. count: edges after the per_project cap. project_edges on each row: the project's full count. per_project=50 with project= lists one project in full. - Rows are ordered by project installs, project, source_fqn. Each row: project, branch, installs, source_fqn, rel_kind, file, line, project_edges. limit ≤ 100. next_offset is absent on the last page.
    ConnectorNo auth
  • List all schemas of an API specification. Optionally include usage counts showing how many endpoints reference each schema. Set scope to 'project' to look across every spec in the project instead — that returns the groups of structurally identical schemas (candidates for the shared library) plus counts, not the full list, and specId is then ignored. Every entry carries the rowVersion update_schema needs, so a batch of updates does not need a get_schema per schema first. Use this to browse schemas or find a schema id; for one schema with its full definition use get_schema. Requires project context.
    ConnectorAPI key
  • Explore the project's app so TestOptim learns new or changed pages and flows. Use it after adding pages, before start_test_run; tests for what it finds are generated and approved in the TestOptim app. Spends the plan's page allowance and replaces an exploration already running. Returns an exploration id - poll get_exploration, which takes minutes.
    ConnectorAPI key
  • 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

Matching MCP Servers

Matching MCP Connectors

  • Upload a file from a public source URL into an ACC project folder. Runs the full four-step APS Data Management flow: top-folder discovery → storage object creation → OSS PUT of bytes → first-version item creation. When to use: The user wants to push a document/photo/model into ACC Docs — e.g. 'upload this site photo to the Tower project Photos folder' or an automation needs to archive an exported report into Project Files. When NOT to use: Do not use for files already in ACC; do not use for files behind auth-gated URLs (fetch step is an unauthenticated GET). For very large files (>100MB), prefer the chunked/signed-S3 upload flow, not this single-PUT implementation. APS scopes: data:read data:write data:create account:read. Rate limits: APS Data Management ~50 req/min per endpoint; OSS upload bandwidth typically 100 MB/min per app. This tool issues 3–5 APS calls per upload, so budget accordingly. Errors: 401 (APS token expired — refresh); 403 (user lacks folder write permission — ask account admin to grant 'Edit' on folder); 404 (project_id not found or folder_path does not match any top folder — verify 'b.' prefix, hub membership, and folder name); 422 (invalid file_name or conflicting version); 429 (rate limit — back off 60s); 5xx (ACC/OSS upstream — retry with jitter BUT be cautious: storage object may already be created so reuse, do not re-create). Also: if source file_url returns non-2xx, the tool throws before touching ACC. Side effects: Creates a storage object, uploads bytes, and creates a versioned item in the target folder. NOT idempotent — a retry may create a duplicate item with a new version. Surface the returned item_id to the user to avoid re-uploads.
    ConnectorNo auth
  • Evaluate an array of content items (headings, prose, CTAs, labels, captions, metrics, outcomes) against UX-writing principles and deterministic heuristics. Returns a per-item verdict (pass/warn/fail) with matched principle ids, concrete issues grounded in principle text, a before→after rewrite suggestion, and an aggregate summary. Heuristics: metric items must carry a number+unit; cta/label must be action-led and ≤4 words; prose flags passive voice, jargon, and hedging; headings flag filler openers and buzzwords; captions flag duplication of any heading in the batch. Pure offline — no network or browser. Use this instead of evaluate_design when you need per-item content verdicts rather than the principle library.
    ConnectorNo auth
  • Start linking a cloud account so it can be scanned. `provider` is "aws", the only provider supported today; `account_id` is the 12-digit AWS account number. `software` is the Tomorrow Central software the link is for; omit it for Cloud Cost Sentinel. Each software has its own read-only role, so link once per software. This is a two-party flow and you cannot finish it alone — creating the read-only IAM role requires the human's AWS credentials. Returns a `launch_url`. Hand the human these instructions verbatim: 1. Open the launch_url (a pre-filled CloudFormation quick-create link). 2. Review the read-only role it creates, then click Create stack. 3. Tell you when the stack says CREATE_COMPLETE. Then call `verify_connection` with the returned connection_id. Verification fails with a clear message until the role exists, so polling it every ~15 seconds is safe and expected. No ARN or secret needs to be copied by anyone.
    ConnectorNo auth
  • Archive a project (reversible shelve) — frees a project slot in-tool. Stops any in-flight machine, then flips the project to `archived`: it drops out of the per-tier project cap (freeing a slot for a new project) and the loop stops dispatching it, but the project + its history are kept and can be restored from the dashboard project page. Stopping a machine DESTROYS the running process state — restoring the project later cannot bring that execution back, so this is destructive despite being reversible. A replay on an already-archived project changes no row, but is not idempotent end to end. This is preferable to `delete_project` unless the project must be gone. Owner-scoped (an MCP key is owner-only); a project not in the workspace 404s.
    Connector
    Destructive
    No auth
  • Meaning-only search: ranks deployments by embedding similarity to the query, ignoring exact words. Use it when keyword search finds little because records use other words for the same idea, for example 'software that reads contracts and flags risky clauses'. To compare a fuller use case description, optionally within an industry, country or provider, prefer find_similar_usecases. Each result has a Similarity score from 0 to 1, Url (the original source) and HubUrl (its hub page).
    ConnectorNo auth
  • Free. Sends a message to the human operators of this service: a bug report, a problem with these tools or the documentation, or a suggestion. It is read by people, not processed by software, and nothing is returned beyond an acknowledgement. Do NOT use it for status updates, progress notes, task narration, error logs, or as a fallback when another tool is unavailable or a payment cannot be made -- it cannot complete, retry or work around any task. Name is optional (omit for anonymous feedback); message is limited to 1000 characters.
    ConnectorNo auth
  • Create a branded mineral exploration map from public registry claims and return a shareable URL. Provide at least one of search, location or claim_numbers. For a specific project, search its claims first and pass exact claim_numbers. Supply published facts and branding when known; never invent ownership, targets, grades or coordinates. Supports separate neighbouring claims, a project callout, locator inset, and map basemap selection. Drill and NI 43-101 layouts require user-supplied data or qualified review; this tool does not generate drill results. Free use allows 10 previews per hour; allowance in the result reports how many remain.
    ConnectorNo auth
  • Query the FCC Space Bureau's weekly satellite public notices since the ICFS cutover (2025-06-18) — every satellite application the FCC accepted for filing and every action it took (grants, partial grants, dismissals, surrenders), as printed. Use this for "what satellite filings has the FCC received or acted on since mid-2025" questions — the current licensing pipeline, which the pre-cutover docket (query_space_satellite_filings_v1) does not carry. Each record is one listing of a filing in one notice: the notice (`report_number` e.g. "SAT-02040", `notice_kind` "Applications Accepted for Filing" or "Actions Taken", `release_date`), the FCC `file_number` (e.g. "SAT-MOD-20260603-00225") and its `filing_type_code` (LOA, MOD, STA, AMD, T/C…), the `call_sign`, the `applicant` as printed (e.g. "Space Exploration Holdings, LLC"), the printed `date_filed` and `filing_type`, on Actions Taken notices the `action` (e.g. "Grant of Authority") and `action_date`, and the entry's full text as printed (`entry_text`, which carries the FCC's description of the request). Filter by `notice_kind`, `filing_type_code`, `action`, `applicant`, `report_number`, `file_number`, `call_sign`, `informative`, or the ranges `report_period_from`/`report_period_to` (release date), `date_filed_from`/`date_filed_to`, `action_date_from`/`action_date_to`. Group by `notice_kind`, `filing_type_code`, `action`, `applicant` or `report_number`. Pass each parameter as a top-level key of `params`. Example: `{"applicant": "Space Exploration Holdings, LLC", "include_records": true}` for SpaceX's listings; `{"notice_kind": "Actions Taken", "action": "Grant of Authority", "group_by": ["applicant"], "order_by": "source_record_count", "top_n": 10}` for the operators granted most often. Every record cites its line in the FCC's notice text, re-verifiable via get_source_evidence_v1. Read carefully: one filing can be listed in several notices, so `source_record_count` counts listings, not distinct filings. Values are what each notice prints: the same filing can show a different `date_filed` or applicant name in different notices. `action_date` is null when the notice prints none (the notice states its release date is then the effective date). The notices carry no status history and omit filings the FCC has not listed; a filing is never a satellite count, an orbital catalog or launch activity. Earth-station (SES) notices are out of scope.
    ConnectorNo auth
  • Use this when the user has a specific question for 7IT that describe_studio does not answer. Ask 7IT Solutions, a solo senior software studio, a question about whether it fits a project, what a first phase could cover, how engagements run, or what the client owns. Answers come only from 7IT's published profile and contain no prices or commitments; questions that need a quote are passed to our team, which replies directly.
    ConnectorNo auth
  • Publish an R3 project live: makes a RELEASE (a frozen copy) of the project as it is now and makes it the one its public live URL shows, for anyone. Only when the user asked for it. Changing the project does NOT change the live site; r3_publish_live does: on a project that is already live this is a publish update (a new release replaces the live one), and the answer names the release number and what changed since the previous live release. `note` (optional, up to 500 characters) is stored with the release. `slug` (optional, the first time a project goes live) is the project part of its public address (e.g. "my-game" for …/<handle>/my-game: letters, numbers and dashes); without it R3 uses a free address (the project's name when free) and the answer says which. Once a project has been live its address never changes. Going live the FIRST time uses one of the live-project slots of the project owner's plan (an update uses none); going live needs a plan. When there is no plan or no room, nothing is published and the answer says how many live projects the plan allows, how many are used and where the user picks a plan. It publishes every change kept so far (yours and the user's: there is nothing to save first). r3_release_list shows the releases, r3_release_rollback makes an older one live again. Needs the publish:live right.
    Connector
    Destructive
    No auth
  • Re-runs an existing usability-test project ("relaunch", "re-run", "run again", "same test") with a fresh batch of AI testers on the same project. Unlike propose_usability_test + launch_usability_test, it does not create a new, duplicate project. Takes `projectId` (the testId from an earlier launch) and an optional `numTesters` for this run. Without `uploadId` it re-runs against the design already hosted for the project (a live public URL serves its latest version); tell the user you are re-running the existing design with no new snapshot. For an updated snapshot-hosted design, pass a new uploadId — it must first be verified with check_design_snapshot and the preview shown to the user for their OK that it is the version and state they want; TheySaid rejects an unverified snapshot (SNAPSHOT_NOT_VERIFIED). Passing it re-points the same project to the new design; the result echoes designRefreshed: true and its startedMessage states which design ran. It does not change the audience or questions; audience changes are saved first with revise_usability_test(projectId). Returns the same testId (reusedProject: true), the resolved `audience` and a `startedMessage`. Spends AI-tester runs. Results come from wait_for_results or get_test_results.
    Connector
    Destructive
    OAuth
  • Find live software by keyword before building from scratch. Public, no sign-in needed. Returns descriptions, USD license prices, tech stacks and listing links. Example: {"search": "invoice", "limit": 5}. Empty search browses recent software. When hasMore is true without nextCursor, narrow the search. Matching is lexical. Errors set isError; retry a rate limit later. Use z2h_compare_marketplace_listings for a shortlist or z2h_show_marketplace for cards. A result does not guarantee suitability or purchase availability.
    ConnectorNo auth
  • Add a list of up to 50 tasks to an existing Onplana project in one call, at the project root or under a sprint / epic. Fits "add these tasks to my launch project" or a checklist pasted into the chat. Single transaction (all-or-nothing), in place of calling create_task N times; add_subtasks covers new tasks that are children of an existing task. THIS TOOL DOES NOT SCHEDULE. Tasks land with NO dates unless startDate and dueDate are set on each one, and there is no way to express durations or predecessors here at all. A schedule (phase durations, effort estimates, "task 5 depends on task 3", a critical path) sent through this tool arrives as a flat dateless list, and the Gantt, timeline and critical path are all empty. Use instantiate_plan instead, which takes estimatedDays per task and computes real start and due dates from them. It accepts a projectId, so it works on a project that already exists. Neither tool accepts predecessors: create the tasks first, then add each dependency with link_dependency. The result includes `url` for the project (and one per task). ALWAYS show the project link in your reply so the user can open what you just created.
    ConnectorOAuth
  • Ask the AI to propose a new schedule for a project that fits all tasks before a target deadline while respecting dependencies. Returns an array of {taskId, startDate, dueDate} proposals (YYYY-MM-DD strings), any warnings, and feasibility status. Use mode="preview" (default) to inspect the proposal first; use mode="apply" to capture a baseline and commit the dates immediately (requires project Owner or Manager role). Cap: 100 tasks per project. Use when the user asks "can we finish by [date]?" or "reschedule this project to meet the deadline".
    Connector
    Destructive
    OAuth
  • Get the join link of an AccountHub shared project (shared project) — NOT a Slack workspace. Unlike invite_to_shared_project it is not tied to an email address: anyone who opens it, signs in to AccountHub and agrees joins the project as themselves. One link per project: the same `url` on every call until it expires (`expires_at`, 14 days), then a new one is made. regenerate: true replaces it and the old link stops working at once (people who already joined stay). Nothing is sent: give the `url` yourself (e.g. through send_message). Any active member can call it; not available for a 1:1 chat.
    Connector
    Destructive
    OAuth