SayBriefly

com.saybrieflyPublished by saybriefly.comOfficial publisherv1.0.2Updated Oct 24, 2026

Know what was agreed with every client: meetings, decisions, to-dos and briefs from SayBriefly.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Remote MCP server that lets an assistant pull client meeting notes, decisions, to-dos and briefs from SayBriefly.

What you can do
  • Retrieve client records from SayBriefly: meetings, decisions, to-dos and briefs.
  • Surface what was agreed with each client so an assistant can answer questions about past commitments.
  • No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when you track client work in SayBriefly and want an assistant to recall what was agreed, decided or assigned in past meetings without copying notes by hand.
Requirements
A remote MCP endpoint at mcp.saybriefly.com over streamable HTTP. OAuth authentication is required, with a bearer personal key sent in the Authorization header; the key is created in SayBriefly under Settings, Integrations, Connect your AI. A SayBriefly account is needed.
Before you install
The connection requires a personal API key (Authorization header) that grants access to your SayBriefly client data; keep it private and revoke it if exposed. Client meeting notes and decisions are sent to the assistant and its model provider. Writing or changing data is not documented, so assume read access only until verified.

Installation

In SourceWeft

  1. Open SayBriefly in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.saybriefly%2Fsaybriefly/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "saybriefly": {
      "type": "http",
      "url": "https://mcp.saybriefly.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v1.0.2LatestOct 2, 2026
  2. v1.0.1Sep 29, 2026
  3. v1.0.0Sep 27, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.