Skip to main content
Glama
Sign In
sheetsdb-mcp-server

sheetsdb-mcp-server

by SarthakS97
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

SheetsDB MCP Server

A Model Context Protocol (MCP) server that enables Claude to interact with Google Sheets through the SheetsDB API.

Features

  • Smart Data Addition - Automatically detects empty vs existing sheets

  • Header Management - Uses SheetsDB's /keys endpoint for reliable header detection

  • CRUD Operations - Read, import, update, and delete sheet data

  • Simple & Reliable - Just 6 focused tools, ~150 lines of code

Related MCP server: Brainstorm MCP

Tools Available

  1. get_keys - Get column headers from sheet

  2. smart_add_data - Intelligently add data (import_json for empty sheets, create for existing)

  3. read_sheet - Read data from sheet

  4. import_json - Import JSON data to empty sheets

  5. update_row - Update specific rows

  6. delete_rows - Delete rows by criteria

Quick Start

Prerequisites

  • Node.js 18+

  • SheetsDB account and API endpoint

  • Claude Desktop or compatible MCP client

Installation

  1. Clone this repository:

    git clone https://github.com/yourusername/sheetsdb-mcp-server.git
cd sheetsdb-mcp-server

  2. Install dependencies:

    npm install

  3. Test the server:

    npm start

Local Claude Desktop Setup

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "sheetsdb": {
      "command": "node",
      "args": ["/path/to/your/sheetsdb-mcp-server/server.js"]
    }
  }
}

Deploy with Smithery.ai

  1. Push to GitHub:

    git add .
git commit -m "Initial commit"
git push origin main

  2. Deploy on Smithery.ai:

    • Go to Smithery.ai

    • Click "Deploy MCP with GitHub"

    • Select this repository

    • The mcp-config.json will be automatically detected

  3. Use in Claude:

    • Get your Smithery deployment URL

    • Add to Claude Desktop config or use directly

Usage Examples

Adding Meal Data

User: "Add chicken dinner (340 calories, 25g protein) to my calorie tracker: https://sheetdb.io/api/v1/your-id"

Claude will:
1. Call get_keys to check headers
2. Call smart_add_data with proper mapping
3. Either create headers (first time) or add to existing sheet

Reading Data

User: "Show me my last 5 meals"
Claude: [Uses read_sheet with limit=5]

Updating Entries

User: "Update yesterday's breakfast calories to 350"
Claude: [Uses update_row to find and modify the entry]

Configuration

The server expects SheetsDB endpoints in this format:

https://sheetdb.io/api/v1/YOUR_SHEET_ID

No additional configuration required - just provide the endpoint when using tools.

Security Notes

  • Endpoints are validated to ensure they're legitimate SheetsDB URLs

  • No API keys stored in the server (SheetsDB handles auth via URL)

  • All requests go directly to SheetsDB's secure endpoints

Contributing

  1. Fork the repository

  2. Create a feature branch

  3. Make your changes

  4. Test thoroughly

  5. Submit a pull request

License

MIT License - see LICENSE file for details

Support

  • Create an issue for bugs or feature requests

  • Check SheetsDB documentation for API-specific questions

  • See MCP documentation for protocol details

Available Tools

6 tools
delete_rowsB

Delete rows from a Google Sheet

Inputs: value (required), column (required), endpoint (required).

get_keysB

Get column headers (keys) from the first row of the sheet

Inputs: endpoint (required).

import_jsonA

Import JSON data to a Google Sheet (creates headers and data). Use for empty sheets or first-time setup.

Inputs: data (required), endpoint (required).

read_sheetB

Read data from a Google Sheet via SheetsDB

Inputs: endpoint (required), limit.

smart_add_dataB

Step 1: ALWAYS call get_keys first to check headers. Step 2: Based on keys result, either import_json (no headers) or create rows (has headers). This tool requires get_keys to be called first in the same conversation.

Inputs: data (required), headers (required), endpoint (required).

update_rowB

Update specific rows in a Google Sheet

Inputs: data (required), value (required), column (required), endpoint (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 6 tools

    Disambiguation3/5

    The tools are largely distinct (read, update, delete, get headers), but smart_add_data and import_json have overlapping responsibilities, and smart_add_data's dependency on get_keys creates a confusing workflow boundary.

    Naming Consistency4/5

    Most tools follow verb_noun naming (read_sheet, get_keys, update_row, delete_rows), but smart_add_data breaks the pattern with an adjective prefix and a less clear verb_noun structure.

    Tool Count5/5

    Six tools is well within the ideal range and covers core CRUD operations plus a helper for headers and a meta-tool for smart insertion, which feels appropriately scoped.

    Completeness4/5

    The set covers create (import_json/smart_add_data), read (read_sheet), update (update_row), and delete (delete_rows), but lacks a simple 'add_row' tool and the smart_add_data description references an undefined 'create rows' operation, leaving minor gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers