Pithflow

com.pithflowPublished by pithflow.comOfficial publisherv1.36.0Updated Oct 24, 2026

Read-only access to your own Pithflow meeting notes, transcripts, dictionary and usage.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Read-only access to your own Pithflow meeting notes, transcripts, dictionary and usage through a remote MCP endpoint.

What you can do
Pithflow exposes your own Pithflow content to an AI assistant over a remote, streamable HTTP connection. According to the registry description, it provides read-only access to meeting notes, transcripts, a dictionary and usage information. No individual tools are listed in the supplied material, so the exact operations are not documented here.
When to use it
Useful when you want an assistant to look up or summarize your own Pithflow meeting notes and transcripts, or to consult your dictionary and usage details, without copying them by hand. It is not intended for editing or creating content, since access is described as read-only.
Requirements
A remote endpoint at api.pithflow.com reached over streamable HTTP, plus a Pithflow account and OAuth authentication, which the manifest marks as required. No environment variables, headers or packages are declared.
Before you install
Access is limited to your own Pithflow data, but that data includes meeting notes and transcripts, which may contain confidential business or personal information; granting OAuth access lets the assistant read it. Review what the OAuth consent covers before connecting.

Installation

In SourceWeft

  1. Open Pithflow 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.pithflow%2Fpithflow/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": {
    "pithflow": {
      "type": "http",
      "url": "https://api.pithflow.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

1
  1. v1.36.0LatestSep 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.