Managed MCP Servers

Your MCP server hosted, metered and kept current, or listed on MCPize.

What it is

An MCP server is only useful while it is running, reachable and current. GTDataWorks takes that part: your Model Context Protocol server is packaged as a Docker container, deployed on Modal or Google Cloud Run, and kept updated, so your team or your customers connect to an endpoint instead of running infrastructure.

Every call is metered against an API key and recorded as a usage receipt. The server can stay private to you, reachable only with keys you issue, or it can be listed for sale on MCPize, the marketplace for paid Model Context Protocol servers. Either way you get logging, key management and a monthly usage report.

What you get

  • Hosted endpointYour server running in a Docker container on Modal or Google Cloud Run, reachable from Claude, ChatGPT, Cursor or any other MCP client that holds a key you issued.
  • Key managementAPI keys issued, rotated and revoked per consumer, with every call metered against the key that made it.
  • Monthly usage reportCalls per key and errors for the month, built from the usage receipts, so you can see who used the server and how much.
  • Update cadenceDependency and runtime updates applied on an agreed schedule and tested before they reach the live endpoint.

How the work runs

  1. Package

    Your server, or one GTDataWorks builds under Custom LLM Connectors & MCP Tools, is containerized with Docker, pinned to known dependency versions and given a health check.

  2. Metering and keys

    Each consumer gets an API key. Calls are counted per key and written as usage receipts, so there is a record for every request the server handled.

  3. Private endpoint or MCPize listing

    The container goes live on Modal or Google Cloud Run. A private server is reachable only with the keys you issue. A server for sale is listed on MCPize as part of launch.

  4. Updates on a cadence

    Runtime and dependency updates are applied on the schedule agreed at setup. Anything that could change behaviour is tested against the server before it goes live.

  5. Monthly usage report

    Each month you receive calls per key and errors, derived from the receipts. The receipts themselves are yours.

Pricing

Setup

$1,000–$2,000

Packaging, hosting, key management and launch.

Hosting

$50–$200/month per server

Updates, logging, monthly usage report. A per-call model is available for high-volume servers.

Prices are in USD and are starting points. Setup is a one-time fee and hosting is billed monthly per server; the final quote follows a scoping call.

Where it fits

A good fit when

  • You have an MCP server, or need one built, and nobody who wants to run it.
  • You want to sell a tool to Claude, ChatGPT or Cursor users without building key management and metering yourself.
  • Your customers need a stable endpoint and a usage record they can check.

Not a fit when

  • The server does not exist yet and hosting is the smaller question. Start with Custom LLM Connectors & MCP Tools; hosting can follow.
  • You need a model or an agent deployed, not an MCP server. See Deployment, MLOps & Hosting.
  • You need the server on AWS or Azure. Managed hosting here runs on Modal or Google Cloud Run.

Questions

Who owns the server code?

You do. GTDataWorks operates it; the source, the container definition and the configuration remain yours.

What happens if GTDataWorks stops hosting?

The container image, deployment configuration and key list are handed over, with notes on running them on Modal, Google Cloud Run or a Docker host of your own. The setup is a standard container, so it runs without GTDataWorks.

How does listing on MCPize work?

MCPize is a marketplace where creators list and sell Model Context Protocol servers. If your server is for sale, the listing is part of launch and the hosted endpoint behind it is kept current. The studio's own listings are described on the MCPize page.

Can I see what the server is doing between reports?

Yes. Every call is logged and metered per key. The monthly report summarizes those receipts, and the receipts are yours.

Hand over the hosting

Tell GTDataWorks what the server does, who will call it and whether it is for sale. Launch takes one to two weeks.