Atlas

MindVest Atlas

You focus on the strategy. Atlas automates it and handles the execution, in your own broker account, by the rules you set.

Most assistants can talk about the market. Few can look at it, and fewer can act on what they find. Atlas is a hosted MCP server that gives an assistant both halves:

Scan the market  →  Decide with your plan  →  Preview  →  You approve  →  Atlas carries it out

This repository holds what you need to connect: the install pages, the tool list, and the plugin. The server itself is hosted for you at https://atlasmcp.finmanagerai.com/mcp. There is nothing to run.

Install

1. Have an Atlas account

Create one, or sign in, at https://www.mind-vest.io/atlas.

2. Add Atlas to your assistant

The address is all most assistants need. Give them https://atlasmcp.finmanagerai.com/mcp and they open Atlas's sign-in page in your browser the first time. You sign in there; the assistant never sees your password.

• ChatGPT and Codex: install the plugin. See The plugin.

• Claude (web and desktop): Settings → Connectors → Add custom connector, and paste the address.

• Claude Code:

  claude mcp add --transport http atlas https://atlasmcp.finmanagerai.com/mcp
  

  then /mcp inside a session to sign in. Or install the plugin, which adds the skills too:

  /plugin marketplace add finmanagerai/atlas-mcp-server
  /plugin install mindvest-atlas@mindvest
  

• Anything that reads the MCP registry: io.github.finmanagerai/atlas-mcp-server

For an assistant that cannot open a sign-in page, use your access key instead. It is on your dashboard under Profile → API / CLI / MCP Key. Treat it like a password.

{
  "mcpServers": {
    "atlas": {
      "type": "streamable-http",
      "url": "https://atlasmcp.finmanagerai.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_ATLAS_ACCESS_KEY" }
    }
  }
}

3. Try it

Ask: "Show me a quote for SPY." If a price comes back, you are connected.

A page for each assistant

Claude Desktop · Claude Code · Cursor · Windsurf · OpenAI Codex CLI · OpenClaw · Docker (for assistants that only speak stdio)

The plugin

A plugin is the server plus skills: short guides that tell an assistant what is possible with Atlas and show it templates to start from. Ten come with it:

To have your own assistant wake itself on a timer, see docs/agent-run-loop.md.

The ChatGPT and Codex archive is a smaller edition. It reads the market, your account and plays, and builds and runs workflows and alerts. It does not place an order, set up a waiting trade, or post or take a play by hand: that skill is left out of it, and the server does not offer it those tools. That is done in Atlas itself and from the other apps. Its script workflow skill leaves out the trades a script can place.

Each skill says what is possible, not what you must do. The lists of fields inside them are written from the live server, so they match it.

Download the archives from the latest release:

Or build them yourself: python3 scripts/build-plugin.py writes dist/.

No key is inside any of them. They carry the server's address, and you sign in when the plugin first connects.

What you can ask for

Scan the options market

What are the biggest options trades in the market today?

Which has more call buying right now: NVDA, AMD or AVGO?

Analyze a stock

Give me the picture on AAPL: the trend, the options flow, and when it next reports.

Where is the largest gamma level on SPY today, and is price above or below it?

Build a workflow

Every weekday at 9:30, send me a brief on SPY and the five names on my list.

When SPY breaks above 600, buy the nearest call with $500, take half off at
+30%, and show me the trade before it goes in.

Set an alert

Tell me when a call sweep over $250k prints on NVDA.

Post or take a play

Post it to my group: SPY 780 calls at 2.10, out at +50% and +100%, stop 30%.

Place and manage a trade

Preview buying 10 NVDA at 900 with a stop at 880 and a target at 940.

Move the stop on my SPY trade to breakeven.

More, with the tools each one uses: docs/examples.md.

Tools

Every tool the server has, with what each one can do at its worst (only reads, adds something, changes something, or can send an order): docs/tools.md. That page is written from the live server.

In short:

• Market data: options flow, quotes, price history, charts, options chains, dealer exposure, earnings, financials, filings, web search.
• Workflows: a plan in plain words that Atlas runs on a schedule, when an alert goes off, or when you press Run.
• Alerts: a price level, a large options trade, a volume spike, a technical cross, a move in dealer exposure, or your own trades.
• Plays: one trade idea, written down in full, shared with a board or a group.
• Orders and trades: preview, place, cancel, and manage a trade that is open, in your own connected broker account.
• Strategies and memory: your written playbooks, and what Atlas remembers about how you work.

Safety

• An order is placed or changed only when you say so, or by a workflow you switched on. Every tool states whether it only reads, changes something, or can send an order, and your assistant asks you first.
• Preview first. An order can be staged and shown to you before anything reaches your broker, and a workflow can hold each run for your approval.
• Your broker sign-in stays with your broker. You connect an account on the Atlas dashboard; an assistant never sees those details.
• Atlas runs on its own servers. It does not read files on your computer or run commands there.
• Atlas does not give investment advice. Trading involves risk, including the loss of what you put in.

More: docs/security.md · Privacy · Terms

This repository holds only what is needed to find and install Atlas. The server, the broker connections and the data pipelines are not open source.