Piggy MCP Server

Created By
anonoza year ago
Overview

what is Piggy MCP Server?

Piggy MCP Server is a backend service that allows interaction with the Money Manager database, enabling users to manage and analyze their financial data.

how to use Piggy MCP Server?

To use the Piggy MCP Server, export an mmbak file from the Money Manager app and place it in the server directory as piggy.sqlite. Then, install the necessary dependencies and start the server to interact with the database.

key features of Piggy MCP Server?

  • Facilitates communication with the Money Manager database.
  • Allows users to analyze their financial data through various queries.
  • Supports integration with MCP clients like Claude.

use cases of Piggy MCP Server?

  1. Analyzing spending habits over time.
  2. Forecasting future expenditures based on historical data.
  3. Generating insights about financial trends and preferences.

FAQ from Piggy MCP Server?

  • What is required to set up the Piggy MCP Server?

You need to export an mmbak file from the Money Manager app and install the server dependencies.

  • Can I use this server with any MCP client?

Yes, it can be used with any MCP client, including Claude.

  • Is there a graphical interface for this server?

No, it is primarily a backend service that requires interaction through MCP clients.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
anonoz
Star
0
Language
Python
License
-
Category
finance
Tags

Recommend Servers

View All
Payai X402 Tools

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago