Platform

MCP, both directions

Give Claude, ChatGPT, Cursor or Claude Code your work context — and bring your other tools into Lodestar.

Lodestar as an MCP server

Connect the assistant you already use and it gains your mail, calendar, files, contacts, projects and commitments as tools it can read and act on. Sign-in is a normal OAuth consent screen; you grant scopes and can revoke them. It stops being a chatbot you brief and becomes one that already knows.

Bring your own MCP servers

Connect remote MCP servers of your own — from a catalog of well-known ones or by URL — and their tools appear in Lodestar chat and are available to your agents and widgets. Airtable, Notion, your internal service: whatever speaks MCP.

You decide what may run unattended

Every external tool call runs inside the same confirmation envelope as Lodestar's own. Ask every time is the default; mark a server read-only and its tools run without interrupting you. Connections are https-only and cannot be pointed at private or internal addresses.

When a connection breaks, it says so

A disabled or expired server does not silently disappear from the model's options. Lodestar names it, explains why, and offers to reconnect in the conversation — rather than answering as though the capability never existed.

  • ·Works with Claude, ChatGPT, Cursor and Claude Code
  • ·OAuth consent with revocable scopes
  • ·Connect your own remote MCP servers
  • ·Per-server confirmation: ask every time, or auto-run read-only