MTG Deck Manager MCP Servers

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is MTG Deck Manager MCP Servers?

MTG Deck Manager MCP Servers is a project that provides Model Context Protocol (MCP) servers for interacting with Magic: The Gathering decks and card information directly through Claude.

how to use MTG Deck Manager MCP Servers?

To use the MTG Deck Manager, clone the repository, set up a Python virtual environment, and configure the servers in your Claude client to interact with your MTG decks.

key features of MTG Deck Manager MCP Servers?

  • MTG Deck Manager: Upload decks, draw cards, manage your hand, perform mulligans, and handle sideboarding.
  • Scryfall API Integration: Search for cards, get random cards, and look up card information.

use cases of MTG Deck Manager MCP Servers?

  1. Managing and organizing Magic: The Gathering decks.
  2. Drawing cards and managing gameplay through a digital interface.
  3. Searching for card information and random card generation.

FAQ from MTG Deck Manager MCP Servers?

  • Can I use MTG Deck Manager with any MTG deck?

Yes! You can upload any MTG deck list to manage your gameplay.

  • Is the Scryfall server stable?

The Scryfall server may occasionally crash due to ongoing development, so ensure both servers are running for optimal use.

  • What programming language is used for this project?

The project is developed in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
Python
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