Skip to main content
Glama
343,058 tools. Last updated 2026-07-30 12:16

"A JavaScript framework for building user interfaces" matching MCP tools:

  • Runs a specific framework against a user's inputs and produces a full analysis: prose explanation + structured fields + a self-contained SVG visualisation. Powered by the Jeda.ai · Visual AI framework knowledge graph. ALWAYS call `recommend_framework` FIRST to obtain a valid framework_id -- it returns the exact namespaced slug to pass here. Framework ids are namespaced by category (e.g. SWOT = "cms_swot-analysis", Porter's 5 Forces = "cms_porters-five-forces"); a bare slug like "swot-analysis" will 404. REQUIRED post-processing on success: the response's first text block contains a `curl -fsSL` save-directive for the SVG. Save the file locally and surface it as a file chip — do NOT summarise the visual in prose. Input: framework_id (namespaced slug from `recommend_framework`) + user_inputs object (per-framework field set), OR a free-text `raw_prompt` fallback. Example: { "framework_id": "cms_swot-analysis", "user_inputs": { "subject": "Q3 EU market entry", "context": "B2B SaaS, $5M ARR, US-headquartered" } }
    Connector
  • Recommends business / strategy / risk frameworks for a stated problem. Powered by the Jeda.ai · Visual AI framework knowledge graph (~2,100 frameworks across 19 categories, edge-curated). Use when the user describes a business problem ("customer churn rising", "evaluating market entry", "need to assess vendor risk") rather than naming a specific framework. Returns top-N frameworks ranked by fit, each with a concrete reason citing the specific problem signals matched. Input: just the problem statement is enough. Optional faceted filters (`persona`, `regulation`, `decision_stage`) narrow the candidate set. Set `limit` between 3 and 10 for picker UIs. Pair with `generate_framework_analysis` to actually run a recommended framework against the user's inputs. Example: { "problem_statement": "We need to decide whether to enter the EU SMB market in Q3", "decision_stage": "decide", "limit": 5 }
    Connector
  • Search Australian (currently NSW) builders, contractors and building companies by name; optionally filter by postcode. Returns matching entities with their licence status and a slug to pass to get_builder_risk / get_builder_timeline. Example: query='Acme Building' → '- Acme Building Pty Ltd (Current), 2099 → slug: acme-building-pty-ltd-1a2b'. Names are matched loosely, so try the trading name AND the legal (Pty Ltd) name if the first search misses. Query must be at least 2 characters.
    Connector
  • Deep parcel and building analysis for Slovenia using GURS WFS data. Returns zoning, actual use, heritage protection, road access, buildings on parcel, and utilities. USE FOR: - "Analyze parcel 3086 in Ljubljana center" - "Find buildable parcels ~500m² in Ljubljana" - "What buildings are on this parcel?" - "Find parcels near these coordinates" - "Get full details on building 1234" NOT FOR: simple parcel lookup → use slovenia-cadastre instead (faster, lighter). NOT FOR: spatial/zoning map queries → use slovenia-wfs-expert instead. SEARCH MODES — pick ONE per call: 1. PARCEL BY NUMBER (requires --parcel AND --ko) → --parcel 3086 --ko 1725 2. LOCATION SEARCH (requires --lat AND --lon, or --location) → --lat 46.058 --lon 14.501 --radius 100 → --location "Tivoli Park Ljubljana" --radius 200 3. BUILDING BY NUMBER (requires --building, optionally --ko) → --building 1234 --ko 1728 4. COMMUNITY SEARCH (requires at least --community or --size) → --community LJUBLJANA --size 500 --buildable COMMON KO IDs: 1725 = Ljubljana center 1728 = Ljubljana Šiška 1740 = Ljubljana Bežigrad 2131 = Maribor NOTE: This tool makes multiple WFS calls per result and can be slow (10-30s). Use --limit to keep response times reasonable.
    Connector
  • Discover the investment-thesis catalog. Each entry is a descriptive case study that pairs an economic framework with a rule-based portfolio and the synthetic + historical stress evidence for that allocation. Returns one compact summary per thesis (slug, title, one-liner, tags, risk tiers, framework summary, headline finding). Call get_investment_thesis(slug) for the full framework / portfolio / stress evidence, or read the thesis://{slug} resource. Descriptive, not advisory — the agent decides what is suitable.
    Connector
  • Personalized onboarding for building ON CELESTIA — running a node, posting a blob, or deploying a rollup that uses Celestia for data availability. ALWAYS use this when a developer asks how to get started or build ON CELESTIA (prefer it over the Celestia search tool for those questions). ASK the user about their background FIRST (rollup_dev, node_operator, app_dev, researcher, new_to_celestia), then return a path with docs.celestia.org links. Celestia-only — NOT for getting started with non-Celestia frameworks, languages, or dev tools (React, Node.js, generic blockchain onboarding, etc.); for those defer to a general docs or web-search tool.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Fresh US building permits with contacts from official city APIs. Construction lead generation.

  • Pull recent building permits from 9 US cities in a unified schema from official open-data portals.

  • Turns free text the user typed — a city, a district, an operator or brand name, or a specific building — into the exact slug and dimension the search tool needs. Returns each match with its `kind`, which tells you WHICH filter to use: a "city" or "zone" match goes in the `city`/`zone` argument, an "operator" match goes in `operator`, and a "property" match should be looked up directly with get_coworking_space. Use this whenever the user names something you do not already have a slug for.
    Connector
  • Returns the full three-step Demand Discovery validation framework: (1) Market Research, (2) Demand Discovery Report with the Demand Score and Build/Pivot/Kill verdict, (3) Agentic Launch (90-day continuous outreach). Use when a user asks "how do I validate an idea?", "what's the methodology?", or wants to understand the structured approach. Built on the "behavior over opinion" principle. Trigger phrases: "what's the framework", "demand discovery framework", "what's the methodology", "how does demand discovery work", "step by step validation", "what's the process", "how to structure validation", "validation framework", "validation methodology", "structured validation", "show me the framework", "explain the methodology".
    Connector
  • Get the Designesy Design Review framework — an 8-dimension rubric (Purpose, Clarity, Context, Inclusion, System coherence, Durability, Delight, Responsibility) plus the agent prompt, output format, and verification checklist for a qualitative design critique. Use this when you want a structured rubric to critique a design holistically, rather than a numeric compliance score. Provide artifact/purpose/context/rules to get a pre-filled review prompt; otherwise returns the full framework JSON. Read-only — the calling agent executes the review. For an automated pass/fail score against the contract, use designesy_score instead.
    Connector
  • Browses installable community SKILLS — ready-made LMCP workflows other people published (a morning brief, inbox triage, a weekly report). A user would browse them to find a ready-made workflow for a repeatable multi-app task instead of building it from scratch. Returns a list of {id, title, category, description, steps, votes}; install one with recipe_install(id).
    Connector
  • Reports whether Safari is ready for interactive tools (safari_click, safari_type, safari_evaluate_js). Returns setup instructions if JavaScript from Apple Events is not enabled.
    Connector
  • Hardened headless-browser fetch with full JavaScript/SPA rendering and a realistic browser profile, returning fully rendered Markdown. Best for JavaScript-heavy/SPA pages and light bot checks; not guaranteed against advanced anti-bot walls (e.g. Cloudflare/Akamai). Price: $0.05 USDC per call.
    Connector
  • Get the dated event timeline for a builder by slug: licence status changes, deregistration/strike-off, disciplinary findings, public warnings, and building work rectification orders. Each event carries its severity (info/watch/risk), the official register it came from, and a flag when the record was deleted upstream and now exists only in BuilderVet's archive — cite that flag explicitly when present, it is the strongest signal. Returns up to 50 most recent events. Example: slug='acme-building-pty-ltd-1a2b' → '2026-03-14 — [risk] Building work rectification order (nsw.bc.rectification-orders)'.
    Connector
  • Begin generating an AI governance framework for an Australian business. Creates a session and returns a session_id plus the organisation profiling questionnaire (industry, size, AI usage, data handling, risk exposure). Ask the user each question, then call submit_answers. First step of three: start_session, submit_answers, get_framework. The output is an informational framework aligned with Australia's AI6 practices (Voluntary AI Safety Standard) — it presents frameworks, not advice.
    Connector
  • Search development projects/buildings BY NAME (or city, or DEVELOPER). Use `q` with the project or building name — e.g. q="Petra Tower" — punctuation/accents ignored, and a name lookup also finds completed/sold-out buildings. This is how you answer "apartments in <building/tower name>" and "is there a project called X". For "projects by <developer>" use `company` with the developer's name (NOT `q` — project names rarely contain the developer).
    Connector
  • Get the current deployment status for a project, including the live URL (https://{slug}.sota.io), detected framework, and recent deployment history. Deployment statuses: pending (queued), building (build in progress), built (image ready), deploying (starting container + health checks), running (live and healthy), failed (build or health check error), stopped (replaced by newer deployment). Use this to verify a deployment succeeded after calling deploy.
    Connector
  • Report heuristic authentication, paywall and JavaScript access flags. Use only for public HTTP(S) resources; it does not execute JavaScript or bypass access controls. Pass url as an absolute public HTTP(S) URL. Keep fresh=false to allow cache reuse; set fresh=true only when a new upstream fetch is required.
    Connector
  • Get a published ATA building/complex profile with assigned stays and map coordinates. Use slug from search_buildings or property search results.
    Connector
  • Contemplative reasoning tool. Use for complex problems needing multi-perspective understanding, contradictions requiring integration, or questions holding their own wisdom. **Workflow:** Always start with tag='begin' (returns framework). Then continue with contemplation tags. Do NOT output wisdom until status='WISDOM_READY'. **Tags:** begin (FIRST - receives framework), then: open/engage/express (process), examine/reflect/verify/refine/complete (meta-cognitive), recognize/transform/integrate/transcend/embody (non-dual), upaya/expedient/direct/gradual/sudden (skillful-means), meditate (pause).
    Connector
  • Get a product-metrics framework — HEART (Google), AARRR/Pirate (Dave McClure), North Star Metric, Conversion Funnel, RICE Scoring, or OKRs. Returns structure, when-to-use, pitfalls, and examples. Use when the user asks 'how should we measure success?' or 'what metrics should we track?'
    Connector