SharedBrief

選択したAI作業からクライアント提案書、プロジェクト更新、意思決定ブリーフを作成し、アクセス制御付きの安定したリンクを公開し、OAuth認証済みのリモートMCPサーバーを通じて読者のアクティビティを確認します。

ホスト型 MCP サーバー

npx add-mcp 'https://www.sharedbrief.com/mcp'

Claude Code、Codex、Cursor などにインストールできます

ドキュメント

Your AI. Your brief.

Start with a private draft, review it, then choose who can read the published link.

SharedBrief server URL

https://www.sharedbrief.com/mcp

Sign in to your SharedBrief account during connection and review the access requested. Connection instructions do not establish directory approval or verified compatibility. Platform availability and account permissions vary.

Set up yourself or let your agent help.

Follow the numbered steps below, or copy the instructions into an agent with browser or computer control. For Cursor, an agent with file access can help. You’ll still sign in and approve access yourself.

ChatGPT

Screenshots show the setup menus and fields. Click an image to open it full size. Your app may look different depending on your plan and version.

  1. Open ChatGPT in your browser and sign in to the account or workspace you want to use.
  2. Open Plugins from the sidebar and check your Personal or installed plugins for an existing SharedBrief connection. If your account uses the Apps interface, open Settings → Apps or Workspace settings → Apps instead.
  3. In Plugins, choose Add → Add custom MCP server. In the Apps interface, enable developer mode under Advanced settings where permitted, then choose Create. If these controls are unavailable, check the official guide below or ask your workspace admin for access.ChatGPT Plugins page with Add open and Add custom MCP server in the menu In the Plugins interface, click Add, then Add custom MCP server. Click to enlarge.
  4. Enter SharedBrief in the Name field. The icon and description are optional.
  5. Enter https://www.sharedbrief.com/mcp as the MCP server URL and choose OAuth authentication.ChatGPT custom MCP form with SharedBrief as the name, the SharedBrief server URL, and OAuth authentication Enter SharedBrief and the server URL, and leave Authentication set to OAuth. Review the notice before choosing Create as a plugin. Click to enlarge.
  6. Review the custom-server notice. If you agree, check I understand and want to continue and choose Create as a plugin. In the Apps interface, follow Scan Tools and Create. Complete SharedBrief sign-in and review and approve the requested access when prompted.
  7. Open a new chat and select SharedBrief from the plugins, apps or tools menu.
  8. Ask ChatGPT to list your SharedBrief briefs to check the connection. An empty list is fine if you have no briefs yet.

These screenshots show the ChatGPT web Plugins interface. Some accounts use the Apps interface instead. Creating and publishing briefs needs write actions; your plan and workspace controls must permit them. Settings and availability vary. See OpenAI’s developer mode guide for current settings and eligibility.

Claude

Screenshots show the setup menus and fields. Click an image to open it full size. Your app may look different depending on your plan and version.

  1. Open Claude and sign in to the account you want to use.
  2. Open Customize → Connectors and check whether SharedBrief is already connected.
  3. Choose + Add → Add custom connector. For Team or Enterprise accounts, an organization owner may need to add it first in Organization settings → Connectors.Claude Customize page with Connectors selected and the Add custom connector menu open Select Connectors, click + Add, then choose Add custom connector. Click to enlarge.
  4. Name the connector SharedBrief and enter https://www.sharedbrief.com/mcp as the remote MCP server URL. Choose Continue.Claude custom connector form filled with SharedBrief and https://www.sharedbrief.com/mcp, with Continue at the bottom Enter SharedBrief as the name and paste the server URL, then click Continue. Click to enlarge.
  5. Review the detected authentication settings. Choose Sign in now and follow the recommended OAuth setup offered by Claude.
  6. Finish adding the connector. Choose Connect if prompted, sign in to SharedBrief, and review and approve the requested access.
  7. Open a conversation and enable SharedBrief from the + menu → Connectors.
  8. Ask Claude to list your SharedBrief briefs to check the connection. An empty list is fine if you have no briefs yet.

Custom connector access depends on your Claude plan and organization permissions. See Claude’s custom connector guide for current settings and eligibility.

Cursor

  1. Open Cursor. Decide whether SharedBrief should be available in every project or just the current project.
  2. For every project, open ~/.cursor/mcp.json. For this project only, open.cursor/mcp.json. Create the file if it does not exist.
  3. Check for an existing SharedBrief entry. Otherwise, merge the configuration below into mcpServers, preserving all other servers and settings.
  4. Save the file and open Cursor’s MCP settings. Check that SharedBrief appears; refresh or restart Cursor if it does not.
  5. Choose the sign-in or Connect option for SharedBrief. Complete OAuth sign-in in your browser, review the requested access, and approve it.
  6. Return to Cursor and enable SharedBrief if prompted.
  7. Ask Cursor’s agent to list your SharedBrief briefs to check the connection. An empty list is fine if you have no briefs yet.
{
  "mcpServers": {
    "SharedBrief": {
      "url": "https://www.sharedbrief.com/mcp"
    }
  }
}

An agent with file access can help edit the configuration. These steps do not require a marketplace installation. See Cursor’s MCP documentation for current settings and eligibility.

Muse

  1. Open Muse and sign in to the account you want to use.
  2. Open Settings → Connectors and look for SharedBrief.
  3. If SharedBrief is listed, select it and choose the connection option.
  4. Follow the sign-in prompts, sign in to SharedBrief, and review and approve the requested permissions.
  5. Return to Muse and ask it to list your SharedBrief briefs to check the connection.
  6. If SharedBrief is not listed, stop here and use another AI connection from this guide. We do not have a verified manual connection path for Muse.

SharedBrief’s current Muse listing availability has not been confirmed. Muse’s official guidance says approved connectors are discoverable in Settings → Connectors. See Muse’s connector guidance for current settings and eligibility.

Sharing and reader activity

Anyone-with-the-link access is unlisted and opens without an account. Verified-reader and specific-email access require readers to sign in with a verified email. A link never overrides its access settings.

Published updates keep the same brief URL. Owners can see visits, approximate time on page, broad device type and approximate location where available. Verified readers appear by email address; anonymous visitors remain anonymous. Estimated views deduplicate repeat views from the same browser on the same day and do not represent a count of people.

Unpublishing removes access to the hosted page. People may retain content they already copied. Deleting removes the brief and its view records.

What you can create

Briefs support headings, paragraphs, lists, tables, quotes and links. Images, file imports and interactive HTML are not currently available. You can publish up to 10 briefs; each document can contain up to 100 KB of text.

Create your brief in a connected AI app, then preview and share it in your briefs. If a connection fails, check that you can sign in to SharedBrief, then reconnect from your AI platform.

SharedBrief is operated by SnuffleLabs LLC. Need help? Email support@sharedbrief.com.