Gridly Server

Created By
sangcnguyena year ago
Overview

what is Gridly MCP Server?

Gridly MCP Server is a server application designed to manage projects, grids, databases, and more through the Gridly API.

how to use Gridly MCP Server?

To use the Gridly MCP Server, you need to install Node.js, set up the Claude Desktop app, and obtain a Gridly API key. You can then run the server using either npx or by cloning the repository for development.

key features of Gridly MCP Server?

  • Manage projects and grids efficiently
  • Access and manipulate databases through the API
  • Create, update, and delete grids and views
  • Add and delete records in views

use cases of Gridly MCP Server?

  1. Managing project data in a collaborative environment
  2. Automating database operations for applications
  3. Creating dynamic views for data representation

FAQ from Gridly MCP Server?

  • What are the system requirements for Gridly MCP Server?

You need Node.js (version 18 or higher) and Claude Desktop installed.

  • Is there a recommended installation method?

Yes, using npx is recommended for ease of use.

  • Can I run Gridly MCP Server in a development environment?

Yes, you can clone the repository and run it locally.

Server Config

{
  "mcpServers": {
    "gridly-server": {
      "command": "npx",
      "args": [
        "-y",
        "gridly-mcp-server"
      ],
      "env": {
        "GRIDLY_API_KEY": "your_api_key_here"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
sangcnguyen
Star
-
Language
-
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.

8 hours ago