Choose a Setup | 6MM Docs

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.

Choose a setup based on two questions:

Which AI client do you want to use?
Do you need public data only, private account access, or trading workflows?

If you are not sure, start with Hosted MCP for public data or Local MCP for private account workflows.

Pick by use case

I only need public market data

Use Hosted MCP. No local install, no user API key, and no private account access.

I want my AI client to read my account

Use Local MCP with read-only credentials. Start in testnet or read-only mode.

My agent can run terminal commands

Use 6MM CLI. This is simple for Codex, Claude Code, Gemini CLI, scripts, and CI tasks.

My team needs a managed endpoint

Use Remote MCP. Deploy the server in infrastructure controlled by your team.

Quick decision table

Goal	Recommended setup	Why
Ask an AI client for public market data	Hosted MCP	No local install and no API key required.
Let Claude Desktop, Cursor, or ChatGPT Desktop call 6MM tools	Local MCP	AI calls tools through a local server controlled by the user.
Let Codex, Claude Code, Gemini CLI, or scripts call 6MM	CLI	Command output can be JSON and easy for agents to parse.
Provide a company-managed MCP endpoint	Remote MCP	The institution controls hosting, credentials, access, and logs.
Standardize repeated analysis or risk workflows	Agentic Skills	Templates define tool usage, guardrails, and output format.

Pick by AI client

AI client	Hosted MCP	Local MCP	CLI	Notes
Claude Desktop	Possible	Recommended	Possible	Use Local MCP when account context is needed.
Claude.ai Web	Recommended when supported	Not applicable	Not applicable	Best for public market data only.
ChatGPT Desktop	Possible	Recommended	Possible	Local MCP is preferred for private account tools.
Cursor	Possible	Recommended	Possible	Local MCP works well with coding workflows.
Codex CLI	Possible	Possible	Recommended	CLI is usually the most direct path.
Claude Code CLI	Possible	Possible	Recommended	CLI or Local MCP depending on workflow.
VS Code / Copilot	Possible	Recommended	Possible	Depends on MCP and terminal support.
Gemini CLI	Possible	Possible	Recommended	CLI is the simplest first setup.
Windsurf	Possible	Recommended	Possible	Local MCP is preferred.

Pick by setup path

Setup	Installation	API key location	Best initial scope	Account and trading scope
Hosted MCP	None	No user API key for public data	Public market data	Not recommended for first release
Local MCP	User installs package	User machine	Public data and account-read	Recommended path for future trading
CLI	User installs package	User machine	Public data and scripts	Useful for preview and automation
Remote MCP	User deploys server	User cloud or institution cloud	Public data or account-read	Possible when the user controls deployment
Skills	Docs or installable templates	Depends on underlying tools	Analysis workflows	Must follow tool permissions

Security rule of thumb

Use the lowest-risk setup that supports the task:

Public market data: Hosted MCP is enough.
Private account data: Local MCP or user-managed Remote MCP.
Trading preview: Local MCP or CLI, preferably testnet first.
Real trading: only after explicit permission, preview, confirmation, limits, and audit logs.

Next step

After choosing a path, open the matching guide and complete one verification prompt before adding sensitive credentials.