google-sheets-mcp-server-by-cdata

Created By
CDataSoftwarea year ago
This read-only MCP Server allows you to connect to Google Sheets data from Claude Desktop through CData JDBC Drivers. Free (beta) read/write servers available at
Overview

What is Google Sheets MCP Server by CData?

This project is a read-only Model Context Protocol (MCP) Server that allows users to connect to Google Sheets data from Claude Desktop through CData JDBC Drivers.

How to use Google Sheets MCP Server?

To use the server, clone the repository, build the server, install the CData JDBC Driver, configure your connection, and create a configuration file for Claude Desktop.

Key features of Google Sheets MCP Server?

  • Provides a read-only interface to Google Sheets data.
  • Allows LLMs to query live data using natural language.
  • Simplifies data access without requiring SQL knowledge.

Use cases of Google Sheets MCP Server?

  1. Querying live data from Google Sheets for analysis.
  2. Integrating Google Sheets data with AI applications.
  3. Automating data retrieval for reporting purposes.

FAQ from Google Sheets MCP Server?

  • Can I write data to Google Sheets using this server?

No, this server is read-only. For write capabilities, consider the full CData MCP Server for Google Sheets.

  • Is there a cost to use this server?

The server is currently in beta and is free to use.

  • What programming language is used for this project?

The server is built using Java.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
CDataSoftware
Star
0
Language
Java
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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.

29 minutes ago