create-ampless 0.2.0-alpha.20 → 0.2.0-alpha.21

package/dist/templates/_shared/AGENTS.ja.md

@@ -60,9 +60,7 @@
 
 エージェントが投稿コンテンツを直接クエリ・編集できる。公開ツール: `list_posts`、`get_post`、`create_post`、`update_post`、`delete_post`、`upload_media`、`get_schema`。
 
-登録方法は 2 つ:
-
-**ローカル stdio（Claude Code / Cursor 向け、推奨）:**
+登録方法:
 
 プロジェクトルートの `.mcp.json` に追加する:
 ```json
@@ -80,8 +78,6 @@
 }
 ```
 
-**管理者発行トークンによる HTTP**（ホスト型エージェント向け）: `/admin/mcp-tokens` で Bearer トークンを発行し、エージェントクライアントを公開 MCP HTTP エンドポイントに向ける。エンドポイント URL は管理 UI で確認できる。
-
 投稿本文は `markdown`、`html`、`tiptap`（JSON ドキュメント）の 3 フォーマットに対応している。
 
 ## 動作確認の基準

package/dist/templates/_shared/AGENTS.md

@@ -60,9 +60,7 @@ This file is written for AI coding agents (Claude Code, Cursor, Codex, etc.). Fo
 
 Lets agents query and modify post content directly. Tools exposed: `list_posts`, `get_post`, `create_post`, `update_post`, `delete_post`, `upload_media`, `get_schema`.
 
-Two registration options:
-
-**Local stdio (recommended for Claude Code / Cursor):**
+Registration:
 
 Add to `.mcp.json` at the project root:
 ```json
@@ -80,8 +78,6 @@ Add to `.mcp.json` at the project root:
 }
 ```
 
-**HTTP via admin-issued token** (for hosted agents): issue a Bearer token at `/admin/mcp-tokens` and point the agent client at the public MCP HTTP endpoint. See the admin UI for the exact endpoint URL.
-
 Post bodies accept three formats: `markdown`, `html`, or `tiptap` (JSON document).
 
 ## Verification expectations

package/dist/templates/_shared/README.ja.md

