GPT-6.1 Sol is in ChatGPT Work and Codex, not chat: attach Sume's MCP

OpenAI put GPT-6.1 Sol in ChatGPT Work and Codex rather than regular chat. Which of those surfaces can take Sume's hosted MCP server.

5 min readSume
All posts

GPT-6.1 Sol, released September 29 at DevDay, is available in ChatGPT Work and in Codex, but not in the main ChatGPT chat, according to the launch coverage read today. Its API id is gpt-6.1-sol, priced at $2 per million input tokens, $0.10 cached and $10 output, one fifth of GPT-6 Astra's rate (read 2026-10-04).

That placement decides where you can attach Sume's hosted MCP server at https://mcp.sume.com/mcp: you do it in the product, not in the model.

Which surface takes an MCP server?

Sume's MCP overview names Codex among the clients and shows a Codex setup. Codex is therefore the straightforward path for Sol today. For ChatGPT Work, check the connectors screen in your own workspace; Sume's docs do not describe a ChatGPT Work setup, so treat that as untested.

Where GPT-6.1 Sol runs, from OpenAI's launch material, read 2026-10-04.
SurfaceGPT-6.1 SolSume's hosted MCP
ChatGPT main chatNot availablen/a
ChatGPT WorkAvailableCheck your workspace's connectors
CodexAvailableDocumented in Sume's quickstart
API (gpt-6.1-sol)AvailableYour code connects to the server

What should I test first?

Run the read-only discovery tools before anything that spends.

  • mcp_health to confirm the connection and auth source.
  • tools_list to see what this credential can reach.
  • account_me to confirm which workspace the agent acts for.
  • Any paid tool with dry_run=true and a max_spend_usd, plus an idempotency_key.

Does a cheaper model change the bill?

Only the planning line. Sume's generation spend is charged separately, so keep a cap on every paid call whichever model is driving.

Sources

Related posts

More in Integrations

All Integrations posts

Written by Sume