Skip to main content
Glama
524,517 tools. Updated 2026-09-06 16:21

"Feature Implementation Planning Tools for Existing Projects" matching MCP tools:

  • List your projects. Each item is {projectId, code, name, apiStatus, dataStatus, language, customerId, customerEmail}. Call this FIRST when you don't know which project to act on, or when another tool returns project_id_required. Let the user pick, then pass the chosen projectId to the other tools. When you own a single project you usually don't need this — the other tools infer it. Pass `query` to search projects by name, code, or owner email. IMPORTANT: if the call returns an EMPTY list, do not assume there are no projects — some accounts only return projects that MATCH a search term, so ask the user what to look for (a project name/code or the owner's email) and retry with a `query`. A broad search may be capped, so keep the query specific. apiStatus GRANTED = active; REVOKED/OVERLIMIT projects are listed too so the user sees them. After the user picks, the usual next step is get_import_status for that projectId.
    ConnectorOAuth
  • 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.
    ConnectorNo auth
  • 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.
    ConnectorNo auth
  • 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.
    ConnectorOAuth
  • List condo/apartment projects we track, optionally filtered by district. Free - use this to discover valid project names before calling the paid stats/yield tools, rather than guessing at spelling.
    ConnectorNo auth
  • Promote an idea into a roadmap feature: creates a feature from the idea (name + description), stamps the idea 'promoted' and links it to the new feature, and returns the feature id. Idempotent — an already-promoted idea returns its existing feature. Resolve the id via list_ideas; only id is required. Align the new feature to an initiative/goal afterwards with update_feature.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    Facilitates software development planning through interactive sessions that break down projects into manageable tasks with complexity scoring, code examples, and implementation plan management.
    6
    20
    MIT

Matching MCP Connectors

  • Projects overview of the caller's board: one entry per top-level epic with recursive descendant progress (done %, counts by status, blocked, points, sub-epics, last activity), plus a triage strip of unrouted work (backlog + unassigned root tickets). Read-only, recomputed live. Use this before planning a session to see initiative health at a glance; use ticket_list/ticket_get to drill into any id it returns.
    ConnectorNo auth
  • Deletes the team account plus all projects and vaults. Requires X-API-Key (existing users can generate an API key in the web app). If headers aren't supported, pass api_key in arguments.
    ConnectorNo auth
  • Create a new project. Status: Planning|Active|On Hold|Completed|Cancelled|Archived (default Planning). budget_type: Fixed|Time&Material|Time (default Fixed). start_date and end_date are REQUIRED so team allocations render correctly in the UI. REVENUE RULES - a project may be created in Planning before its price is agreed, but it cannot leave Planning earning nothing. A database trigger holds it there, so this applies to the app too: • Fixed: `revenue` is the agreed contract sum. Required for any status other than Planning. • Time / Time&Material: revenue comes from logged hours x pricing-group rates, so pass `pricing_groups` (at least one {group_name, hourly_rate} above 0). Required for any status other than Planning; `revenue_ceiling` is the optional cap. manager_id is REQUIRED: a project with no manager never appears in anyone's awaiting-decision list, so when the nightly job closes it the decision reaches nobody. Anything you leave out comes back in `open_questions`. Those are not errors - the project is created - but put them to the user rather than leaving the project half filled in.
    ConnectorOAuth
  • Create a new bug report or feature-request issue in this tenant's issue tracker, filed in the 'open' status. Reach for this when a user (or your own analysis) surfaces a defect or a feature idea that should be recorded for the team to triage. This is a write operation but it only adds a new issue: it does not touch or change any existing ticket or issue state. [price: $0.02]
    ConnectorNo auth
  • List your Ranklogs projects, flattened into rows: project_id, domain, tracking type, engine/locale, keyword count, and top-line movement. Each row's project_id is a ranking id you pass to other tools. tracking_type is web, local, or YouTube. Demo/sample projects are flagged is_demo — do not treat them as the customer site. Call this tool first to get valid project_id values before calling anything else. Free — calling it never consumes lookups.
    ConnectorAPI key
  • Record one completed LeanSolver iteration against the current tracked contract. Result artifact refs must resolve to existing evidence or goal_attachment rows owned by this goal. Rework iterations accept only registered finding IDs and require a separate judged evidence row as repeatCheckEvidenceId; Planner derives the repeat verdict server-side. Only certificates admitted here may affect the numeric implementation rework rate.
    ConnectorNo auth
  • Use when providing monetary policy narrative context for a macro brief, investment committee, or CFO rate planning session. Returns illustrative cut, hike, and hold probabilities for the next three FOMC meetings based on current FRED fed funds data. Scenario planning tool — not futures-implied market odds. Example: Hold probability 68% at next meeting, cut probability 31% — conditioned on fed funds at 5.33% and latest CPI print. Source: FRED St. Louis Fed.
    ConnectorNo auth
  • List projects with structured filters (membership, progress state, health, category, tag, company, owner). For "my projects" pass user_ids with the ID from twprojects-get_user_me, or only_starred. For projects that have slipped pass project_statuses=["late"] — a project row carries no late flag, so this filter is the only way to ask.
    ConnectorNo auth
  • Returns the complete x711 tool catalog (34 tools) with pricing, free tier status, and ready-to-run examples. Optionally filter by category: perception, web, memory, onchain, payments, ai, comms, compute, economy, identity, social. Free, no API key needed. Use in agent planning loops to dynamically select the cheapest available tool for each sub-task.
    ConnectorNo auth
  • Get upcoming funding deadlines for planning an application schedule. Default compact mode returns a merged `results` list of lean rows (id/title/org/deadline/daysUntil and direct url when it fits) plus section counts/index ranges so grants and procurement stay balanced without duplicating every row. Pass compact:false for full descriptions, quality details, and full `sections.grants` / `sections.procurement` arrays. Non-biddable notices (Sources Sought, Award notices, etc.) and past/undated rows are excluded. Pass `category` to restrict to one type (e.g. "procurement" for contracts only). Paid feature. Counts toward your monthly searches.
    ConnectorNo auth
  • Project NZ annual leave balance forward under the Holidays Act 2003. Calculates hours accrued per week based on the holiday pay rate (8% standard NZ minimum), then projects the existing balance forward by the requested future period. Returns projected balance in hours, days, and weeks of equivalent leave. Use for any question about: annual leave accrual, future leave balance, planning time off, calculating entitlement after N months/years of work. NZ context: Holidays Act 2003 mandates minimum 4 weeks paid annual leave per year, which equates to 8% of hours worked accruing as leave. Employers may offer higher rates. Standard NZ full-time week is 40 hours across 5 x 8-hour days. Args: current_balance: Existing leave balance (in hours or days). current_balance_unit: 'hours' or 'days'. Default 'hours'. hours_per_workday: Standard workday length for this person (default 8). holiday_rate_pct: Holiday pay accrual rate (default 8% = NZ minimum). hours_per_workweek: Standard work-week (default 40). future_period: How far forward to project (default 12). future_period_unit: 'weeks', 'months', or 'years' (default 'months').
    ConnectorNo auth
  • Retrieve the verbatim source text (a "drawer") linked from a brain page. Use this when a summary lacks specifics you need — drawers contain the original tool output, redacted for credentials. Returns 404 if the page has no linked drawer (not all pages do — drawers are a Step 4 feature for allowlisted tools only).
    ConnectorNo auth
  • Returns the full text of one Fiveable AP study guide as Markdown. Accepts the exact canonical guide reference or a close approximation of its title. Suitable when a student asks to learn or review a topic. It consumes one full-content preview for a free caller unless existing access covers this subject and feature. Expensive — a full guide can be 3-8k tokens.
    ConnectorNo auth
  • Returns turva.dev's service catalog: the Shopify agent storefront check, agent-readiness audit, advisory, implementation, agent operations, and MCP server design, plus the engagement model and pricing (fixed list prices for the Shopify agent storefront check, audit, advisory and implementation; agent operations and MCP server design on request), and two implementation add-ons that carry a fixed price and are sold only together with the diagnosis they follow. Use this when a user asks what turva.dev offers, what it costs, or how an engagement works. Read-only: returns static JSON and changes nothing.
    ConnectorNo auth
  • Use when assessing EU AI Act compliance readiness ahead of the August 2, 2026 enforcement deadline or preparing a board AI governance briefing. Returns a composite payload with framework, deadline, total_controls, controls[], hint, and query timestamp, optionally filtered by NIST function from compliance_controls reference data. Example: Filter by MAP to review mapped EU AI Act controls and implementation statuses in the returned controls array for governance planning. Source: EU AI Act mappings in compliance_controls reference data.
    ConnectorNo auth