AgentStack

Hosting MCP servers

Hosted MCP listings run behind the AgentStack gateway, which authenticates each buyer’s entitlement and meters every call for usage billing. You choose how the server runs.

Option 1 — Self-hosted

You run the MCP server yourself (any cloud, any region). In the dashboard you register the upstream URL and an optional verify-header. The gateway authenticates, meters, and proxies each call to your endpoint — your code never runs on AgentStack.

Dashboard → Manage listing → Hosting → Self-hosted
  Upstream URL:   https://your-mcp.example.com/v1
  Verify header:  X-AgentStack-Secret: <your secret>

Option 2 — Managed by AgentStack

Don’t want to run infrastructure? AgentStack runs your container on Google Cloud Run with scale-to-zero. You provide a container image and configure scaling; we provision an isolated, least-privilege service and point the gateway at it.

  • Fully configurable — container image, port, region, min/max instances, CPU (0.25–8 vCPU), memory, and request concurrency.
  • Environment variables — including secrets, injected into your runtime.
  • Scale-to-zero — min instances 0 means you pay nothing while idle. Raise it for warm starts.

Billing — cost passthrough + 10%

Managed hosting bills you the actual Cloud Run compute cost AgentStack incurs for your service, plus a 10% platform margin, charged monthly to your card on file. The dashboard shows a live estimate of the current month. A card on file is required before provisioning.

Monthly charge = Cloud Run compute cost × 1.10

Continuous deployment

Each managed deployment has a deploy token. Add one step to your CI after you build and push your image — it redeploys your Cloud Run service with the new image, no login required:

curl -X POST https://api.agentstack.voostack.com/api/hosted/deploy \
  -H 'content-type: application/json' \
  -d {"token":"$AGENTSTACK_DEPLOY_TOKEN","image":"gcr.io/you/mcp:$GIT_SHA"}

Find and rotate the token under Manage listing → Hosting. Keep it secret (treat it like a password).

How buyers connect

Either way, buyers point their agent client at the gateway with their license:

https://mcp.agentstack.voostack.com/mcp/<slug>

Every call is authenticated, metered, and (for usage-priced plans) reported to Stripe Billing Meters.

Frequently asked questions

What are the two hosting options for MCP servers?

Self-hosted (you run the server anywhere, AgentStack proxies + meters to it) and Managed (AgentStack runs your container on Cloud Run with scale-to-zero, and bills you the GCP compute cost plus a 10% margin).

How much does managed hosting cost?

You pay the actual Google Cloud Run compute cost for your service plus a 10% platform margin. With scale-to-zero (min instances 0) you pay nothing while idle. You can raise min instances for warm starts at extra cost.

Do I need a card on file for managed hosting?

Yes. Managed hosting bills you for compute, so a card on file is required before AgentStack will provision your container.

Can I set environment variables and scaling?

Yes — managed hosting is fully configurable: container image, port, region, min/max instances, CPU, memory, request concurrency, and environment variables (including secrets).

Next: Publishing →