Archidekt Deck Assistant logo
Archidekt Deck Assistant Collection-aware deckbuilding for your chatbot
Archidekt collection command center

A full deckbuilding website for your AI assistant.

Build deckbuilding prompts from your collection, connect ChatGPT or Claude, inspect every tool this server exposes, and sign in to Archidekt for private decks from one place.

Create a deck brief Connect Archidekt Checking sign-in mode...
Page 1

Deck Builder

Capture collection details, deck intent, format, budget, and write safety rules in a copy-ready prompt.

Open builder
Page 2

Connect

Copy the server URL and follow chatbot-specific setup for ChatGPT, Claude, or another MCP client.

Open connectors
Page 3

Account

Use the same OAuth-backed Archidekt sign-in flow to load private account and deck information.

Open account
1

What The App Does

It turns Archidekt collection and deck data into reliable chatbot tool calls.

Collection-aware

Every request carries an explicit collection locator so the assistant never guesses which inventory to use.

Deck-safe

Personal deck usage can be checked before reusing cards already committed elsewhere.

Write-gated

The generated prompt tells the chatbot to ask before creating or updating Archidekt decks.

Remote-ready

The MCP endpoint is prepared for remote connectors when hosted behind public HTTPS.

2

Application Map

Use these sections like a small product site, not a single debug console.

OverviewPurpose, flow, and major capabilities
Site
FunctionsMCP tools and HTTP helper routes
Reference
HostRuntime facts, health, and deployment notes
Ops
Deck Builder

Shape a deck request your chatbot can act on.

Fill in what you know. The page builds a prompt that tells the chatbot which tools to use and when to ask for confirmation.

1

Your Archidekt Collection

Use whichever identifier is easiest. Username is usually enough for public collections.

2

Deck Goal

Describe the deck in normal language. The prompt below turns this into tool guidance.

Chatbot Connectors

Connect the MCP server to the assistant you already use.

Copy the server URL, choose a chatbot guide, then paste the generated deck request in a new conversation.

1

Connection URL

This is the remote endpoint your chatbot should connect to.

Chatbot connection URL
Application Functions

Everything the assistant can do through this server.

Browse account, collection, search, and deck-writing functions without reading code or API docs.

Account And Private Context

Use these after Archidekt sign-in or with an account payload.

READ

login_archidekt

Resolves the Archidekt account and returns personal deck context.

READ

list_personal_decks

Lists private, unlisted, and public personal decks visible to the account.

Collection Intelligence

The collection locator is passed on every collection call.

READ

get_collection_overview

Returns totals, owner, game, page count, and fetched timestamp.

READ

read_collection

Reads the full Archidekt export and can write a local CSV when requested.

READ

check_collection_card_availability

Calculates free owned copies after personal deck usage.

WRITE

refresh_collection_cache

Forces a fresh snapshot when stale collection data is suspected.

Deck Operations

Writes should be confirmed by the user before the assistant performs them.

READ

get_personal_deck_cards

Loads deck cards and relation IDs before editing an existing deck.

WRITE

create_personal_deck

Creates a new personal deck and invalidates private deck caches.

WRITE

update_personal_deck

Updates metadata such as name, description, format, or visibility.

WRITE

modify_personal_deck_cards

Adds, changes, or removes deck cards using resolved IDs.

Website And HTTP Helpers

These routes support the website and browser workflows.

GET

/, /deckbuilder, /connect, /functions, /account, /host

Website pages rendered from the packaged Web UI template.

GET

/favicon.ico and /assets/*

Allowlisted generated logo and favicon files.

GET

/health

Runtime status and cache/auth configuration facts.

POST

/api/*

Browser helper routes that call the same service methods as MCP tools.

Archidekt Account

Sign in once, then use private decks and account-backed reads.

The browser uses the same OAuth authorization flow as remote MCP clients. No account JSON is required on this page.

Host And Runtime

Operational details for the person running the server.

Non-technical users can stay on the other pages. This section explains deployment, health, and public URL requirements.

MCP path/mcp
Transportstreamable-http
Stateless HTTPyes
Collection cache86400s
1

Public Hosting Checklist

Required when ChatGPT, Claude, or another cloud chatbot should connect.

  • Expose the same server behind HTTPS.
  • Set ARCHIDEKT_MCP_PUBLIC_BASE_URL to the public base URL when OAuth is enabled.
  • Keep the MCP path aligned with /mcp.
  • Protect Redis because it can hold OAuth sessions and Archidekt tokens.
  • Use trusted proxy headers only from known reverse proxy IPs.
Why localhost is different

A local browser can open this website at localhost, but cloud chatbots cannot reach your machine. Use a public HTTPS URL for remote connectors.