Skip to main content
Glama
627,060 tools. Updated 2026-10-01 12:31

"Logseq - A Knowledge Management and Note-Taking App" matching MCP tools:

  • Use this when the user asks to add, change or clear their own note on an exercise, built-in or custom ("note on my bench: seat 4, pause on the chest"). The note is a short gym-floor cue the Reps app shows on the exercise and during a workout; a custom exercise's step-by-step how-to goes in `notes` on `update_custom_exercise` instead. Get the slug and the current `note` from `get_exercise_library`. `note` replaces the whole note (to add to it, send the old text plus the new); an empty `note` clears it. Applied at once, with no confirmation step, so use it when the user asks for the note or has just agreed to it, and say in one sentence what the note now says.
    Connector
    Destructive
    OAuth
  • Mint a PROJECT-scoped management token (`er_mcp_`) for MCP and REST; it cannot authenticate relay traffic. Use it after create_project to configure a fresh project, or for any project you already own. Attenuated by design: the scopes must be a subset of THIS management token's own grant (`read` is always included), expiry is mandatory (1–90 days, default 30, never "never"), and the minted management token (being project-scoped) can never mint management tokens itself. `spend` is human-granted only: no management token, of any scope, can mint one carrying it. Mint a spend-scoped token from the project's panel instead. Requires an ACCOUNT-scoped management token and the `config` scope. Returns the plaintext exactly once; only its hash is stored.
    ConnectorNo auth
  • Materializes a free Cabgo workspace for the operator and queues an Android build of their branded app. No payment, no card, no checkout — the workspace is free to create and operate. Call ONLY when the user explicitly wants to create / launch / spin up / set up a new app for their business — verbs like 'create', 'launch', 'build me', 'set up an app for'. Do NOT call this for setup / installation / connector questions (use cabgo_install_instructions). Ask the user 2 things: (1) what type of business — taxi / food delivery / gas distribution? (2) what brand name for their app? Optionally city + brand color. **The connected OAuth user becomes the owner automatically** — no email or name is needed in the body. **A single user can own multiple tenants** — calling this again creates a NEW workspace rather than erroring. Branding tweaks happen via other Cabgo tools after creation. Any plan / billing / subscription management is done by the operator on https://www.cabgo.app — never through this tool.
    ConnectorNo auth
  • List the key's workspace's proposed actions (the approval queue). Read-only. Optionally filter by ``status`` (proposed / approved / executing / done / failed / dismissed). Returns ``{id, action_type, status, source, title, source_doc_id, external_id}`` per proposal. NOTE: MCP can read and PROPOSE actions but deliberately cannot approve or execute them — a human approves every action in the app UI.
    ConnectorNo auth
  • List the projects on your account (archived included), each with `id`, `slug`, `name`, `apiBaseUrl` and `archived`, plus `accountEmail` — the account this token authenticates as. Requires an ACCOUNT-scoped management token (one minted with no project) and the `read` scope. A PROJECT-scoped management token cannot call this: use it on its own project's tools instead.
    ConnectorNo auth
  • Lists on-screen windows of any app with window_id, owning app bundle id + name, title, bounds (global space, top-left, points), display_id (the CGDirectDisplayID — matches list_displays, so you can look up which display a window is on), layer (0 = normal app window; non-zero = panel/overlay/menu), and is_focused. Window TITLES require Screen Recording permission — without it this returns an explicit permission_required error rather than a title-less result. Optional app_bundle_id filter — note that Electron-style apps often own their windows from a HELPER process with a different bundle id, so a filter can come back empty while the app is plainly on screen. on_screen_only DEFAULTS TO TRUE and excludes minimized, hidden and other-Space windows; pass false to see them. include_overlays DEFAULTS TO FALSE and excludes non-zero-layer windows (Notification Center, widgets, menus); pass true to include them — use layer in the result to tell them apart from normal windows. include_minimized_state DEFAULTS TO FALSE (an extra Accessibility lookup per app, so it's opt-in); pass true to add `minimized` (true/false) to each window AND, when on_screen_only is true (the default), also bring back the minimized windows that filter would otherwise drop — WITHOUT Accessibility granted `minimized` is `null` (unknown) and no minimized windows are added back, never a guessed false, so you can find/capture a minimized window without bringing it forward first. When the result is empty this tool returns a `note` explaining which filter emptied it and what to pass instead — read it instead of concluding the app has no windows. window_id is stable within the session for later targeting.
    ConnectorOAuth

Matching MCP Servers

Matching MCP Connectors

  • The live Haveno XMR/USD order book, both sides, priced against centralized spot. Each price level carries its cumulative depth, offer count, payment methods and a reversible flag. `asks` are makers selling XMR, so taking one means buying; `bids` are makers buying, so taking one means selling. Offers are advertisements with differing payment methods rather than a matched book, so nothing executes on its own and the best bid can sit at or above the best ask.
    ConnectorNo auth
  • Stop injecting a stored secret into one app. The app restarts without it, so call this only when the app no longer needs that variable. The stored value stays in the account vault and any other app using it keeps working; deleting the stored value itself is a dashboard action. Do not report the secret as deleted, report it as removed from this app.
    Connector
    Destructive
    No auth
  • Rename an app's slug (its unique per-tenant identifier / folder prefix). Fails if the new slug is already in use. Note: this renames the APP; it does not move member resources, which are matched by their own slugs.
    ConnectorOAuth
  • Write a coach summary / opinion on one completed activity — the athlete sees it in the activity card in Blocks (labelled “Coach read”). Pass the activity `id` from list_activities. By default it REPLACES the coach note; pass append:true to add. Optionally set a post-session `grade` (A..E) for how the session was EXECUTED vs the plan — it shows as a colored badge on the ride card (A=nailed it, B=solid/minor deviations, C=partial/mixed, D=undercooked/well off target, E=missed/abandoned; a smart bail on a genuine bad day is NOT automatically E — grade the execution + judgement, not the athlete). Ground the read in the real numbers (duration, TSS, IF, NP, HR, zones, intervals from list_activities/get_activity), the athlete profile and the knowledge base — concrete and useful, not generic praise. Markdown renders in the app — keep it airy: a few short `##` sub-headings with normal-weight prose (or short `-` bullets), `**bold**` only on a key number or the verdict, and don't restate the ride name or the grade (they're shown separately above the note and as a badge). Separate from the athlete's own note.
    Connector
    Destructive
    OAuth
  • Search your personal knowledge base. Finds relevant notes using semantic search. Searches across ALL your vaults by default; pass vault_id to limit to one. Omit query to list the most recently updated notes instead. Pass similar_to with a note path, instead of query, to find notes like that one. Use when the user asks about their notes, vault, knowledge, or memory.
    ConnectorOAuth
  • Full-text search the ACC Docs repository of a project for drawings, specs, submittals, and other files via the APS Data Management search endpoint. When to use: The user wants to find a document by keyword (filename, sheet number, or metadata match). E.g. 'find the latest A-201 sheet' or 'search for mechanical specs on Tower project'. When NOT to use: Do not use to upload a file (use acc_upload_file); do not use to fetch issues/RFIs. If you already have a document URN, fetch it directly with an agent that has Data Management folder/item access. APS scopes: data:read account:read. No write scope required. Rate limits: APS Data Management ~50 req/min per app per endpoint; pageable (limit 200 upstream). Avoid tight query loops. Errors: 401 (APS token expired — refresh); 403 (user lacks Docs view permission on the project); 404 (project_id not found — verify 'b.' prefix and hub membership); 422 (invalid filter syntax — simplify query text); 429 (rate limit — back off 60s); 5xx (ACC upstream — retry with jitter). Side effects: None. Read-only and idempotent.
    ConnectorNo auth
  • Full-text search the ACC Docs module on a project for drawings, specs, submittals, and other documents matching a query string. Calls the APS Data Management v1 search endpoint scoped to a project. When to use: an agent needs to locate a spec section, a sheet, or a submittal by keyword (e.g. 'fireproofing', 'A-101', 'RFI 23'). When NOT to use: you already have the document URN/lineage — fetch it directly. You want the file contents — this returns metadata; download separately via Data Management. APS scopes: data:read account:read Rate limits: APS default ~50 req/min per app per endpoint; Model Derivative translation jobs ~60 req/min; OSS uploads size-limited per file to 100MB for direct upload, larger via resumable. Errors: 401 APS token expired/invalid — refresh; 403 scope or resource permission denied (Docs module access required); 404 project_id not found — check the ID (note: this endpoint re-prepends 'b.' so pass the UUID form); 429 rate limited — backoff and retry; 5xx APS upstream outage — retry with jitter. Side effects: READ-ONLY. Inserts a row into D1 usage_log. Idempotent.
    ConnectorNo auth
  • The VM's SERIAL CONSOLE: kernel messages and early-boot/cloud-init output. ⛔ THIS IS NOT YOUR APPLICATION'S LOGS. For a deployed app - a crash loop, a 500, a failed DB connection - use get_container_logs, which returns what the containers actually printed. Reach for this one only for boot-level questions: the machine never came up, the disk did not mount, cloud-init failed before the app existed. Note that on this platform the console goes silent once a machine is past early boot, so an empty result here says nothing about a running VM.
    ConnectorNo auth
  • Change a service you own. Only the fields you pass change. Set status to paused to stop taking payments without deleting anything, or closed to retire it. Replacing prices retires the old options and mints new ones; charges already settled keep the price they were sold at.
    ConnectorNo auth
  • Recall your own memories — hybrid (semantic + exact-term), with provenance attached. Every result carries where it came from (`source_query_ids`, replayable), when it was believed (`valid_from`/`valid_to`) and what knowledge time it is about (`as_of`), plus a `recall` block stating which model and which filters produced the answer. Args: query: what you are looking for, in words. kinds: restrict to some of 'query' 'factor_def' 'watchlist' 'finding' 'note'. as_of: knowledge-time bound — pass a backtest's as_of and nothing recorded later can come back. Use this for anything point-in-time. key: the stable name, when you know it (e.g. a factor name). agent_id: narrow to one of your agents. include_superseded: also return old versions (the audit view). Default is current only.
    ConnectorNo auth
  • Read the append-only cross-surface edge ledger without taking a standing. Pass record_id for one declaration, subject_kind plus subject_public_id for machine-attested transport and its declarations, or neither to list recent records. Every field is explicitly tagged machine_attested, testimony, or unknown. This never infers authorship, labor, personhood, reputation, or settlement.
    ConnectorNo auth
  • Refresh data from all of the business's installed integrations now (pulls the latest transactions/records from each connected app). Returns per-app sync results. Note: this pulls from every connected provider in turn and can take a while — on a business with several live bank feeds it may run longer than a typical tool-call timeout; if it times out the sync still continues server-side, so re-read (e.g. list_expenses) shortly after rather than immediately retrying.
    ConnectorOAuth
  • Publish an app YOU own. Takes effect immediately, with no review queue and nobody to ask. Two ways to publish: "public" gives it a tile in the autario app store under Community apps, next to AI Visibility 360 and the World Bank and FRED data surfaces, plus a public URL, "unlisted" gives it only the URL, so anyone you send the link to can open it and nobody else finds it. Returns public_url. Viewers read data through autario.js with their own role: a stranger sees public catalog data only, a team member the owner invited to the app (Account > Team) sees the datasets the app declares. Note that a published app is deliberately NOT search-engine indexed; only autario can put a community app into the sitemap. Use it when the user says the app is ready to share. unpublish_app reverses it.
    ConnectorNo auth
  • Connect this workspace's WhatsApp by providing credentials the user generated in THEIR OWN Meta app (the 'bring your own credentials' alternative to the browser signup popup). Use this to connect a workspace's WhatsApp number entirely in chat: ask the user for the three values from their Meta app's WhatsApp API setup — a permanent access_token, the phone_number_id, and the waba_id (WhatsApp Business Account id) — then call this tool with them. DripRaven validates the token against Meta and, on success, sends real broadcasts from that number. Returns { connected, status, phone_number, verified_name }. Fails with VALIDATION_ERROR if the credentials are wrong. Note: for credentials from your own Meta app, delivery/read stats won't update (they require webhook wiring in your own app); outbound sending works.
    ConnectorOAuth
  • Read Fieldproxy's app-building reference. topic='index' lists every guide and widget. Guides: 'app' (app JSON), 'view' (screen JSON), 'actions' (onclick/onchange/navigation), 'schema' and 'tenant-schema' (data tables), 'theming', 'design', 'dashboards', and more. Any widget type name (e.g. 'table', 'form', 'map_widget') returns that widget's full syntax. Read the relevant doc before writing any app or screen JSON — it is more reliable than memory. Web and mobile apps have DIFFERENT references: pass platform 'mobile' for a mobile app (no `type: "web"`).
    ConnectorAPI key