page:recipes:mcp server:asp net core:artifact storage

Host mcp server with ASP.NET Core: stored input and output artifacts

Deploy a mcp server built with ASP.NET Core on Ample using the generated downloads pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, a managed PostgreSQL 16 database is auto-provisioned and injected as DATABASE_URL, a private S3-compatible bucket holds objects with credentials delivered as encrypted environment variables. Verified on ASP.NET Core: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Not separately tested: your export formats, retention policy and entitlement model; treat the mcp server-specific behavior as your application code.

Representative Queries

Resource Requirements

Infrastructure Requirements

Compute

Postgres

S3-compatible object storage

Prerequisites

Workflow Steps

Build and Start

Implement the Pattern on PostgreSQL

Wire Object Storage

Deploy

Verify

Examples

ASP.NET Core Pattern Fixture

Success Checks

App Responds on Its Public URL

Generated-downloads Self-test

Limitations

Cost Estimate

Components