Skip to main content
Glama
649,985 tools. Updated 2026-10-09 19:15

"Angular" matching MCP tools:

  • Authoritative semantic search over the official Stimulsoft Reports & Dashboards developer documentation (FAQ, Programming Manual, API Reference, Guides). Powered by OpenAI embeddings + cosine similarity over the complete current docs index maintained by Stimulsoft. Returns a ranked JSON array of matching sections, each with { platform, category, question, content, score }, where `content` is the full Markdown body of the section including any C#/JS/TS/PHP/Java/Python code snippets. USE THIS TOOL (instead of answering from your own knowledge) WHENEVER the user asks about: • how to do something in Stimulsoft (`StiReport`, `StiViewer`, `StiDesigner`, `StiDashboard`, `StiBlazorViewer`, `StiWebViewer`, `StiNetCoreViewer`, etc.); • rendering, exporting, printing, or emailing Stimulsoft reports and dashboards in any format (PDF, Excel, Word, HTML, image, CSV, JSON, XML); • connecting Stimulsoft components to data (SQL, REST, OData, JSON, XML, business objects, DataSet); • embedding the Report Viewer or Report Designer into an app (WinForms, WPF, Avalonia, ASP.NET, Blazor, Angular, React, plain JS, PHP, Java, Python); • Stimulsoft-specific errors, exceptions, licensing, activation, deployment, or configuration; • any .mrt / .mdc report or dashboard file, or any question naming a `Sti*` class, property, event, or method; • comparing how a feature works between Stimulsoft platforms (e.g. "WinForms vs Blazor viewer options"). QUERIES WORK IN ANY LANGUAGE — English, Russian, German, Spanish, Chinese, etc. Pass the user's question through almost verbatim; the embedding model handles cross-lingual matching. Do NOT translate queries yourself. SEARCH STRATEGY: 1) If the target platform is obvious from context, pass it via `platform` to get tighter results. 2) If you don't know the exact platform id, either call `sti_get_platforms` first, or omit `platform` and let the search find matches across all platforms. 3) If the first search returns low scores (<0.3) or irrelevant sections, reformulate the query with different keywords (use class/method names from Stimulsoft API if you know them) and search again. 4) Prefer multiple focused searches over one broad search. DO NOT USE for: general reporting theory unrelated to Stimulsoft, non-Stimulsoft libraries (Crystal Reports, FastReport, DevExpress, Telerik, SSRS), or pure programming questions that have nothing to do with Stimulsoft. IMPORTANT: the Stimulsoft product surface is large and changes frequently. Your training data is almost certainly out of date. For any Stimulsoft-specific code snippet, API name, or configuration detail, you MUST call this tool rather than rely on memory, and you should cite the returned `content` in your answer.
    ConnectorNo auth
  • Authoritative semantic search over the official Stimulsoft Reports & Dashboards developer documentation (FAQ, Programming Manual, API Reference, Guides). Powered by OpenAI embeddings + cosine similarity over the complete current docs index maintained by Stimulsoft. Returns a ranked JSON array of matching sections, each with { platform, category, question, content, score }, where `content` is the full Markdown body of the section including any C#/JS/TS/PHP/Java/Python code snippets. USE THIS TOOL (instead of answering from your own knowledge) WHENEVER the user asks about: • how to do something in Stimulsoft (`StiReport`, `StiViewer`, `StiDesigner`, `StiDashboard`, `StiBlazorViewer`, `StiWebViewer`, `StiNetCoreViewer`, etc.); • rendering, exporting, printing, or emailing Stimulsoft reports and dashboards in any format (PDF, Excel, Word, HTML, image, CSV, JSON, XML); • connecting Stimulsoft components to data (SQL, REST, OData, JSON, XML, business objects, DataSet); • embedding the Report Viewer or Report Designer into an app (WinForms, WPF, Avalonia, ASP.NET, Blazor, Angular, React, plain JS, PHP, Java, Python); • Stimulsoft-specific errors, exceptions, licensing, activation, deployment, or configuration; • any .mrt / .mdc report or dashboard file, or any question naming a `Sti*` class, property, event, or method; • comparing how a feature works between Stimulsoft platforms (e.g. "WinForms vs Blazor viewer options"). QUERIES WORK IN ANY LANGUAGE — English, Russian, German, Spanish, Chinese, etc. Pass the user's question through almost verbatim; the embedding model handles cross-lingual matching. Do NOT translate queries yourself. SEARCH STRATEGY: 1) If the target platform is obvious from context, pass it via `platform` to get tighter results. 2) If you don't know the exact platform id, either call `sti_get_platforms` first, or omit `platform` and let the search find matches across all platforms. 3) If the first search returns low scores (<0.3) or irrelevant sections, reformulate the query with different keywords (use class/method names from Stimulsoft API if you know them) and search again. 4) Prefer multiple focused searches over one broad search. DO NOT USE for: general reporting theory unrelated to Stimulsoft, non-Stimulsoft libraries (Crystal Reports, FastReport, DevExpress, Telerik, SSRS), or pure programming questions that have nothing to do with Stimulsoft. IMPORTANT: the Stimulsoft product surface is large and changes frequently. Your training data is almost certainly out of date. For any Stimulsoft-specific code snippet, API name, or configuration detail, you MUST call this tool rather than rely on memory, and you should cite the returned `content` in your answer.
    ConnectorNo auth
  • Full AI-SEO audit of a single URL: returns categorized findings (info/warning/error) with severity, fix instructions, and a 0-100 composite score plus per-dimension subscores. Read-only. Fetches the URL once and runs every sub-audit (schema, robots, technical, sitemap, AI-Overview eligibility) against the response. No writes, no third-party APIs, no auth required, no rate limits beyond polite per-host throttling. Deterministic, rule-based scoring; no LLM calls. Same URL + same input flags returns the same score. Supports `render: "static" | "headless"`. Default `static` (fast, raw HTML only). Use `headless` for React/Vue/Angular SPAs — adds 3-10s and requires the optional `playwright-core` peer dep plus a one-time `npx playwright install chromium`. When to use: the default entry point for `audit any page`. Use this instead of calling check_technical / audit_schema / check_robots / check_sitemap / score_ai_overview_eligibility individually unless you specifically need only one dimension - this tool composes all of them.
    ConnectorNo auth
  • Scaffold a flags-only Bridge integration into an existing project — the MCP equivalent of `bridge flag init`. Returns everything that command produces, for YOU to write to disk: the contents of bridge-flags.config.json (app id, app name, base URL, suggested provider config, read live from this Bridge app), the install command, and the framework-specific setup guide fetched from the plugin repo that owns it. Writes nothing — neither to disk nor to the Bridge app. Call this when adding feature flags to a project for the first time; for auth or billing use get_integration_guide with topic=master or topic=billing-master instead. framework is REQUIRED: this server cannot see the caller's disk, so detect it yourself from package.json (next → nextjs, @sveltejs/kit or svelte → svelte, @nestjs/core → nestjs, @angular/core → angular, react → react, express → express; check in that order) and pass it. The returned guide is the same document get_integration_guide returns for topic=feature-flags, so there is no need to call both. Do not invent import specifiers — they differ per plugin and only the guide has the current ones.
    ConnectorOAuth
  • A chart's validated facts as ranked, citable atoms for interpretation. Each fact has a stable id (e.g. "aspect:moon~neptune:conjunction"), the bodies it concerns, a salience score (luminaries, angular placements, the chart ruler, tight/hard aspects, configurations rank high), and a plain-language statement. Facts span placements, aspects, configurations, the structural signature, dispositors and receptions, a body's tight conjunction with a bright fixed star (e.g. "star:jupiter:Sirius"), and the Part of Fortune and Spirit (e.g. "lot:fortune"). Read the facts, write the interpretation in your own words, and cite the [id] each statement rests on — do not introduce facts not listed. Returns the ranked facts plus a ready-to-interpret `brief`. By default a real birth chart: pass date+lat+lon. The chart's grounding is first-class via `realm` (what it is: observed/forecast/fictional/mythic/archetypal/…) and the time: an exact `date`, an uncertain `earliest`+`latest` range (the brief then frames it as provisional and trusts the Moon/angles/houses less), `constraints` for an archetypal chart with no time (synthesized via the compiler), or a full structured `when` (relative-to-another-event or a narrative calendar). A `when` of kind `relative` looks its `anchorId` up in `anchors` (a map of id → UTC instant supplied in the request). Omit lat+lon for a placeless chart (nominal houses).
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • AI development agent using Kendo UI to rapidly create and style quality web UIs or Pages.

  • List, search, and inspect Ply Angular + Tailwind copy-in components.

  • The one-call "what is up right now" answer. For an observer location and instant, iterate every naked-eye solar-system body (and, with include_stars, the bundled bright stars), compute altitude and azimuth, keep those above the horizon, rank them brightest-and-highest first, and attach a plain-language visibility note to each, along with its angular distance from the Sun. The whole sky is gated by the Sun's altitude into daylight / civil / nautical / astronomical twilight / dark, returned alongside the list, and each note says when daylight, civil twilight, or the Sun's glare hides or dims that body. `time` is a single evaluation instant, not a window — for "tonight" pass a time after astronomical dusk (use astronomy_get_rise_set on the sun to find it). Default elevation 0 m; use min_altitude to skip objects grazing the horizon. This server does not geocode — resolve coordinates upstream first; pass an IANA timezone for observer-local times on each body.
    ConnectorNo auth
  • Read the Bridge integration guide for a topic — the supported, opinionated way to consume Bridge from application code. Call this BEFORE writing or changing app code that reads a feature flag, renders billing or team UI, or wires authentication, and before hand-rolling anything against the SDK: the SDKs ship declarative surfaces for these cases (components, route guards, decorators) and reimplementing them against SDK internals is the most common integration mistake. Per-framework topics (framework REQUIRED): integration (first-time setup) | auth | feature-flags | billing | team | branding. Framework-agnostic MASTER topics (framework is IGNORED — omit it): master, the end-to-end auth integration prompt served by `bridge guide`, which orchestrates project discovery and then routes to the per-framework guides; flags-master and billing-master, the same orchestration for a flags-only or billing-only integration; mechanisms, how limits, upgrades and customization work; orientation, what Bridge does (the same map get_started returns); fit-together, how roles, plans, limits and flags fit together; integration-success, the message to show the developer when an integration is done. Before setting up flags, roles, plans or limits, read topic=fit-together. Start at topic=master when integrating Bridge into a project for the first time. framework: svelte | react | angular | nextjs | nestjs | express — pass the one the target app actually uses; this server cannot detect it. Returns the guide as markdown plus its source URL. Guidance is a default, not a mandate — follow the user's stated preference when it differs.
    ConnectorOAuth
  • Get the harmonic constituents NOAA uses to compute tide or current predictions at a station — the amplitude, phase, and angular speed of each tidal constituent (M2, S2, N2, K1, O1, ...). For water-level stations: amplitude (feet/meters), phase_GMT and phase_local (degrees), speed (degrees/hour). For current stations (alphanumeric IDs) constituents are current ellipses (major/minor amplitudes and phases per depth bin — pass bin to filter). Use for: building custom tide computations, checking a station's dominant constituents (M2 amplitude indicates semidiurnal range), verifying whether a station is harmonically predicted at all. Only reference (R) stations have constituents — subordinate stations use offsets (noaa_get_prediction_offsets).
    ConnectorNo auth
  • Compute the apparent topocentric position of one solar-system body (sun, moon, mercury through neptune, pluto) or a named bright star for an observer location and instant. Returns equatorial (RA/Dec), refraction-corrected horizontal (altitude/azimuth), and ecliptic coordinates, plus distance, apparent magnitude, angular diameter, phase angle, illuminated fraction, angular distance from the Sun, and the constellation it falls in. For a solar-system body it also returns that body card — classification, mean radius, naked-eye visibility — the same values served at astronomy://body/{body}, so a client without resource support does not need a second surface to reach them; a catalog star has no card and the field is absent. Positions are parallax- and aberration-corrected for the given observer; default elevation is 0 m and the default time is now. Supply `star` (e.g. "Sirius", "Polaris") instead of `body` to target a catalog star; `body` is ignored when `star` is set. Pass an IANA `timezone` to also receive the observer-local time. This server does not geocode — resolve a place name to latitude/longitude upstream first.
    ConnectorNo auth
  • Semantic (meaning-based) search over the Handsontable + HyperFormula documentation knowledge base — docs guides, code recipes, blog posts, release notes and GitHub issues. Returns ranked page-level snippets with title, content, relevance score, url and provenance (framework, kind, htVersion/hfVersion). `url` is null when no public page exists (recipes, releases, issues) — never fabricate a link. Scores are rank-only. Guides repeat once per framework (javascript/react/angular/vue) — dedupe on url/title when you need distinct documents. Pass ht_version/hf_version (your installed releases) to get an explicit coverage note when the KB documents a different version.
    ConnectorNo auth
  • Используйте, когда пользователь ищет актуальные IT или Digital вакансии по поддерживаемой профессии. Например: разработчики Python, Java/Scala/Kotlin, Go, Node.js, C#, PHP, C++/C, React, Vue, Angular; iOS, Android, Flutter, React Native, KMP; 1С, SAP, WordPress, CRM/low-code; Unity, Unreal, гейм-дизайн; DevOps, системный администратор, сетевой инженер, DBA, кибербезопасность, Embedded/IoT; ручное и автоматизированное тестирование; бизнес-, системный и дата-аналитик, BI/DWH/ETL; Data Scientist, Data Engineer, AI инженер, MLOps; UI/UX, продуктовый, графический, Motion и 3D-дизайн; тимлид, CTO, CDO, Product/Project менеджер, Scrum Master; digital-, performance-маркетолог, SMM, контент-маркетолог, DevRel, рекрутер, HRBP/HRD, C&B; вайбкодинг. Это примеры, а не исчерпывающий список; сначала сопоставьте профессию с get_professions. HireSeeker объединяет вакансии hh.ru, других площадок, Telegram и сайтов компаний. Доступны формат работы, страна, город, зарплатные диапазоны, период, язык и группы источников. Поиск без регистрации; по умолчанию 7 дней, все доступные языки и 5 вакансий со ссылками на HireSeeker. Не используйте для советов по резюме, оформления отклика, подписки, платежей или отсутствующей профессии. Первый вызов — criteria; продолжение — только cursor. Зарплата задаётся диапазонами сайта; грейд, точный порог и свободный текст не поддерживаются. Для таких условий сначала объясните ограничение, предложите доступные фильтры и запросите явное согласие пользователя. До согласия не вызывайте поиск и не заменяйте его ручной проверкой описаний или пересчётом валют. По умолчанию покажите по каждой вакансии работодателя, зарплату с валютой, формат и место работы, краткие задачи, требования и условия, а также open_url. Не выдавайте только заголовки, если пользователь явно не просит этого. description — фрагмент: для нескольких показываемых карточек с description_truncated=true сначала вызовите get_vacancies (до пяти ID за раз), для одной — get_vacancy. При отсутствии сведений пишите «не указано»; не выводите их из названия. total_items — размер снимка на searched_at; снятые вакансии могут сократить страницу. Пустая страница с next_cursor не означает конец выдачи; продолжение определяется next_cursor.
    ConnectorNo auth
  • Используйте, когда пользователь ищет актуальные IT или Digital вакансии по поддерживаемой профессии. Например: разработчики Python, Java/Scala/Kotlin, Go, Node.js, C#, PHP, C++/C, React, Vue, Angular; iOS, Android, Flutter, React Native, KMP; 1С, SAP, WordPress, CRM/low-code; Unity, Unreal, гейм-дизайн; DevOps, системный администратор, сетевой инженер, DBA, кибербезопасность, Embedded/IoT; ручное и автоматизированное тестирование; бизнес-, системный и дата-аналитик, BI/DWH/ETL; Data Scientist, Data Engineer, AI инженер, MLOps; UI/UX, продуктовый, графический, Motion и 3D-дизайн; тимлид, CTO, CDO, Product/Project менеджер, Scrum Master; digital-, performance-маркетолог, SMM, контент-маркетолог, DevRel, рекрутер, HRBP/HRD, C&B; вайбкодинг. Это примеры, а не исчерпывающий список; сначала сопоставьте профессию с get_professions. HireSeeker объединяет вакансии hh.ru, других площадок, Telegram и сайтов компаний. Доступны формат работы, страна, город, зарплатные диапазоны, период, язык и группы источников. Поиск без регистрации; по умолчанию 7 дней, все доступные языки и 5 вакансий со ссылками на HireSeeker. Не используйте для советов по резюме, оформления отклика, подписки, платежей или отсутствующей профессии. Первый вызов — criteria; продолжение — только cursor. Зарплата задаётся диапазонами сайта; грейд, точный порог и свободный текст не поддерживаются. Для таких условий сначала объясните ограничение, предложите доступные фильтры и запросите явное согласие пользователя. До согласия не вызывайте поиск и не заменяйте его ручной проверкой описаний или пересчётом валют. По умолчанию покажите по каждой вакансии работодателя, зарплату с валютой, формат и место работы, краткие задачи, требования и условия, а также open_url. Не выдавайте только заголовки, если пользователь явно не просит этого. description — фрагмент: для нескольких показываемых карточек с description_truncated=true сначала вызовите get_vacancies (до пяти ID за раз), для одной — get_vacancy. При отсутствии сведений пишите «не указано»; не выводите их из названия. total_items — размер снимка на searched_at; снятые вакансии могут сократить страницу. Пустая страница с next_cursor не означает конец выдачи; продолжение определяется next_cursor.
    ConnectorNo auth
  • Paid tier only. Calling this without an authenticated CivilQuants account returns TIER_INSUFFICIENT — sign up at https://civilquants.com/pricing or use the free-tier alternative compute_cantilever_wall. Modular gabion retaining wall built from welded or hexagonal-mesh wire baskets filled with hard angular graded stone (SHW Cl. 622). The first non-concrete retaining structure in the platform and the FIRST member of the earth_structures L1 leaf — opening Phase E. Spans four structural forms via the gabion_form discriminator: STACKED_RECTANGULAR (standard highway boundary), STACKED_STEPPED (architectural / heritage), BATTERED (tall walls with back batter), and FACING_MATTRESS (Reno-type mattresses for slope facing / scour protection). Eight variant presets exercise the parameter form covering all four gabion_form values: highway boundary, landscape, stepped front, heritage stepped, battered, river training, scour apron, and tall battered. Routes via three new WorkCategory entries (GABION_BASKET, GABION_FACING_MATTRESS, STONE_FILL) — the first session where the classed-then-legacy discriminator pattern is applied to fundamentally new measurement vocabulary rather than to existing concrete categories. Codes: CESMM4 E.8.1-3 (Class E — Earthworks), NRM2 5.20-22 (Group 5 — Excavating and filling), MMHW 600.12-14 (Series 600 — Earthworks; SHW Cl. 622/623), and SMM7 D41.1/D41.2/D20.20 (D41 — Crib walls / gabions / reinforced earth — the only standard with a NAMED home). 16th use of the discriminator pattern, first applied to new WorkCategories rather than legacy ones. Example params: wall_height=3 m (0.1–8), wall_length=25 m (5–200), basket_length_m=2 m (1–3). Example call: {"params": {"wall_height": 3, "wall_length": 25, "basket_length_m": 2}, "standard": "MMHW"}. Omitted parameters use sensible engineering defaults. Pass deliverables=["xlsx","dxf","pdf"] (any subset) to also receive one-shot download URLs in the same call: Excel BoQ (both tiers, watermarked free) plus the dimensioned DXF (CAD) and PDF drawing sheets (paid tier).
    ConnectorNo auth
  • Read the official usage examples of one Ionic Framework component, as published on its documentation page. Use this before writing markup for a component to see how it is actually used in Angular, React, Vue or vanilla JavaScript — the template, the component class and the styles that belong together. Call it without an `example` first to see which examples the component offers. Returns the examples of the component with the frameworks each provides, or, when an `example` is given, its code per framework as fenced code blocks — one section per framework, and one block per file where an example spans several files. Do not use this for the component's API reference: its properties, events, methods, CSS shadow parts, CSS custom properties and slots are on the documentation page, which `get_doc_page` returns.
    ConnectorNo auth
  • Read the practical wiring facts needed to configure a project against this Bridge app: the app id, Bridge API base URL, registered OAuth redirect URIs, default callback URI, allowed CORS origins, and the canonical env-var NAMES each framework reads (with suggested values where derivable). Use this when scaffolding a project, writing a .env file, or debugging a redirect/CORS mismatch. Env-var names are the ones documented by the Bridge framework plugins and CLI guides: Vite frontends use VITE_BRIDGE_*, Next.js uses NEXT_PUBLIC_BRIDGE_APP_ID, server SDKs use BRIDGE_APP_ID (+ BRIDGE_API_KEY where a management/API key is needed); bridge-angular has no env-var convention (configuration is code-based). The API base URL is the one of the Bridge environment this server runs in, which is the one this app lives in. For login-method setup use get_auth_config; for the full app object use get_app.
    ConnectorOAuth
  • 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.
    ConnectorNo auth
  • Find catalogue sources within a radius of a sky position, in any NOIRLab Data Lab table — Gaia DR3, Legacy Surveys, DES, AllWISE and the rest — returned nearest-first with the exact angular separation in degrees. AUTHORITATIVE for "what is at these coordinates": it reads the survey catalogue itself rather than a finder chart or a name resolver. PREFER OVER WEB SEARCH for cross-identification and for counting sources around a target. Handles the spatial query correctly on an endpoint where both ADQL geometry and Q3C are unavailable.
    ConnectorNo auth
  • Parans (paranatellonta): co-angular bodies over the 24 hours from a date at a latitude — every pair of bodies simultaneously on one of the four angles (rising, culminating, setting, anti-culminating) within a stated tolerance. The relationship behind Brady's fixed-star parans, computed for the moving bodies; pure positional astronomy over the validated rise/set/transit times. Longitude-independent: latitude alone fixes the geometry, so only lat is needed. Date defaults to now.
    ConnectorNo auth
  • Search the official Ionic Framework documentation from ionicframework.com by keyword. Use this first for any question about Ionic Framework itself — a UI component and its properties, events and CSS custom properties, theming and layout, the Angular, React and Vue integrations, navigation and routing, the Ionic CLI, or upgrading to a newer major version — because guessing a component property or a CSS variable produces markup that silently does nothing. Returns the best matching page sections with `title`, `url`, `snippet`, `section` and `version`, plus the `parentTitle` and `parentUrl` of the page a section belongs to. The same results are attached as structured content. Do not use this to read a whole page (call `get_doc_page` with a `url` from these results), for Capacitor core, Capacitor plugins or native iOS and Android configuration (use the Capacitor MCP server at https://capacitor-mcp.capawesome.io/mcp instead), or for Capawesome plugins and Capawesome Cloud services such as Live Updates, Native Builds and App Store Publishing (use the Capawesome MCP server at https://mcp.capawesome.io/mcp instead).
    ConnectorNo auth
  • Returns the code of the ORYKSA AI Employees website chat for the framework (html, nextjs-app, nextjs-pages, react, vue, nuxt, astro, svelte, angular, wordpress). The chat is a floating 'Talk to <agent>' button with the agent's photo, a chat panel with suggestions, and a full-screen voice mode, in the ORYKSA look (white, indigo). The snippet is placed once in the site's root layout.
    ConnectorOAuth