// A little paperwork. Once.

Connect your assistant.

Connect Milton. Ask “did you get that memo?”

Milton connects through MCP, a standard that lets assistants use tools. You need a client that supports remote MCP, OAuth sign-in, and tools that read and save. Your plan or workspace administrator may restrict these features.

First, sign in to Milton with Google or GitHub. Use the same account when your assistant asks you to authorize the connection. Early access is free; no credit card is required.

Set up with your assistant

// Start with a prompt

Open in Claude Open in ChatGPT

Opens a new tab with the setup prompt. You may need to sign in. If the prompt doesn’t appear, copy it below.

Read or copy the prompt
Manual setup instructions →
Milton’s MCP server URL
https://mcp.meetmilton.com/mcp

Claude

  1. Open Claude’s connector settings and add a custom connector named Milton.
  2. Use the server URL above, then complete the sign-in and authorization prompts.
  3. Enable Milton in the conversation’s connectors menu before asking Claude to use it.

Claude supports custom connectors across its plans; Free accounts have a one-custom-connector limit. Workspaces may need an owner or administrator to add it. Claude’s current connector guide ↗

Claude Duet

Guide only: not yet verified with Milton.

Anthropic says Duet uses the connectors in your Claude account. The expected setup path is to connect Milton in Claude first, then use that connection in Duet.

  1. Follow the Claude setup steps above.
  2. Open Duet with the same Claude account and make Milton available to the conversation.
  3. Ask “Did you get that memo?” Confirm it reads the current TPS Report before relying on the connection.

Duet is a research preview with limited access. Check Anthropic’s Duet guide ↗for current availability. If Milton is unavailable in Duet, use the connected Claude client while compatibility is being checked.

ChatGPT

  1. Open Plugins and look for the option to add a custom MCP server.
  2. Add Milton with the server URL above and complete the sign-in prompts.
  3. Make Milton available in your conversation before asking ChatGPT to read or save preferences.

Custom MCP access depends on your plan and workspace settings. You need both read and write tools; a search-only connection won’t save preferences. If the option is missing, check the official connection guide ↗ before signing up for a different plan.

Grok Bot

Guide only: not yet verified with Milton.

Grok Bot can add an MCP server by URL through chat. Try this in your Bot:

Add Milton as a remote MCP server at https://mcp.meetmilton.com/mcp. Use OAuth browser sign-in, then list its tools. Do not save or change preferences during setup.
  1. Complete the browser sign-in using your Milton account.
  2. Start a new message after connecting, then ask “Did you get that memo?”
  3. Confirm the Bot reads your current TPS Report. Once connected, use the save and read examples below.

Grok Bot connections are shared across the Bots on your account. Workspace policies may restrict connectors. See the Grok Bot connection guide ↗.

Muse

Guide only: not yet verified with Milton.

Ask Muse in chat to create a Custom Connector:

Create a Custom Connector named Milton for the remote MCP server at https://mcp.meetmilton.com/mcp. It uses Streamable HTTP and OAuth browser sign-in. List its tools after connecting. Do not save or change preferences during setup.
  1. Follow Muse’s connection flow and complete browser sign-in using your Milton account.
  2. Ask “Did you get that memo?” and confirm Muse reads the current TPS Report.
  3. Once the connection works, use the save and read examples below.

Meta documents chat-created Custom Connectors; Milton’s OAuth flow still needs a complete Muse test. Milton does not provide an API key, so this connection must use browser sign-in. If Muse cannot complete it, report the connection issue instead of treating setup as finished. Meta’s connector guide ↗

Claude Code

In your terminal, add Milton for your user account:

claude mcp add --transport http --scope user milton https://mcp.meetmilton.com/mcp

Then open Claude Code, run /mcp, select Milton, and complete authentication. User scope makes the connection available across projects. Claude Code’s MCP guide ↗

Codex

With the Codex CLI installed, run:

codex mcp add milton --url https://mcp.meetmilton.com/mcp
codex mcp login milton

Complete the browser authorization. If adding Milton already signed you in, you don’t need to sign in again. Start a new Codex session if the tools aren’t available in the current one. Codex’s MCP guide ↗

Cursor

Add a remote MCP server named Milton in Cursor’s MCP configuration, using the server URL above. Cursor supports HTTP connections and OAuth sign-in. Complete authentication and enable the tools for your agent. Cursor’s setup and configuration guide ↗

Put your first preference on file.

Your account starts empty. Try an instruction you actually want to keep. For example:

“Milton, go ahead and file this: lead with the answer. Keep replies concise unless I ask for detail.”

Or ask your assistant to help draft your preferences, then approve the complete draft before saving. Open Milton to check the report.

In your next conversation, ask:

“Did you get that memo?”

“Did you get the memo?” also works.

Use this to ask your assistant to fetch your latest TPS Report, even if it read an earlier copy. It should confirm only after a successful read. This requests a read, not a save.

Connecting Milton doesn’t automatically load the report into every chat. Ask for a read when you start work. All connected assistants can read the whole report, so keep private project context in its own tools.

Not connecting?

Check the server URL, sign in with the same Milton account, and confirm your assistant allows the connector in this conversation. Workspace policies may require administrator approval. For help, email peter@meetmilton.com.

See current access and planned pricing →