Local-first personal knowledge base. Cited answers from your vault via vector + graph retrieval.
Loom MCP server exists for a simple reason — assistants are far more useful when they can act on Loom directly instead of describing what you should do. Local-first personal knowledge base. Cited answers from your vault via vector + graph retrieval.
Point it at your notes folder. Loom indexes everything, maps typed relationships between ideas (which notes cite the same sources, which contradict each other, which extend the same argument), and builds a persistent graph that gets smarter as you add more. Your vault, vector index, and graph stay on your machine. Only the specific passages behind an answer go to Claude for synthesis — or skip that and run a local model instead.
Once Loom is connected, these are the calls the assistant has available:
Gotchas — The Gotchas tool exposed by this serverYou will need 2 environment variables: ANTHROPIC_API_KEY, LOOM_VAULT_PATH. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
fastapi on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of payments and commerce servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Loom's toolset — Gotchas — is a fair guide to whether it matches your workflow. It is maintained by KlossKarl; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Gotchas | The Gotchas tool exposed by this server. |
{
"mcpServers": {
"loom": {
"command": "python",
"args": ["C:\\path\\to\\loom\\loom_mcp.py"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| ANTHROPIC_API_KEY | Credential the server authenticates with. | Yes |
| LOOM_VAULT_PATH | Filesystem location the server is allowed to use. | Optional |
Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.
Enables querying and listing Azure resources and costs directly from an MCP client.
Empowers LLMs with Bitcoin Lightning Network payment capabilities via the ZBD API.