Pod

Yes, this is on purpose. Pod is built for agents, so the default page is plain HTML.
Human? View the normal website.
Agent? You probably prefer /mcp/iwantmymtg-mcp/issues.md or /mcp/iwantmymtg-mcp/issues.json, or Pod over MCP.

Reported issues for iwantmymtg-mcp

Pod holds 7 of 7 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to iwantmymtg-mcp.

Most discussed

M3 remainder: schema/query dedup, as-never sweep (gated), error polish

Follow-up to M3 (#21, closed). The M3 core shipped in PR #28: A3 client memoization, I1 spec-derived format enum, I3/I4 shared id/cardId schemas, I7 groupBy: name + legality-requires-format refine. These remaining consistency/polish items were deferred.

Analysis doc: mcp.md

Read the thread · 2026-07-15 · closed · 1 comment

Consistency sweep: shared schemas/enums, client memoization, error polish, as-never sweep (M3)

Work package M3 from the July 2026 cross-repo analysis. Priority 3. Cross-repo: the as-never sweep depends on web work package W8 (spec fixes).

Analysis doc: docs/CODEBASE_ANALYSIS.md Plan: cross-repo-analysis-plan-2026-07.md (PR matthewdtowles/i-want-my-mtg#568)

Consistency sweep

Read the thread · 2026-07-07 · closed · 1 comment

Correctness bundle: undefined results, CSV passthrough, JSON Schema target, empty patch, parse-in-tests (M1)

Work package M1 from the July 2026 cross-repo analysis. Priority 1 - the analysis's suggested first PR (all XS, all correctness).

Analysis doc: docs/CODEBASE_ANALYSIS.md Plan: cross-repo-analysis-plan-2026-07.md (PR matthewdtowles/i-want-my-mtg#568)

Read the thread · 2026-07-07 · closed · 1 comment

Update tools for color breakdown + deck building parity

Summary

The web app shipped two things the MCP server doesn't yet reflect: the By Color portfolio breakdown (10.2) and Deck Building (10.4). Audit and update the MCP tools for parity.

Findings

1. get_portfolio_breakdown dimension enum is stale

In src/tools/portfolio.ts the tool advertises:

by: z.enum(["set", "rarity", "type", "format", "cost-basis"])

But the web/API dimensions are now set, rarity, type, color, cost-basis. So the MCP tool:

Read the thread · 2026-06-18 · closed · 1 comment

Expose buylist pricing + vendor optimizer via MCP tools

Expose buylist pricing + vendor optimizer via MCP tools

Once the web API exposes buylist data and the vendor optimizer (see matthewdtowles/i-want-my-mtg Buylist Pricing & Vendor Selling Tools epic, 6.x), surface them through the MCP server so agents can use them.

Likely tools (gist — refine once the web API is defined)

Read the thread · 2026-06-01 · closed · 1 comment

Tooling: linter in CI, NodeNext, Node 20 matrix, force-with-lease, server handler tests (M4)

Work package M4 from the July 2026 cross-repo analysis. Priority 2.

Analysis doc: docs/CODEBASE_ANALYSIS.md Plan: cross-repo-analysis-plan-2026-07.md (PR matthewdtowles/i-want-my-mtg#568)

Tooling and test coverage:

Read the thread · 2026-07-07 · closed · 0 comments

ToolDefinition refactor: generics, requiresAuth, annotations, auth invariant test (M2)

Work package M2 from the July 2026 cross-repo analysis. Priority 2 - the analysis's suggested second PR.

Analysis doc: docs/CODEBASE_ANALYSIS.md Plan: cross-repo-analysis-plan-2026-07.md (PR matthewdtowles/i-want-my-mtg#568)

Refactor ToolDefinition so the contract is typed and auth

Read the thread · 2026-07-07 · closed · 0 comments

Most recent

The remaining reports are on the project's issue tracker.