Skip to main content

Frequently Asked Questions

General​

What is Targetly?​

Targetly is a specialized hosting platform specifically designed for Model Context Protocol (MCP) servers. It allows you to deploy MCP tools with a single command and get instant, production-ready URLs.

Why use Targetly instead of deploying manually?​

Targetly simplifies MCP server deployments with:

  • One-command deployment - No complex configuration
  • Auto-idle shutdown - Optimize resource usage
  • Instant URLs - Get subdomain URLs automatically
  • Simple management - Easy CLI commands for all operations

Is Targetly free?​

Targetly is self-hosted on your own VPS. You pay only for your VPS hosting costs. The Targetly software itself is open source.

What is MCP?​

MCP (Model Context Protocol) is an open standard that allows AI models to securely interact with external tools and data sources. Learn more at modelcontextprotocol.io.

Installation & Setup​

How do I install Targetly CLI?​

Install via Homebrew (macOS/Linux):

brew tap Targetly-Labs/tap
brew install targetly

Or using the install script:

curl -fsSL https://targetly.dev/install.sh | sh

See the Installation Guide for more options.

What are the system requirements?​

  • OS: macOS, Linux, or Windows (WSL2)
  • Node.js: 16.6+ (for some MCP servers)
  • Docker: For local testing and builds

Do I need to install Docker?​

Docker is recommended for local testing, but not strictly required for deployments. Targetly handles Docker builds on the server side.

Deployment​

What files are required for deployment?​

You need:

  • A Dockerfile in your project root
  • Your application code and dependencies
  • Any configuration files referenced in your Dockerfile

What happens when I run 'tly deploy'?​

When you deploy:

  1. Your project is bundled (zipped)
  2. Bundle is uploaded to Targetly
  3. Targetly builds a Docker image from your Dockerfile
  4. A container is started with automatic port mapping
  5. You receive a unique subdomain URL

What port should my MCP server use?​

Your MCP server must listen on port 8080. This is the standard port for all Targetly deployments.

Can I deploy the same project multiple times?​

Yes! Each tly deploy creates a new deployment with a unique ID and URL. You can have multiple deployments of the same project running simultaneously.

Sleep/Wake​

Why do deployments go to sleep?​

Deployments automatically sleep after 15 minutes of inactivity to optimize VPS resource usage. This allows you to run many deployments efficiently on a single server.

Does sleeping delete my deployment?​

No! Sleep only stops the Docker container. All your code, configuration, and deployment URL are preserved.

How do I wake a sleeping deployment?​

Use the tly start command:

tly start <deployment-id>

The deployment wakes in 2-5 seconds without requiring a rebuild.

Can I disable auto-sleep?​

Auto-sleep is currently enabled for all deployments. Future versions will support disabling it on a per-deployment basis.

Troubleshooting​

My deployment fails to build​

Common causes:

  • Invalid Dockerfile syntax
  • Missing dependencies in requirements.txt or package.json
  • Incompatible base image

Solution: Check logs with tly logs <deployment-id> for specific errors.

Container starts but URL is not accessible​

Possible issues:

  • Server not listening on 0.0.0.0 (using localhost instead)
  • Server not listening on port 8080
  • Server taking too long to start

Solutions:

  • Check logs for startup errors
  • Verify port 8080 is exposed and used
  • Ensure server binds to 0.0.0.0:8080

'Command not found: tly' after installation​

The binary may not be in your PATH.

Solutions:

  • Restart your terminal
  • Check if /usr/local/bin is in your PATH
  • Re-install using the appropriate method

MCP Specific​

What transport mode should I use?​

Always use SSE (Server-Sent Events) transport for Targetly deployments. STDIO transport is only for local command-line servers.

How do I connect my AI client to a deployed MCP server?​

Configure your AI client (e.g., Claude Desktop) with the SSE endpoint:

{
  "mcpServers": {
    "my-server": {
      "url": "https://your-deployment.prod.targetly.io/messages",
      "transport": "sse"
    }
  }
}

Can I deploy non-MCP applications?​

Technically yes, since Targetly just runs Docker containers. However, it's optimized for MCP servers (port 8080, SSE transport, etc.).

Support​

Where can I get help?​

How do I report a bug?​

Open an issue on our GitHub repository with:

  • Description of the problem
  • Steps to reproduce
  • Expected vs. actual behavior
  • Relevant logs from tly logs