Skip to main content
Glama
457,785 tools. Updated 2026-08-14 15:53

"How to create a Gantt chart for planning projects" matching MCP tools:

  • How to operate as a product manager on AIOProductOS. No arguments and no side effects — returns the same operating guide as plain text every call (deterministic): how to ground in the product brain, keep work welded to the spine (insight→feature→task→outcome), prioritise on evidence (affected accounts + MRR + reach), and what 'done' means. Call it FIRST, before planning or prioritising, to load the house rules the other tools assume.
    Connector
  • List extendable delegate candidates for a `receiver` and `resourceType` (ENERGY|BANDWIDTH). Optional `suggestData` scores an extend-and-buy scenario for planning purposes. Read-only; does NOT create orders or change on-chain state. Works without `mcp-session-id`; when a session is present, auth is forwarded so results can reflect the logged-in account where supported. NOTE: this is GraphQL market data for discovery only. To actually submit an extension, call the authenticated REST `POST /v2/get-extendable-delegates` with `extendData` (payload shape differs from this GraphQL response).
    Connector
  • Visualize a trained model's backtest — a cumulative-return chart + trade log + stats. Use after `one_shot` / `list_models` with the model's `stem` to SHOW the user how it traded (the "is it actually any good" view). In ChatGPT this renders an interactive widget. In Claude, render an interactive **artifact** from this tool's structured output: a line chart of the cumulative return plus a table of the trades. Args: stem: The model stem (e.g. "14_EURUSD_15min_Model_24") from `list_models` / `one_shot`. Returns: dict with: ok, stem, symbol, timeframe, stats {ret, wr, pf, n, mdd, sharpe}, and trades [{type, entry_time, exit_time, entry_price, exit_price, pnl, pnl_pct, exit_reason, period}] (most recent ~200). exit_reason is one of TP / SL / close_only / signal / end. ret/mdd/wr are fractions; pnl_pct is percent.
    Connector
  • List extendable delegate candidates for a `receiver` and `resourceType` (ENERGY|BANDWIDTH). Optional `suggestData` scores an extend-and-buy scenario for planning purposes. Read-only; does NOT create orders or change on-chain state. Works without `mcp-session-id`; when a session is present, auth is forwarded so results can reflect the logged-in account where supported. NOTE: this is GraphQL market data for discovery only. To actually submit an extension, call the authenticated REST `POST /v2/get-extendable-delegates` with `extendData` (payload shape differs from this GraphQL response).
    Connector
  • Search Epinu real-asset projects. Returns bounded summaries only; call projects_get_deep_dive for detailed packets. Results include public projects plus the token owner's own archived, draft, or unpublished projects for duplicate checks; another owner's unpublished projects are never returned. Available without a token for public results only.
    Connector
  • Returns a full Vedic birth-chart (janam kundali) summary for one person from their birth date, time and place: the lagna (ascendant) with sign, nakshatra, pada and lord; all nine grahas with sidereal sign, house, nakshatra, pada, dignity and retrograde/combust flags; the currently running Vimshottari mahadasha and antardasha with end dates, omitted only for a chart cast at the present moment, where no dasha has yet elapsed; and the most notable classical yogas detected, with a count of how many were found in all. Use this when the user wants their whole chart read. Prefer the cheaper, narrower sibling when the question is narrow: get_birth_details for only nakshatra / moon sign / lagna, get_dasha_periods for the full dasha timetable, get_upapada_arudha for the Jaimini layer, get_transits for where the planets are RIGHT NOW rather than at birth. Read-only deterministic computation (Swiss Ephemeris, Lahiri ayanamsa, whole-sign houses); no writes, no auth. Rate limits are counted per server instance: at least 30 requests/min/IP on this endpoint, plus a shared engine budget of at least 60/min/IP across all birth-chart tools. Accuracy depends on birth-time precision.
    Connector

Matching MCP Servers

  • F
    license
    -
    quality
    B
    maintenance
    An OAuth-protected MCP server that converts project descriptions into realistic schedules, handling dependencies, resource leveling, critical path analysis, and generating shareable charts (HTML, SVG, PNG, JSON, CSV).
  • A
    license
    -
    quality
    C
    maintenance
    A minimal MCP server with get_weather and create_ticket tools, used for testing MCP servers across protocol, unit, eval, transport, and auth layers.
    MIT

