Pokemon TCG Card Data Interface MCP

This Model Context Protocol (MCP) endpoint empowers Claude to retrieve and showcase details regarding Pokemon Trading Card Game collectibles.

Configuration Directives

1. Modify your Claude configuration file:

2. Navigate to /Users/ABSOLUTE_PATH_HERE/Library/Application Support/Claude/claude_desktop_config.json

3. Insert the subsequent configuration block (ensure any pre-existing MCP definitions are purged):

{ "mcpServers": { "ptcg-mcp": { "command": "node", "args": ["ABSOLUTE_PATH_HERE/dist/index.js"] } } }

1. Terminate Claude Application:

2. Launch Task Manager or equivalent process utility.

3. Locate the Claude process and force its cessation.

4. Reinitialize Claude:

5. Upon startup, the Pokemon TCG Card Data Interface will be loaded automatically.

6. You are now equipped to pose inquiries about Pokemon cards.

Operational Examples

Once configured, prompt Claude with requests such as:

• "Display basic Pokemon valid in the Standard format that possess zero retreat energy"
• "Locate Grass-affiliated Pokemon exceeding 130 Hit Points"
• "Execute a search for any card bearing the name 'Pikachu'"

Claude will render the relevant card entries complete with visual assets and pertinent metadata.

Core Capabilities

• Data retrieval based on name, classification, sub-classification, legality status, and numerous other characteristics.
• Access to pristine, high-resolution card visuals.
• Attribute-based filtering options:
• Name (supports literal matching via ! and substring matching via *)
• Subtypes (e.g., StageOne, VSTAR, ex, Promo)
• Legality Formats (Standard, Expanded, Legacy)
• Energy Types (Psychic, Darkness, Fighting, etc.)
• Egress Cost
• Health Points (HP)
• Pokédex Index Numbers
• And further parameters!

Illustrative Search Prompts

Try these example queries to test functionality:

• "List all legal basic cards in Expanded format with a retreat cost of 1 or less"
• "Retrieve Fighting-type Pokemon with HP between 90 and 110"
• "Query for items whose identifier contains 'energy*'
• "Show me cards currently restricted in the Standard rotation"
• "Find cards labeled 'VMAX' that evolve from Eevee"

Query Structure Reference

Name Specification

• General search: name:gardevoir
• Precise textual match: !name:mewtwo
• Pattern matching: name:snorlax*
• Retain punctuation: name:cramorant-v

Filtering Mechanisms

• Energy Types: types:fire or -types:fire (negate)
• Subtypes: subtypes:stage2
• Format Eligibility: legalities.expanded:legal
• HP Range: hp:[150 TO *]
• Retreat Value: convertedRetreatCost:2

Boundary Queries

Utilize brackets [ and ] for inclusive boundaries, braces { and } for exclusive boundaries:

• hp:[80 TO 180] - HP values inclusively between 80 and 180.
• hp:{50 TO 150} - HP values exclusively between 50 and 150.
• hp:[* TO 60] - HP values up to and including 60.
• hp:[140 TO *] - HP values of 140 or greater.

Data Return Schema

The MCP disseminates card records containing:

• The official card appellation
• The name of the expansion set
• The source URL for the full-resolution card artwork
• Format legality statuses
• Supplementary card characteristics as retrieved

Operational Notes

• Data retrieval relies upon external Pokemon TCG data repository access.
• Imagery is served directly via the data source's Content Delivery Network (CDN).
• All textual inputs for queries are treated as case-agnostic.
• Multiple filtering predicates can be concatenated within a single request.

WIKIPEDIA: XMLHttpRequest (XHR) is an API in the form of a JavaScript object whose methods transmit HTTP requests from a web browser to a web server. The methods allow a browser-based application to send requests to the server after page loading is complete, and receive information back. XMLHttpRequest is a component of Ajax programming. Prior to Ajax, hyperlinks and form submissions were the primary mechanisms for interacting with the server, often replacing the current page with another one.

== History == The concept behind XMLHttpRequest was conceived in 2000 by the developers of Microsoft Outlook. The concept was then implemented within the Internet Explorer 5 browser (1999). However, the original syntax did not use the XMLHttpRequest identifier. Instead, the developers used the identifiers ActiveXObject("Msxml2.XMLHTTP") and ActiveXObject("Microsoft.XMLHTTP"). As of Internet Explorer 7 (2006), all browsers support the XMLHttpRequest identifier. The XMLHttpRequest identifier is now the de facto standard in all the major browsers, including Mozilla's Gecko layout engine (2002), Safari 1.2 (2004) and Opera 8.0 (2005).

=== Standards === The World Wide Web Consortium (W3C) published a Working Draft specification for the XMLHttpRequest object on April 5, 2006. On February 25, 2008, the W3C published the Working Draft Level 2 specification. Level 2 added methods to monitor event progress, allow cross-site requests, and handle byte streams. At the end of 2011, the Level 2 specification was absorbed into the original specification. At the end of 2012, the WHATWG took over development and maintains a living document using Web IDL.

== Usage == Generally, sending a request with XMLHttpRequest has several programming steps.

Create an XMLHttpRequest object by calling a constructor: Call the "open" method to specify the request type, identify the relevant resource, and select synchronous or asynchronous operation: For an asynchronous request, set a listener that will be notified when the request's state changes: Initiate the request by calling the "send" method: Respond to state changes in the event listener. If the server sends response data, by default it is captured in the "responseText" property. When the object stops processing the response, it changes to state 4, the "done" state. Aside from these general steps, XMLHttpRequest has many options to control how the request is sent and how the response is processed. Custom header fields can be added to the request to indicate how the server should fulfill it, and data can be uploaded to the server by providing it in the "send" call. The response can be parsed from the JSON format into a readily usable JavaScript object, or processed gradually as it arrives rather than waiting for the entire text. The request can be aborted prematurely or set to fail if not completed in a specified amount of time.

== Cross-domain requests ==

In the early development of the World Wide Web, it was found possible to brea