---
title: "Deploy Tcpcore demo"
description: "Runtime governance for every agent API call"
category: "Other"
url: https://railway.com/deploy/tcpcore-demo
---

# Deploy Tcpcore demo

Runtime governance for every agent API call

**[Deploy Tcpcore demo on Railway](https://railway.com/template/tcpcore-demo)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/tcpcore-demo/manifest.json

- **Creator:** TCPCore
- **Category:** Other
- **Total deploys:** 1

## Template content

### tpcore-demo

- **Source:** https://github.com/TCPCore/tpcore-demo
- **Public domain:** Yes

## Documentation

# Deploy and Host Tcpcore-demo on Railway

[TCPcore Demo is a live, self-contained governed MCP surface. It runs the TCPcore governance kernel against four mock integrations with no credentials, database, or external services. A low-risk call executes immediately, a medium-risk write queues for human approval, and an agent-forbidden delete is refused and hidden from the agent's tool list.]



## About Hosting Tcpcore-demo
[Hosting TCPcore Demo means running a single container that starts two processes: a mock API server on 127.0.0.1:4001 and the governance kernel via tcpctl serve on the public port. There is no database, no Redis, no queue, and no credential to configure. The kernel loads four demo adapters pointing at the in-container mock, compiles them into a minimal MCP tool list, and exposes a JSON-RPC endpoint at /api/mcp]

## Common Use Cases

- [Evaluate the governance model before committing]
- [Demonstrate agent governance to stakeholders]
- [Test MCP client integration]

## Dependencies for Tcpcore-demo Hosting

- [Runtime: None beyond the container. It ships Node.js 22, @tcpcore1/cli, the mock server, and the four demo adapters.]
- [External services and credentials: None. No database, no Redis, no queue, no object storage, and every demo adapter uses auth: none against the in-container mock.]

### Implementation Details 

[The container runs a single entrypoint that starts both processes:

sh
node /app/mock-server.js &
tcpctl serve /app/adapters/*.yaml --port "${PORT:-8080}"
The four demo adapters are:

Adapter	Risk tiers demonstrated
demo	low read, medium approval, high agent_forbidden
demo-crm	low read, medium approval, high agent_forbidden
demo-billing	low read, medium refund approval
demo-content	low read with content_risk: high (prompt-injection scanning)
Probe the running instance:

bash
curl https:///api/mcp/tools        # the minimal tool surface
curl https:///api/integrations     # the four loaded adapters
curl https:///api/audit-log        # NIST AU-3 audit rows
curl https:///api/approvals        # the human approval queue]

## Why Deploy Tcpcore-demo on Railway?


Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Tcpcore-demo on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.


## Similar templates

- [Rocky Linux](https://railway.com/deploy/rocky-linux) — Hosted Rocky Linux 9 workspace with SSH and persistent storage. 🚀
- [Foundry Virtual Tabletop](https://railway.com/deploy/X5tR6G) — A Self-Hosted & Modern Roleplaying Platform
- [Letta Code Remote](https://railway.com/deploy/letta-code-remote) — Run a Letta Code agent 24/7. No inbound ports, just deploy.

Open this page in a browser: https://railway.com/deploy/tcpcore-demo