Trino MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Trino MCP Server?

Trino MCP Server is a Model-Control-Protocol server that enables users to list and query tables via Trino using Python, facilitating big data analytics.

how to use Trino MCP Server?

To use the Trino MCP Server, configure the necessary environment variables for Trino connection details and run the server using the provided command structure.

key features of Trino MCP Server?

  • Lists Trino tables as MCP resources.
  • Reads table contents through MCP.
  • Executes arbitrary SQL queries against Trino.

use cases of Trino MCP Server?

  1. Querying large datasets efficiently using SQL.
  2. Integrating AI models with data sources for analytics.
  3. Bridging various data tools through the MCP protocol.

FAQ from Trino MCP Server?

  • What is the required Python version?

Python 3.9 or higher is required to run the server.

  • How do I configure the server?

The server configuration is done through environment variables for Trino connection details.

  • Can I use Trino with different databases?

Yes, Trino supports various catalogs like Hive, PostgreSQL, etc.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

17 hours ago