Goal
Prepare a hosted AssemblyMCP service pilot that exposes the existing National Assembly MCP capabilities behind an API-key based service boundary.
Context
AssemblyMCP appears mature enough to consider service hosting. The strategic goal is to try a hosted MCP service model, starting with API-key access and operational hygiene before broader productization.
Scope
- Define hosted service boundary for AssemblyMCP.
- Decide API-key auth model and rate-limit assumptions.
- Identify deploy target and runtime requirements.
- List secret/API-key handling rules.
- Define minimum health, logging, and usage tracking needs.
- Produce a small pilot plan before implementation.
Acceptance Criteria
- Hosting architecture note exists.
- API-key access model is specified.
- Required env/secrets are listed without exposing secret values.
- Pilot deployment checklist is ready.
- Implementation tasks are split into follow-up issues.
Out of Scope
- Immediate public launch.
- Billing.
- Multi-tenant account management beyond basic API keys.
Goal
Prepare a hosted AssemblyMCP service pilot that exposes the existing National Assembly MCP capabilities behind an API-key based service boundary.
Context
AssemblyMCP appears mature enough to consider service hosting. The strategic goal is to try a hosted MCP service model, starting with API-key access and operational hygiene before broader productization.
Scope
Acceptance Criteria
Out of Scope