PocketSmith (read-only)

com.pocketsmithPublished by pocketsmith.comOfficial publisherv0.1.0Updated Oct 31, 2026

Read-only: transactions, budgets, forecasts and insights from the PocketSmith personal finance tool.

The publisher's own server: PocketSmith

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Read-only MCP access to PocketSmith personal finance data, letting an assistant review transactions, budgets, forecasts and insights.

What you can do
  • Read transactions from the user's PocketSmith account
  • Review budgets and spending against them
  • Look at forecasts and financial insights
  • All access is read-only, so nothing in the account is changed
When to use it
Useful when you want an assistant to answer questions about your personal finances, spending patterns, budgets or forecasts held in PocketSmith, without giving it the ability to edit that data.
Requirements
A remote MCP endpoint at mcp-readonly.pocketsmith.com over streamable HTTP. OAuth authentication is required, so a PocketSmith account and a browser-based sign-in flow are needed. No environment variables or headers are declared.
Before you install
The assistant can read your personal financial records, including transactions, budgets and forecasts, once you authorize it. Access is granted through OAuth to your PocketSmith account; review the scopes shown at sign-in and revoke access if no longer needed. The server is described as read-only, so it should not modify data.

Installation

In SourceWeft

  1. Open PocketSmith (read-only) 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.pocketsmith%2Fmcp-readonly/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": {
    "pocketsmith-read-only": {
      "type": "http",
      "url": "https://mcp-readonly.pocketsmith.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. v0.1.0LatestOct 31, 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 Pocketsmith integrations