xippios-cashctrl-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@xippios-cashctrl-mcplist my open CashCtrl tasks due this week"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
xippios-cashctrl
Typed Python client, MCP server and FastAPI routes for CashCtrl, part of the xippios SDK family. Names and semantics follow the upstream documentation; every response carries release metadata (source, endpoint, retrieved_at, published_at, vintage).
Install
uv add xippios-cashctrl # client only
uv add "xippios-cashctrl[mcp]" # + MCP server
uv add "xippios-cashctrl[http]" # + FastAPI routerSet CASHCTRL_API_KEY in the environment. Nothing is read from files.
Related MCP server: slurm-mcp
30-second example
from xippios.cashctrl import tasks
# result = tasks.<task>(...)
# result.data, result.meta.retrieved_at, result.meta.requestTask functions are listed in the status table below as they are added.
MCP
{
"mcpServers": {
"cashctrl": {
"command": "uvx",
"args": ["--from", "xippios-cashctrl[mcp]", "xippios-cashctrl-mcp"],
"env": { "CASHCTRL_API_KEY": "..." }
}
}
}Tools are read-only and named cashctrl_<verb>_<noun>. Results are capped at
200 rows or 64 KB with a note on how to narrow the query. --http serves streamable
HTTP instead of stdio.
Write tools run in a separate server, xippios-cashctrl-mcp-write; every write
tool previews its change unless called with confirm=true.
Status
Upstream operation | Task function | MCP tool | Status |
(none yet) |
Upstream terms and attribution
Data comes from CashCtrl (https://cashctrl.com) under its own terms of use;
this package adds no rights to it. Documentation snapshot: docs/upstream/.
Licence
Apache-2.0. See LICENSE.
This server cannot be deployed
Maintenance
Related MCP Connectors
Find tools and hosted agents by task, with source documentation and connection requirements.
Read-only search of 2,189 AI agent tools (MCP servers, x402 APIs) with daily automated trust scores.
A read-only verified record of agent-operable GTM tools: search, fetch, compare, track changes.
Ask your accounts-receivable portfolio anything. Read-only, scoped to your account.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceProvides read-only access to OpenClaw and Codex operational data like status, tasks, sessions, logs, and Git changes. Ensures safety via redaction, allowlists, and bounded outputs.MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to query Slurm scheduler state safely through a read-only allowlist, with progressive disclosure to minimize context usage.MIT
- FlicenseNot gradedqualityBmaintenanceProvides read-only database access for AI agents, enabling table listing, schema inspection, and filtered row queries through MCP tools.-
- AlicenseNot gradedqualityDmaintenanceEnables agent clients to perform read-only regulatory retrieval through tools for searching the corpus, retrieving source text, tracing citations, listing authorities, and inspecting recent filings. It is designed to keep regulated actions and workspace changes behind human review gates.Apache 2.0