MCP Documentation
CardSight's Model Context Protocol (MCP) server exposes our complete trading card catalog and identification capabilities directly to AI assistants like Claude and ChatGPT. Enable your users to ask natural language questions about cards—"Which Bo Jackson rookie cards were released in 1990?"—and get instant, accurate answers powered by our 14M+ trading card database.
Unlike our REST API which is designed for developers building applications, the MCP server is designed for end-user experiences. Integrate it into your app to give users an AI-powered conversational interface for card search, identification, pricing, and catalog browsing. This documentation covers the available MCP tools, request/response formats, and integration guides for Claude Desktop and other MCP-compatible AI assistants.
Server URL
https://mcp.cardsight.aiProtocol
Streamable HTTP (MCP 2025-03-26)Option 1: URL Query Parameter (Recommended)
Best for Claude, ChatGPT, and other AI clients that support URL-based auth
https://mcp.cardsight.ai/?k=YOUR_API_KEYOption 2: HTTP Header
Use the X-API-Key header for custom integrations
X-API-Key: YOUR_API_KEYKey Format
32-character Alphanumeric (no hyphens)Example key: b5405bdf74c945769c6288202c6028ca
Available MCP Tools
Setup Examples
// Configure Claude Desktop to use CardSight MCP
// Add to ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"cardsight": {
"url": "https://mcp.cardsight.ai/?k=YOUR_API_KEY"
}
}
}
// Alternative: pass the key via headers instead
// {
// "mcpServers": {
// "cardsight": {
// "url": "https://mcp.cardsight.ai",
// "headers": {
// "X-API-Key": "YOUR_API_KEY"
// }
// }
// }
// }Real-time Updates
Tools reflect latest API capabilities
JSON Schema Validation
Type-safe parameter definitions