tillpad-mcp
Related Servers
Alternatives to tillpad-mcp
- AlicenseBqualityCmaintenanceEnables agents and apps to verify end-user identity through company API keys, human login links with multi-channel notifications, OIDC client registration, and budget-aware billing.131MIT
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to persistently store and retrieve decisions, patterns, and knowledge across sessions, with workspace organization and semantic search so context survives restarts and compaction.6 npmMIT
- AlicenseAqualityDmaintenanceProvides persistent key-value storage with full-text search, tags, and namespaces for AI agents to maintain context across sessions.743 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to automatically capture durable knowledge and retrieve only relevant, token-bounded context from a secure local-first long-term memory, with support for progressive disclosure, snapshots, health diagnostics, and background tasks.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables Claude and other AI agents to persistently store and retrieve decisions, patterns, and knowledge across sessions, surviving context limits, restarts, and compaction. It supports self-hosted Redis/Valkey or managed cloud deployment with workspace organization and automatic semantic retrieval.6 npmMIT
- FlicenseNot gradedqualityDmaintenanceProvides AI agents with persistent, searchable memory that survives across conversations using semantic search, temporal versioning, and smart organization. Enables long-term context retention and cross-session continuity for AI assistants.14-
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to share a local, searchable context store with summary-first reads, so a new agent can resume a long-running task at a flat token cost without re-reading prior history.1-
TDQS
Scored across 17 tools
Each tool targets a distinct operation within its area—billing, keys, KVP, files/RAG, support—and the descriptions clarify boundaries. usage_get and budget_get both report quota state but with different focuses, and inspect_storage aggregates rather than duplicating the CRUD tools. Overall, misselection risk is low.
Names mix verb-first styles (usage_get, file_upload, inspect_storage) with noun-first styles (keys_create, kvp_put, run_finish) and compound nouns like billing_machine_pay. There is no consistent verb_noun convention, though prefixes like kvp_ and files_ provide some structure.
17 tools is at the high end for a single MCP server and spans several unrelated domains: billing, key management, key-value storage, RAG files, and support. For a multi-purpose platform API the count is defensible, but it is heavier than a focused, well-scoped server should be.
KVP storage has full CRUD and RAG covers upload, listing, and semantic search, but file deletion is missing and key management only supports creation, not listing or revocation. Billing covers usage and budgets but not detailed subscription state or payment history. These gaps are workable but notable for a platform toolkit.