Skip to main content

Getting Started

Simple & Fast Setup

Get your team using secure MCP tools with our streamlined installation process

STEP 1

Download and Configure

Download Configuration File

Download the docker-compose.yml file:

curl -o docker-compose.yml https://files.peta.io/package/docker-compose.yml

Or create it manually with the configuration provided in our GitHub repository.

Configure Environment Variables (Optional)

For production or custom configurations, create a .env file in the same directory:

# Console Port (default: 3000)
CONSOLE_PORT=3000

# Security Keys (REQUIRED for production!)
CONSOLE_JWT_SECRET=your-strong-random-secret-key
NEXTAUTH_SECRET=your-nextauth-random-secret-key
NEXTAUTH_URL=http://localhost:3000

# MCP Gateway Connection (default: http://localhost:3002)
MCP_GATEWAY_URL=http://localhost:3002
PROXY_ADMIN_URL=http://localhost:3002/admin
⚠️

Production Warning

For production deployments, you must create a .env file and change CONSOLE_JWT_SECRET and NEXTAUTH_SECRET to strong, random values. For local testing, you can skip this step and use default values.

Prerequisites Checklist

Before you begin, ensure you have:

Docker and Docker Compose installed

Ports 3000 and 5439 available

Peta Core running with MCP Gateway accessible (default: http://localhost:3002)

📝

Important

This setup requires Peta Core to be running separately. Peta Console connects to Core's MCP Gateway for server management.

STEP 2

Launch and Verify

Start Services

Launch all services with a single command:

docker compose up -d

This will:

  • Start PostgreSQL database for Console (port 5439)
  • Launch Peta Console web interface (port 3000)
  • Configure health checks and automatic restarts

Verify Deployment

Check service status:

docker compose ps

All services should show status as "Up" or "healthy".

Access Console

Open your browser and navigate to:

http://localhost:3000

You should see the Peta Console login page.

What's Included

This Docker Compose setup includes:

Peta Console

Web management interface

PostgreSQL 16

Database for Console data

Health Checks

Automatic service monitoring

Persistent Storage

Data volumes for PostgreSQL

STEP 3

Install Peta Desk (Optional)

For team members: Self-configure MCP clients, add tools instantly, no manual config files or IT tickets needed

TROUBLESHOOTING

Common Issues

Use docker run -p 3001:3000 and access via localhost:3001

NEXT STEPS

What's Next?

Explore Architecture

Understand how Peta's security model protects your infrastructure

View Architecture →

See Use Cases

Discover how teams across industries deploy Peta MCP

Browse Use Cases →

Get Support

Need help? Join our community or request early access

Get Help →