AI Deck

Changelog

Release notes and product updates for AI Deck.

1.8.0

Add to and organize your deck over MCP

New

  • Three deck-writing MCP tools: the AI Deck MCP server (https://api.ai-deck.app/mcp) can now edit your deck from a conversation. “Add the tool we just used to my deck” is something you can literally say to Claude
    • add_to_deck — add a service to your deck. It matches the catalog (500+ services) by name and URL and favorites the hit (any plan). Services outside the catalog are created as private services automatically on the Pro plan
    • move_in_deck — move a service to another area of your deck or reorder it
    • request_service_addition — ask the AI Deck team to add a missing service to the catalog (any plan)
  • API key scopes: when creating a key you now choose read-only (the default) or read & write. The writing tools require a read & write key

Safe by design

  • Every existing key stays read-only: keys you created before this release can never write to your deck. Create a new read & write key only when you want writing
  • Matching that avoids mistakes: when several catalog services match a name about equally, nothing is added — you get the candidate list instead. Adding the same service twice never corrupts your deck
  • Your own deck only: every writing tool operates exclusively on the deck of the key’s owner

How to use

  1. Create an API key with the read & write scope at Settings → Developer
  2. Add https://api.ai-deck.app/mcp to your MCP client with an Authorization: Bearer <key> header
  3. Just ask Claude: “add Perplexity to my deck”, “move it to my research area”
1.7.0

Read your own deck over MCP

New

  • New MCP tool get_my_deck: the AI Deck MCP server (https://api.ai-deck.app/mcp) can now return the deck of the API key’s owner — your areas and favorite AI services. Hand your AI agent (Claude and friends) the exact set of tools you actually use
  • Always live: unlike published decks, this is not a snapshot — it returns your deck as it is at call time, and you don’t need to publish anything
  • Customizations included: custom names, custom URLs and other overrides are resolved into the response. For large decks, filter to a single area with the area argument

Privacy by design

  • Private memos are never included: your personal notes are excluded at the query level — they never enter the response, and a permanent regression test guarantees it

How to use

  1. Create an API key at Settings → Developer
  2. Add https://api.ai-deck.app/mcp to your MCP client with an Authorization: Bearer <key> header
  3. Ask your agent to “show my deck” — it will call get_my_deck
1.6.0

Service articles are now public

New Features

  • Service articles are now public: Articles that previously required a login are now open to everyone, in both Japanese and English
  • Merged into the blog: Service articles now live in the blog, and the index has category tabs (Service Guides / Articles). A single article can be linked to multiple services, so comparison pieces are reachable from each service involved
  • Rebuilt changelog page: This page is now statically served as well, and no longer requires a login

Improvements

  • Article shortcut: The article icon on a service card takes you straight to that service’s guide
  • Faster pages: Articles and the changelog are now generated at build time as static pages, so they load faster — and search engines can index them properly
  • Fixed a layout issue in the blog index for posts without a thumbnail

Breaking Changes

  • Article URLs have changed: /articles/<serviceId>/blog/<slug>/ (Japanese: /ja/blog/<slug>/)
  • The changelog URL is now /changelog/ (trailing slash required), previously /changelog
  • The article APIs (/api/v1/articles, /api/v1/changelog, /api/admin/posts) and the admin post editor have been removed. Articles are now authored as Markdown files
1.5.0

Unified posts system

New Features

  • Unified posts system: Service articles, blog posts, and changelog entries are now managed in a single posts table
  • /blog page: Added a blog index and article pages
  • /changelog page: Switched to dynamic data (previously hardcoded)
  • Draft support: Publication state is controlled by the is_published toggle, and published_at is recorded automatically

Improvements

  • The Layer 2 (custom) precedence rule now applies to posts as well
  • The hasArticle flag in /api/v1/services is now based on the new posts table

Breaking Changes

  • /admin/articles/:serviceId/edit has been removed. Use /admin/posts/:id/edit instead
  • The legacy /api/admin/articles/:serviceId API has been removed and consolidated into the common CRUD /api/admin/posts