Optiverse MCP Server

Optiverse is also an MCP server. Connect it to the AI tools you already use, and they can search your meetings, read analysis and summaries, work on your boards, or hand a whole task to the Optiverse Agent.

This is the opposite direction from connecting MCP servers to OptiAgent: here, another AI tool is the client and Optiverse provides the tools.

Server URL

https://assistant.optiverse.ai/mcp

The server uses Streamable HTTP. You sign in with your Optiverse account (OAuth), or, for agents without a browser, with your personal API key.

Connect an AI Tool

The quickest way is from Optiverse: open Settings → MCP, the Connect your AI page (app.optiverse.ai/settings/mcp-server), and choose your tool. Each tool asks you to sign in to Optiverse and approve access once.

Claude

1. In Connect your AI, click Connect Claude. Claude opens with the Optiverse connector filled in.
2. Click Add, then Connect, and sign in to Optiverse.
3. In a chat, enable the Optiverse connector from the tools menu.

You can also add it manually in Claude under Settings, Connectors, Add custom connector, with the server URL above.

ChatGPT

1. In ChatGPT, open Settings, Apps & Connectors, and enable developer mode under Advanced settings if your plan requires it.
2. Create a connector with the server URL above and OAuth authentication.
3. Sign in to Optiverse when prompted.

See OpenAI's MCP guide for the current steps on your plan.

Cursor

1. In Connect your AI, click Add to Cursor. Cursor opens and offers to install the Optiverse server.
2. Confirm, then click Connect next to Optiverse in Cursor's MCP settings and sign in.

Codex

Run this in a terminal, then sign in when the browser opens:

codex mcp add optiverse --url https://assistant.optiverse.ai/mcp && codex mcp login optiverse

Other MCP Clients

Any client that supports remote MCP servers with OAuth works. Add the server URL; the client discovers the sign-in flow automatically.

Connect a Headless Agent with an API Key

Agents that run without a browser, such as scripts, CI jobs, or servers, can authenticate with your personal API key instead of OAuth. Send it as a bearer token:

Authorization: Bearer optiuser_v1_your_key_here

Cursor (.cursor/mcp.json):

{
  "mcpServers": {
    "optiverse": {
      "url": "https://assistant.optiverse.ai/mcp",
      "headers": { "Authorization": "Bearer ${env:OPTIVERSE_API_KEY}" }
    }
  }
}

Claude Code:

claude mcp add --transport http optiverse https://assistant.optiverse.ai/mcp \
  --header "Authorization: Bearer $OPTIVERSE_API_KEY"

Codex (~/.codex/config.toml):

[mcp_servers.optiverse]
url = "https://assistant.optiverse.ai/mcp"
bearer_token_env_var = "OPTIVERSE_API_KEY"

Available Tools

The server exposes 24 tools. They are the same operations as API v2, with the same limits.

Read tools are marked read-only, so most clients run them without asking. Clients usually ask you to confirm write tools, and update_* and move_tasks are marked as changing existing data. Boards and tasks cannot be deleted over MCP.

Direct Tools or ask_optiverse

• Direct tools are fast, free, and return structured data. Your AI tool decides which ones to call and combines the results itself. Use them for lookups and focused edits: "find last week's meetings with Acme", "add these three tasks to my Launch board".
• ask_optiverse hands the whole request to the Optiverse Agent, which plans its own steps and can also use the integrations you have connected in Optiverse (CRM, Slack, Teams, and others). Use it for multi-step work or anything that needs those integrations. Each call uses one credit and can take a few minutes; clients that support progress notifications show what the agent is doing.

ask_optiverse returns a conversation_id. Pass it back on the next call to continue the same thread. Threads started over MCP can also be continued through the REST API, and the reverse.

If an accepted request fails or its connection to the agent is interrupted, the error includes a recovery conversation_id in its text and _meta, with retryable: false. Work may still be running or may already have changed an external system. Inspect the existing session through the REST API before resending the request. MCP cancellation targets only the individual call; it cannot cancel another call in the same conversation.

get_meeting_summaries preserves earlier summary formats after a template changes, and each result includes its stored summaryType. batch_create_tasks reports status: "partial" and confirmed task IDs if persistence fails partway through; inspect its failure and remainingTaskIndexes instead of replaying the whole batch. See summary formats and batch results.

Limits and Credits

• Read tools: 120 calls per minute. Write tools: 60 per minute. ask_optiverse: 10 per minute.
• Limits are per user and shared with the REST API.
• Direct tools are free. Each ask_optiverse call uses one credit, the same as asking in the app.

See Activity and Revoke Access

In Settings, Connect your AI, each connected client is listed with the date you connected it.

• Click Activity to see the client's recent tool calls, with the status and time of each.
• Click Revoke to disconnect the client immediately. It has to ask you to sign in again before it can reconnect.

Calls made with an API key appear in Settings, API keys, under the key's activity. To disconnect those agents, delete the key.

Security

• Every tool runs as you and sees exactly what you can see in Optiverse, including meetings shared with you through your workspace.
• OAuth access is limited to the MCP server: the token a client receives cannot be used to sign in to the Optiverse app or call other Optiverse services.
• Optiverse logs which tool was called, by which client, and whether it succeeded. It does not store the arguments, such as your search terms or prompts, in the activity log.
• ask_optiverse can act through your connected integrations, for example sending a message or updating a CRM record. Review your AI tool's confirmation prompts before approving.