SShortSingh.
Back to feed

GetQueryly Launches MCP Server and REST API for AI-Powered Data Analysis

0
·2 views

GetQueryly has released a data analysis platform offering both an MCP server and a REST API, allowing users to upload files in formats such as CSV, Excel, JSON, PDF, and Parquet for AI-driven querying. Users can ask questions in plain English and receive charts, explanations, and automated Quick Insight summaries based on their actual uploaded data. The tool integrates out of the box with AI clients like Claude and Cursor, addressing a common problem where AI assistants guess about data they cannot directly access. Operations are priced in a credit unit called 'Makes', with uploads being free and more complex analyses such as swarm runs costing up to six credits. A free tier is available for daily testing, with paid credit packs available for heavier usage.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingHacker News ·

Developer explains AI tool calling using just 40 lines of plain JavaScript

A developer has published a concise tutorial demonstrating how AI tool calling works using only 40 lines of vanilla JavaScript, with no external libraries required. The lesson, dated September 15, 2026, is part of a series hosted on the Buttercup platform. Tool calling is a key AI capability that allows language models to invoke external functions or APIs to complete tasks. The tutorial aims to demystify the concept by breaking it down into minimal, readable code. The post was shared on Hacker News, where it attracted early attention from the developer community.

0
ProgrammingDEV Community ·

Poja Uses Naming Conventions to Auto-Wire AWS Infrastructure for Spring Boot Apps

Spring Boot developers already rely on conventions like package placement and classpath scanning to wire application internals, but AWS infrastructure — queues, retries, permissions, and routing — typically still requires manual configuration. This gap means a simple requirement like async processing translates into a complex set of infrastructure decisions that developers must declare separately from their application code. Poja, a framework built on top of Spring Boot, extends the convention-over-configuration principle to cloud infrastructure by inferring SQS queues, dead-letter queues, and visibility timeouts from just two developer-defined values in the event class. Developers need only extend a base event class, name the consumer service after the event, and place both in expected packages — Poja resolves the wiring through string concatenation and calculated timeouts. The approach aims to eliminate the split between application logic and infrastructure declaration by treating AWS resource configuration as a derivable convention rather than an explicit task.

0
ProgrammingDEV Community ·

Charts.css, ProvChart, FSCSS: Three CSS-native charting tools without JS libraries

Three open-source tools — Charts.css, ProvChart, and FSCSS (st-core) — offer ways to render charts without shipping heavyweight JavaScript chart libraries, which typically add 40–150 KB to page load. Charts.css converts semantic HTML tables into visual charts using CSS classes, making it well-suited for accessible, content-driven pages like blogs and static sites. ProvChart compiles JSON data into scoped HTML, CSS, or SVG at build time, targeting performance-sensitive pages where first-paint speed and zero chart-runtime hydration are priorities. FSCSS (st-core) uses a dedicated .fscss syntax that compiles to native CSS, designed for design systems and component libraries shared across multiple frameworks. The three tools are not interchangeable but complementary, and organizations may use all three depending on whether charts appear in documentation, API-fed dashboards, or shared UI kits.

0
ProgrammingDEV Community ·

Microsoft Document Intelligence SDK Turns Scanned PDFs Into Structured Data for AI Pipelines

Microsoft's Document Intelligence SDK, formerly known as Form Recognizer, is a core but often overlooked component in AI document processing pipelines. The SDK offers two main clients: one for running document analysis and another for managing custom-trained models. It supports prebuilt models for common document types such as invoices, receipts, and IDs, as well as custom extraction models trained on user-labeled data. A classifier layer can route documents of unknown type to the appropriate model, making it practical for real-world pipelines that handle mixed document formats. The SDK can convert scanned PDFs into structured markdown, preserving headings and tables, which makes it particularly useful for retrieval-augmented generation applications.