"How to query data in Snowflake" matching MCP servers:

Converts natural language queries into valid GraphQL queries and executes them against GraphQL APIs. Includes schema introspection, query validation, execution with authentication, and query history tracking.

MCP server that fetches API responses and generates ready-to-use model/POJO classes in your configured language, with built-in login/refresh token handling.

A FastMCP server that enables AI applications to navigate and query OpenAPI specifications, including resolving $ref pointers and inspecting paths and operations.

An MCP server that mocks payments, third-party API responses, and test data to enable QA flows for donation, checkout, SIP, and subscription pages without depending on a live gateway.

Enables AI assistants to query API documentation from Eolink Apikit instances via the Eolink Open API, supporting listing projects, groups, searching APIs by keyword/path, and retrieving detailed API definitions.

Enables Claude to create local, persistent mock REST APIs on demand from plain-language descriptions, with data written to disk so it survives restarts.

Enables agents to interact with the Logflare API by writing JavaScript functions that run in a Vercel Sandbox, using three tools: search, execute_read, and execute_write.

A stdio MCP server that audits other MCP servers over the live protocol. It connects to any MCP target (stdio or HTTP), lints every tool's schema for agent-usability, then actually calls the tools with deliberately broken inputs to see how the server handles them, and returns a 0–100 conformance score with a per-dimension breakdown rendered as Markdown.

Enables testing how different MCP clients handle tool results containing both content and structuredContent, including outputSchema enforcement and mismatch scenarios.

Provides comprehensive documentation for 377 Fortnox API endpoints and 81 resource categories directly from the official OpenAPI specification. It enables users to search, browse, and explore technical endpoint details and data schemas within AI assistants without requiring authentication.

MCP server for reading, writing, and organizing API documentation in Apidog.

A read-only API change deploy gate for AI coding agents that analyzes OpenAPI specs to determine if changes are safe to deploy. It provides tools for comparing specs, explaining breaking changes, and generating migration guides.

An MCP server for interacting with Treasure Data API, allowing users to retrieve database information and check server status through natural language queries.

Enables AI assistants to fetch and understand API endpoint definitions from Apifox projects in real-time. Supports retrieving complete API specifications including request methods, parameters, headers, and response schemas to improve development efficiency and code generation quality.

Converts any OpenAPI/REST API into MCP tools with dynamic server switching, variable substitution, and runtime configuration. Enables seamless interaction with multiple API environments through natural language without pre-configuration.

A Model Context Protocol server enabling AI assistants to interact with Kong Konnect's API Gateway, providing tools to query analytics data, inspect configurations, and manage control planes through natural language.

Point Claude at any API. JitAPI figures out which endpoints to call and in what order — automatically. Register any OpenAPI spec, search endpoints in plain English, and orchestrate multi-step workflows across multiple APIs. No API keys required — works out of the box with local embeddings.

A generic MCP (Model Context Protocol) server that bridges any GraphQL API to Claude Code. It introspects your GraphQL schema and exposes each query and mutation as an individual tool, letting Claude interact with your API directly.

Enables MCP-compatible AI clients to query, search, create, and update YApi API definitions and categories using natural language, with write operations excluding deletion for safety.

Enables AI agents to send HTTP requests to any endpoint with full control over methods, headers, query parameters, and request bodies.