buddybase

com.protoductaiPublished by protoductai.comOfficial publisherv1.0.0Updated Oct 29, 2026

Keep personal records like expenses, vocabulary and health logs in your own buddybase.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote MCP server that lets an assistant keep personal records such as expenses, vocabulary and health logs in your own buddybase.

What you can do
  • Record and keep personal entries such as expenses, vocabulary and health logs in your own buddybase.
  • The registry description names no individual tools, so the exact set of operations is not documented here.
  • Access is through a hosted remote endpoint rather than a local package.
When to use it
Useful when you want an assistant to capture and maintain everyday personal records — spending, language learning, health tracking — in a single personal store you control, instead of scattered notes.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local runtime or package is needed. Sign-in is required via OAuth, so you need a buddybase account. Network access to the hosted endpoint is required.
Before you install
The server stores personal records, including expense and health information, in your buddybase account, so consider how sensitive that data is before connecting. OAuth grants the assistant access to that account; review the scopes requested. The available tools are not listed, so confirm what it can read, change or delete before use.

Installation

In SourceWeft

  1. Open buddybase 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.protoductai%2Fbuddybase/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": {
    "buddybase": {
      "type": "http",
      "url": "https://mcp.buddybase.protoductai.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.0.0LatestOct 29, 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.

Other Protoductai integrations