Gumroad MCP Server

Created By
rmarescua year ago
A Model Context Protocol (MCP) server implementation for Gumroad API
Overview

What is Gumroad MCP Server?

Gumroad MCP Server is a Model Context Protocol (MCP) server implementation designed for Gumroad's API, allowing MCP-compatible AI clients to interact seamlessly with Gumroad's services.

How to use Gumroad MCP Server?

To use the Gumroad MCP Server, developers can integrate it with their MCP-compatible AI clients, such as Claude Desktop, to facilitate communication with Gumroad's API.

Key features of Gumroad MCP Server?

  • Implementation of the Model Context Protocol for Gumroad's API.
  • Enables interaction between AI clients and Gumroad services.
  • Actively developed with ongoing updates and improvements.

Use cases of Gumroad MCP Server?

  1. Integrating AI clients with Gumroad for automated tasks.
  2. Enhancing user experience by allowing AI to interact with Gumroad's offerings.
  3. Facilitating data retrieval and management through AI-driven applications.

FAQ from Gumroad MCP Server?

  • What is the purpose of the Gumroad MCP Server?

The Gumroad MCP Server serves as a bridge between MCP-compatible AI clients and Gumroad's API, enabling efficient communication.

  • Is the Gumroad MCP Server open source?

Yes! The Gumroad MCP Server is available on GitHub under the MIT license.

  • How can I contribute to the project?

Contributions are welcome! You can check the GitHub repository for guidelines on how to contribute.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
rmarescu
Star
9
Language
TypeScript
License
MIT license
Tags

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.

16 hours ago
Voyei

6 hours ago