Official MCP server providing AI assistants with direct access to Stimulsoft Reports & Dashboards developer documentation. Enables semantic search across FAQ, Programming Manual, Server Manual, User Manual, and Server/Cloud API references across all Stimulsoft platforms (.NET, WPF, Avalonia, WEB, Blazor, Angular, React, JS, PHP, Java, Python).
Scored across 2 tools
The two tools have clearly distinct purposes: sti_get_platforms lists available platforms, while sti_search performs semantic search over documentation. There is no overlap in functionality, and the descriptions reinforce their separate roles.
Both tools share the 'sti_' prefix and use lowercase snake_case. sti_get_platforms follows a verb_noun pattern, while sti_search is just a verb, which is a minor deviation but still predictable.
With only two tools, the server feels minimal. However, for a documentation-focused MCP server, the count is borderline acceptable, as the two tools cover the primary use case of discovering and searching documentation.
The surface covers the essential workflow: enumerate platforms and search for answers. Minor gaps exist, such as no direct fetch by document ID or category browsing, but the search tool returns full content, mitigating the need for additional endpoints.
List every Stimulsoft product/platform that has indexed documentation available through this MCP server. Returns a JSON array of { id, name, description } objects covering the full Stimulsoft Reports & Dashboards product line (Reports.NET, Reports.WPF, Reports.AVALONIA, Reports.WEB for ASP.NET, Reports.BLAZOR, Reports.ANGULAR, Reports.REACT, Reports.JS, Reports.PHP, Reports.JAVA, Reports.PYTHON, Server API, etc.).
CALL THIS FIRST when the user's question is ambiguous about which Stimulsoft platform they are using, or when you need to pick a valid platform value to pass into sti_search. The returned platform id values are the exact strings accepted by the platform parameter of sti_search.
This tool is cheap (no OpenAI call, no vector search) — call it freely whenever you are unsure about platform naming.
Inputs: no named parameters.
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.
Inputs: query (required), limit, category, platform.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.