Etsy MCP Server

Created By
vienle90a year ago
Overview

what is Etsy MCP Server?

Etsy MCP Server is a Model Context Protocol (MCP) server designed for integrating with the Etsy API, built using Node.js and TypeScript. It allows users to manage Etsy listings programmatically without needing to use the web interface.

how to use Etsy MCP Server?

To use the Etsy MCP Server, clone the repository, install dependencies, configure your Etsy API credentials in a .env file, build the project, and start the server. Then, authenticate with Etsy and connect it to Claude Desktop to manage your listings.

key features of Etsy MCP Server?

  • OAuth 2.0 authentication with Etsy API
  • Create draft listings
  • Upload images to listings
  • Retrieve taxonomy information (categories)
  • Compatible with Claude Desktop through the Model Context Protocol

use cases of Etsy MCP Server?

  1. Automating the creation of new Etsy listings.
  2. Uploading images to existing listings without manual intervention.
  3. Fetching category information for better listing management.

FAQ from Etsy MCP Server?

  • What are the prerequisites for using the Etsy MCP Server?

You need Node.js 16+, Yarn package manager, an Etsy Developer account with an API key, an Etsy Shop, and Claude Desktop.

  • Is there a graphical interface for managing listings?

No, the server is designed for programmatic access through Claude Desktop.

  • Can I run this server on any machine?

Yes, as long as the prerequisites are met, you can run it on any machine.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
vienle90
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago