Access Methods

Remote MCP Deployment

Deploy a 6MM MCP endpoint in user-managed or institution-managed infrastructure.

View as Markdown

Planned — not yet launched AI Hub is a planned feature. Capabilities, endpoints, commands and client configurations on this page describe the proposed design and are not currently available. Final availability and setup instructions will be announced at launch.

Remote MCP is for users or institutions that want a long-running MCP endpoint under their own control.

Unlike Hosted MCP, Remote MCP is not operated by 6MM for the user. 6MM provides code, images, templates, and documentation; the user controls hosting and credentials.

Architecture

AI client
  -> user-managed MCP HTTP endpoint
  -> 6MM REST / WebSocket API

Deployment targets

  • Docker or Docker Compose.
  • VPS with a reverse proxy.
  • Railway.
  • Render.
  • Fly.io.
  • AWS ECS or Lambda.
  • Internal Kubernetes.

Required files

  • Dockerfile.
  • docker-compose.yml.
  • .env.template.
  • HTTP transport mode.
  • /mcp endpoint.
  • /health endpoint.
  • Reverse proxy and TLS notes.

Credential model

Credentials should be stored in the user-managed environment, not in the AI client prompt. For institution-managed deployments, restrict access to approved clients and networks.

Start with public market data. Add account-read only after authentication, key scoping, logs, and access controls are available. Trading should remain disabled until controlled trading requirements are met.