Matching MCP Connectors

  • Create and manage Gantt project charts directly from Claude — add tasks and milestones, link all four dependency types, duplicate/share charts, and export to Markdown, CSV, Mermaid, or .gantt. Backed by the free, no-signup ganttchartmaker.app, with cloud save and real-time collaboration.

  • World Bank Projects & Operations MCP.

  • Save durable information for future recall; skip transient chat. Existing Projects paths attach automatically. create_project is a deprecated ordinary-client compatibility input; model-routed project creation belongs to project(entity='project', action='create'). Use Ledger, not generic memory, for financial records.
    Connector
  • Create a dashboard with one or more widgets. Call get_skill with skillId: "dashboards" first — see skill for context-first workflow and inheritance rules. Put shared settings in `dashboardContext` (period required when chart widgets are present: prefer datePreset when possible, otherwise startDate/endDate; text-only dashboards may omit period; plus metricId, common groupBy, currency, optional conditionsCel). Chart widgets inherit by default and should only specify overrides: do not repeat from/to, datePreset, groupBy, metricId, currency, or conditionsCel when they match dashboardContext. The legacy `context` alias is temporarily accepted but deprecated; never send both. Text widgets use `{ type: "text", title, textContent }` — no queries or period. Comparison widgets add compare: omit its from/to to compare against the preceding period automatically (preset-aware), and set compare.chartType to WATERFALL (default), TABLE, or KPI_BREAKDOWN. Returns a URL — you MUST include it in your response. EXAMPLE: "AWS overview dashboard" → see skill dashboards Workflow A.
    Connector
  • Call when the user wants a visual overview rather than a narrative answer ("show me this week", "chart for today", "next 12 months", "看一下图"). Returns an ASCII chart: `hourly` = 12 two-hour blocks of one day, `weekly` = 7 days, `yearly` = 12 months. The `hourly` mode emits the same hour-resolution scores as `intentions_ask_hour` and is gated behind the Pro subscription on the same terms — on the free tier it returns a `subscription_required` error whose payload suggests `weekly` / `yearly` chart modes or `intentions_ask_day` as alternatives. `weekly` and `yearly` are always free.
    Connector
  • Calculate a relocation chart (relocated birth chart) for a new place on Earth. The birth moment stays the same, so every planet keeps its natal sign and degree, while the Ascendant, Midheaven, Vertex, and all twelve house cusps are recomputed for the new latitude and longitude. Returns the relocated houses and angles, the planets that change house, the angular planets activated at the new place, and the distance and compass direction from the birthplace. Built for relocation astrology readings, astrocartography style move planning, and travel charts. Verified against NASA JPL Horizons.
    Connector
  • Who is connected to Layero and how many projects they have. Call this first when you are unsure the token is configured: a clear error here is cheaper than one halfway through a deploy.
    Connector
  • Create a goal/task/milestone/habit in the planning tree. Two modes: grove (default) — enforces acceptance criteria gate on status transitions (AC required before in_progress, file-evidence per AC before done); standard — carries the same AC but without the evidence gate (advisory linting only). Returns the created goal with id, webUrl, mode, and nextStep hint. Every goal must belong to a project (pass projectId or inherit from parent).
    Connector
  • Create NPC mnemons (FACTION or INDIVIDUAL). npcType is REQUIRED on each item. Use memberNpcEntryIds (on FACTIONs) and affiliationEntryIds (on INDIVIDUALs) to wire membership; the server projects into MEMBER relationships. Players may not call this — GM/co-GM only.
    Connector
  • Use when you need the full natal chart for interpretation, comparison, or downstream transit/progression work. Returns planets, houses, aspects, patterns, dignities, and Big Three. `detail="compact"` drops the per-aspect details (keeps `aspects.summary` counts) and per-pattern planet lists — saves ~15k tokens on a typical chart, useful when you only need placements + angles. Next step: if you need aspect-by-aspect narrative material, call with `detail="full"`; for transits to this chart, call `current_transits` or `transit_search` with the same birth data.
    Connector
  • Use this when the user identifies a saved chart by id and wants to view it or retrieve its metadata and URLs. Displays the published chart when available and does not return its config; requires authentication.
    Connector
  • List extendable delegate candidates for a `receiver` and `resourceType` (ENERGY|BANDWIDTH). Optional `suggestData` scores an extend-and-buy scenario for planning purposes. Read-only; does NOT create orders or change on-chain state. Works without `mcp-session-id`; when a session is present, auth is forwarded so results can reflect the logged-in account where supported. NOTE: this is GraphQL market data for discovery only. To actually submit an extension, call the authenticated REST `POST /v2/get-extendable-delegates` with `extendData` (payload shape differs from this GraphQL response).
    Connector
  • Use this when the user wants to permanently save and publish a chart from a Szum config. Validate each generated or changed config once before rendering, saving, or updating. Do not revalidate unchanged input; a successful render preflights it for later saves or updates. Errors block; warnings require explicit user approval for the exact config. Suggestions do not block. Replace the complete config with suggestedConfig and revalidate before repair. Supply one idempotencyKey per intended chart and reuse it for retries. Returns permanent public Image and Embed URLs plus Edit and Studio links; requires authentication and saved-chart storage.
    Connector
  • Compare ONE indicator across MULTIPLE entities (e.g. GDP of DEU vs USA vs CHN). BY DEFAULT returns a per-entity summary (first/latest/min/max/avg/count) — enough to say who is highest and how current levels compare — plus row_count + x_range. Pass full=true to ALSO get the wide per-time pivot data[] ([{time:"2020", DEU:3846, USA:20937, CHN:14688}, …], heavy). Use this for country comparisons, cross-region analyses, or any chart that compares the same metric across entities.
    Connector
  • Dividend payment history for a ticker. Chart-ready: includes the current snapshot (yield %, payout ratio, frequency, annualised payout) plus two time series — a per-payment list [{ex_date, pay_date, amount, yield_pct, is_special, ...}] (newest first, capped at `count`) and an annual_totals list [{year, amount, yield_pct}] suitable for a yearly bar chart. All yields are emitted as percentages (4.5 = 4.5%), so plots don't need to know which underlying field used decimal vs. percentage encoding. Use for: "AAPL dividend history", "yield trend over 5 years", "dividend growth chart", "is the payout sustainable". Args: ticker: Stock ticker (e.g. 'AAPL', 'JNJ'). count: Number of most-recent individual payments to return (default 16, max 100). The annual_totals series is always returned in full.
    Connector
  • Get AI-computed market insights for a specific Bangalore project. Returns three computed signals derived from 2,700+ RERA projects: - Price intelligence: how this project's price/sqft (or starting price) compares to the locality median - Builder scorecard: track record — total projects, completed, lapsed, avg construction progress, verdict - Sales velocity: % units booked at this project vs the locality average Use this when the user asks: - "Is this fairly priced?" / "Is this good value?" - "Can I trust this builder?" / "What's the builder's track record?" - "Is this project selling well?" / "How popular is this project?" - Wants a data-driven assessment before booking a visit Requires a RERA number from search results. Call search_projects or get_project first if needed.
    Connector