Fluent

io.becomefluentPublished by becomefluent.ioOfficial publisherv1.0.0Updated Oct 27, 2026

Your work meetings, notes, people, tasks and follow-ups from Fluent, in your AI assistant.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Fluent brings your work meetings, notes, people, tasks and follow-ups into an AI assistant through a hosted remote endpoint.

What you can do
  • Access Fluent work meetings and notes from the assistant
  • Look up people and their related context
  • Review tasks and follow-ups recorded in Fluent
  • Use that workspace context while drafting or planning in the assistant
When to use it
Useful if your team keeps meeting notes, people records and follow-ups in Fluent and you want the assistant to work with that context instead of copying it over by hand.
Requirements
A remote MCP endpoint at mcp.becomefluent.io reached over streamable HTTP, with OAuth sign-in to a Fluent account. No packages, environment variables or headers are declared.
Before you install
The connection is authorized through OAuth and exposes work meeting notes, people and task data to the assistant, so review the scopes granted and whether that content may leave your organization. No tool list is published, so what the assistant can read or change is not documented here.

Installation

In SourceWeft

  1. Open Fluent 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/io.becomefluent%2Ffluent/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": {
    "fluent": {
      "type": "http",
      "url": "https://mcp.becomefluent.io/"
    }
  }
}

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

1
  1. v1.0.0LatestOct 16, 2026

Score

67% 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
  • 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.