coilyco-gaming/eco-app

Watch

Investigate whether /preview should move to root #21

New issue

Closed

opened 2026-06-17 07:29:28 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-06-17 07:29:28 +00:00

Owner

Originally filed by @coilysiren on 2026-05-02T23:10:32Z

Context

Today the HTTP app routes are:

/ - 302 redirect to /preview
/preview, /preview.json, /preview-map, /preview-map.json, /preview/<tool>, /preview/<tool>.json - dev iframe shell + Jinja2 card, JSON twin
/mcp/ - Streamable-HTTP MCP transport
/healthz

See src/eco_mcp_app/http_app.py:124 for the root redirect.

Question

Why is the dev preview namespaced under /preview with / as a redirect, instead of just serving the preview at /?

Current rationalization (from a chat thread):

/preview* is a tree (.json twins, per-tool subroutes), not a single page. Hoisting to root would shadow other top-level routes or force awkward names.
/ is reserved as a future service-info / landing page.
/preview is explicitly dev-only per the module docstring. Real MCP clients hit /mcp/, never /preview. Keeping it under its own prefix signals "browser-poking surface, not the product."

These are not very compelling on their own. Worth checking what other public MCP servers do at the root URL.

Investigation

Survey 5-10 publicly-deployed MCP servers (Streamable-HTTP transport). What do they serve at /? Empty 404? Service-info JSON? A landing page? A redirect?
Check the MCP Apps spec and Streamable-HTTP transport spec for any guidance on root-URL behavior.
Decide: keep the redirect, replace / with service-info JSON (already drafted at service_info in http_app.py:127, just unrouted), or collapse /preview into /.
If we collapse, figure out how to keep the .json twin and per-tool subroutes coherent (/.json is awkward; maybe /tools/<name> instead of /preview/<name>).

Out of scope

Changing the /mcp/ mount path.
Anything about the iframe shell internals.

Migrated from coilyco-flight-deck/eco-mcp-app#5 during the eco repo consolidation (coilysiren/inbox#100).

_Originally filed by @coilysiren on 2026-05-02T23:10:32Z_ ## Context Today the HTTP app routes are: - `/` - 302 redirect to `/preview` - `/preview`, `/preview.json`, `/preview-map`, `/preview-map.json`, `/preview/<tool>`, `/preview/<tool>.json` - dev iframe shell + Jinja2 card, JSON twin - `/mcp/` - Streamable-HTTP MCP transport - `/healthz` See `src/eco_mcp_app/http_app.py:124` for the root redirect. ## Question Why is the dev preview namespaced under `/preview` with `/` as a redirect, instead of just serving the preview at `/`? Current rationalization (from a chat thread): 1. `/preview*` is a tree (`.json` twins, per-tool subroutes), not a single page. Hoisting to root would shadow other top-level routes or force awkward names. 2. `/` is reserved as a future service-info / landing page. 3. `/preview` is explicitly dev-only per the module docstring. Real MCP clients hit `/mcp/`, never `/preview`. Keeping it under its own prefix signals "browser-poking surface, not the product." These are not very compelling on their own. Worth checking what other public MCP servers do at the root URL. ## Investigation - Survey 5-10 publicly-deployed MCP servers (Streamable-HTTP transport). What do they serve at `/`? Empty 404? Service-info JSON? A landing page? A redirect? - Check the MCP Apps spec and Streamable-HTTP transport spec for any guidance on root-URL behavior. - Decide: keep the redirect, replace `/` with service-info JSON (already drafted at `service_info` in `http_app.py:127`, just unrouted), or collapse `/preview` into `/`. - If we collapse, figure out how to keep the `.json` twin and per-tool subroutes coherent (`/.json` is awkward; maybe `/tools/<name>` instead of `/preview/<name>`). ## Out of scope - Changing the `/mcp/` mount path. - Anything about the iframe shell internals. --- _Migrated from coilyco-flight-deck/eco-mcp-app#5 during the eco repo consolidation (coilysiren/inbox#100)._

coilysiren added the

priority

label

2026-06-17 07:29:28 +00:00

coilysiren commented

2026-06-17 08:20:40 +00:00

Author

Owner

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.

coilysiren

2026-06-17 08:20:40 +00:00

closed this issue
added the
burndown-2026-06
label

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

coilyco-gaming/eco-app#21

No description provided.

Rows
Columns