MCP GraphQL

Created By
setyolegowoa year ago
Overview

What is MCP GraphQL?

MCP GraphQL is a GraphQL API service designed for the Mission Control Platform (MCP), providing a flexible and efficient interface for querying and manipulating MCP data.

How to use MCP GraphQL?

To use MCP GraphQL, clone the repository, install the necessary dependencies, and run the service using Node.js.

Key features of MCP GraphQL?

  • Flexible querying capabilities through GraphQL.
  • Efficient data manipulation for MCP services.
  • Easy integration with existing Node.js applications.

Use cases of MCP GraphQL?

  1. Querying MCP data for analytics and reporting.
  2. Integrating MCP services with other applications.
  3. Building custom dashboards using MCP data.

FAQ from MCP GraphQL?

  • What are the prerequisites for using MCP GraphQL?

You need Node.js and npm or yarn installed, along with access to MCP services.

  • Is MCP GraphQL open source?

Yes! MCP GraphQL is open source and available on GitHub.

  • What license is MCP GraphQL under?

MCP GraphQL is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
setyolegowo
Star
0
Language
TypeScript
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.

8 hours ago