@@ -137,8 +137,6 @@ export default defineConfig({
 | 変数 | 利用箇所 |
 | --- | --- |
 | `WEBHOOK_SECRET` | `@ampless/plugin-webhook` の HMAC 署名 |
-| `AMPLESS_MCP_SERVICE_EMAIL` | HTTP MCP サービスユーザーのメール — `/api/mcp` を有効化するのに必須 |
-| `AMPLESS_MCP_SERVICE_PASSWORD` | HTTP MCP サービスユーザーのパスワード |
 
 env 変数追加 / 変更後は再デプロイをトリガーしてください。
 
@@ -157,7 +155,6 @@ ampless は 1 つの Amplify Hosting デプロイで複数のサイトを配信
 ampless は MCP（Model Context Protocol）サーバーを同梱しているので、Claude Desktop / Cursor / Claude Code など MCP に対応した AI クライアントから投稿の読み書きができます。
 
 - **ローカル / sandbox** — グローバルに 1 度入れる: `npx -y @ampless/mcp-server@alpha` に `amplify_outputs.json` のパスを渡す
-- **本番（HTTP）** — `/admin/mcp-tokens` で Bearer トークンを発行し、MCP クライアントを `https://<your-domain>/api/mcp` に向ける。フルセットアップ: [docs/mcp-http-setup.ja.md](https://github.com/heavymoons/ampless/blob/main/docs/mcp-http-setup.ja.md) ([English](https://github.com/heavymoons/ampless/blob/main/docs/mcp-http-setup.md))
 
 ## ampless の更新
 

package/dist/templates/_shared/README.md

@@ -137,8 +137,6 @@ Set per-environment values in **Amplify Hosting console → Hosting → Environm
 | Variable | Used by |
 | --- | --- |
 | `WEBHOOK_SECRET` | `@ampless/plugin-webhook` HMAC signing |
-| `AMPLESS_MCP_SERVICE_EMAIL` | HTTP MCP service-user email — required to enable `/api/mcp` |
-| `AMPLESS_MCP_SERVICE_PASSWORD` | HTTP MCP service-user password |
 
 Trigger a redeploy after adding/changing env vars.
 
@@ -157,7 +155,6 @@ There's a caching trade-off in multi-site mode; details in [RUNBOOK.md → Multi
 ampless ships an MCP (Model Context Protocol) server so Claude Desktop / Cursor / Claude Code / anything that speaks MCP can read and write your posts.
 
 - **Local / sandbox** — install once globally: `npx -y @ampless/mcp-server@alpha` with the path to your `amplify_outputs.json`.
-- **Production (HTTP)** — issue a Bearer token at `/admin/mcp-tokens` and point your MCP client at `https://<your-domain>/api/mcp`. Full setup: [docs/mcp-http-setup.md](https://github.com/heavymoons/ampless/blob/main/docs/mcp-http-setup.md) ([日本語](https://github.com/heavymoons/ampless/blob/main/docs/mcp-http-setup.ja.md)).
 
 ## Updating ampless
 

package/dist/templates/_shared/amplify/backend.ts

@@ -8,6 +8,7 @@ import { eventDispatcher } from './events/dispatcher/resource.js'
 import { processorTrusted } from './events/processor-trusted/resource.js'
 import { processorUntrusted } from './events/processor-untrusted/resource.js'
 import { apiKeyRenewer } from './functions/api-key-renewer/resource.js'
+import { mcpHandler } from './functions/mcp-handler/resource.js'
 import { userAdmin } from './functions/user-admin/resource.js'
 import { customizeBackend } from './backend.custom.js'
 
@@ -27,6 +28,7 @@ const backend = defineAmplessBackend({
   processorTrusted,
   processorUntrusted,
   apiKeyRenewer,
+  mcpHandler,
   userAdmin,
 })
 

package/dist/templates/_shared/amplify/functions/mcp-handler/handler.ts

@@ -0,0 +1 @@
+export { handler } from '@ampless/backend/functions/mcp-handler'

package/dist/templates/_shared/amplify/functions/mcp-handler/resource.ts

@@ -0,0 +1,11 @@
+import { defineFunction } from '@aws-amplify/backend'
+
+export const mcpHandler = defineFunction({
+  name: 'mcp-handler',
+  entry: './handler.ts',
+  // Co-locate with the data stack so the function has the KvStore
+  // table ARN available without cross-stack references at synth time.
+  resourceGroupName: 'data',
+  memoryMB: 512,
+  timeoutSeconds: 30,
+})

package/dist/templates/_shared/package.json

@@ -26,8 +26,8 @@
     "@ampless/plugin-rss": "^0.2.0-alpha.6",
     "@ampless/plugin-seo": "^0.2.0-alpha.6",
     "@ampless/plugin-webhook": "^0.2.0-alpha.6",
-    "@ampless/admin": "^0.2.0-alpha.18",
-    "@ampless/backend": "^0.2.0-alpha.8",
+    "@ampless/admin": "^0.2.0-alpha.19",
+    "@ampless/backend": "^0.2.0-alpha.9",
     "@ampless/runtime": "^0.2.0-alpha.9",
     "@digital-go-jp/tailwind-theme-plugin": "^0.3.4",
     "ampless": "^0.2.0-alpha.6",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-ampless",
-  "version": "0.2.0-alpha.20",
+  "version": "0.2.0-alpha.21",
   "description": "Create a new ampless project",
   "license": "MIT",
   "type": "module",

package/dist/templates/_shared/app/api/admin/mcp-tokens/route.ts

@@ -1,6 +0,0 @@
-import { admin } from '@/lib/admin'
-import { createMcpTokensRoute } from '@ampless/admin/api'
-
-export const dynamic = 'force-dynamic'
-export const runtime = 'nodejs'
-export const { GET, POST, DELETE } = createMcpTokensRoute(admin)

package/dist/templates/_shared/app/api/mcp/route.ts

@@ -1,9 +0,0 @@
-import { admin } from '@/lib/admin'
-import { createMcpRoute } from '@ampless/admin/api'
-
-// `force-dynamic` keeps CloudFront from caching MCP responses. Each
-// tool call must hit the SSR Lambda — caching would serve stale or
-// cross-token responses.
-export const dynamic = 'force-dynamic'
-export const runtime = 'nodejs'
-export const { POST } = createMcpRoute(admin)