PuppyGraph MCP Server

Created By
puppygrapha year ago
Overview

what is PuppyGraph MCP Server?

PuppyGraph MCP Server is a Model Context Protocol (MCP) server designed for PuppyGraph, enabling users to query graph data using Gremlin and Cypher through Claude Desktop.

how to use PuppyGraph MCP Server?

To use the PuppyGraph MCP Server, clone the repository, install dependencies, and start the server using Node.js. Configure environment variables for connecting to PuppyGraph instances.

key features of PuppyGraph MCP Server?

  • Connects to PuppyGraph instances via Neo4j Bolt protocol and WebSocket.
  • Supports querying graph data with Gremlin and Cypher.
  • Retrieves graph structure and schema information from multiple endpoints.
  • Compatible with Claude Desktop and other MCP interfaces.
  • Includes robust fallback mechanisms for connection issues.

use cases of PuppyGraph MCP Server?

  1. Executing complex graph queries using Cypher and Gremlin.
  2. Integrating graph data querying capabilities into applications.
  3. Testing and troubleshooting graph database connections.

FAQ from PuppyGraph MCP Server?

  • What are the prerequisites for using PuppyGraph MCP Server?

You need Node.js 18+ and a running PuppyGraph instance.

  • How do I configure the server for Claude Desktop?

Set up the MCP server in your Claude Desktop configuration with the necessary environment variables.

  • What should I do if I encounter connection issues?

Check server logs, verify credentials, and ensure the remote server is accessible.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
puppygraph
Star
0
Language
TypeScript
License
Apache-2.0 license

Recommend Servers

View All
Payai X402 Tools

an hour ago
Payai X402 Tools

an hour 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.

a day ago