Organizze Mcp

Created By
silviorodrigues8 months ago
Overview

what is Organizze MCP?

Organizze MCP is a Model Context Protocol server designed to interface with the Organizze API, allowing users to manage their financial data effectively.

how to use Organizze MCP?

To use the Organizze MCP server, you need to provide your Organizze credentials and run the server using the command: npx -y organizze-mcp --organizze-username=YOUR_USERNAME --organizze-api-key=YOUR_API_KEY.

key features of Organizze MCP?

  • Access to bank accounts and transactions
  • Management of credit card details and invoices
  • Budget tracking and category management

use cases of Organizze MCP?

  1. Fetching bank account details for financial analysis.
  2. Retrieving transaction history for budgeting purposes.
  3. Managing credit card invoices and payments.

FAQ from Organizze MCP?

  • What is required to use Organizze MCP?

You need an Organizze account with valid credentials and an API key.

  • Can I access multiple bank accounts?

Yes! You can retrieve details for multiple bank accounts using the provided tools.

  • Is there support for budget tracking?

Yes! The MCP server includes tools for managing and retrieving budget information.

Server Config

{
  "mcpServers": {
    "organizze-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "organizze-mcp",
        "--organizze-username=rafaoliveirabispo@gmail.com",
        "--organizze-api-key=1531ccd33e71cae6315a1de5eb7d56e0123efb0a"
      ]
    }
  }
}
Project Info
Created At
8 months ago
Updated At
6 months ago
Author Name
silviorodrigues
Star
-
Language
-
License
-

Recommend Servers

View All
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.

12 minutes ago