"Tools or methods for organizing Org files and Org-roam nodes based on content" matching MCP tools:

• write_app_filesA

  Control PlaneA

  Create, edit, append to, move, or delete the text files of an app you write for the user, stored on Control Plane per org and app NAME across calls and sessions; NAME is also the image and workload name. In a shell on the user's machine with a working cpln CLI (never a chat app's sandbox), prefer a directory there and `cpln image build --remote --dir PATH --name NAME:TAG --org ORG`, so the user keeps the code. Whole files in files, a large file in parts through appends, exact-text replacements in edits, removals in deletePaths, moves and renames (uploaded files too) in moves, at most 200 files per call. Files the user has (images, fonts, PDFs, data) never go inline: create_app_files_upload_link takes the ones that stay as they are until the next build, and content the owner changes after launch is uploaded through the app once it runs. Never include credentials or a .env with values. A Dockerfile is optional for common stacks. An app that keeps anything (content its owner changes, records, files, or sign-ins; for example a portfolio, a blog, or a shop): plan_app before the first write. Then deploy_app with the same NAME builds and runs it.

  Connector

  Destructive

  OAuth

• run_testsA

  Cirra AI Salesforce Admin MCP ServerB

  Run Apex tests and native Flow Tests asynchronously and return the job ID used to poll for results. Use tests to run specific classes or methods, or testLevel to run tests org-wide

  ConnectorOAuth

• list_my_toolsA

  OakallowA

  Enumerate the customer-defined tools currently available to the signed-in user in the named org (or their only org if they have one). Returns tool names, descriptions, default permission, and risk level.

  ConnectorOAuth

• browse_oosA

  OTPA

  Browse published Organizational Operating Systems on OTP. Filter by industry, org size, template type, or quality tier. Returns a list of published OOS files with org metadata.

  ConnectorAPI key

• scan_watchA

  PriviB

  Pin the server's current tools as approved and get a real-time event on your private Live 'org' channel the moment they change, a risk appears or the server goes down. Free plan: 3 servers; Pro: 500. Needs the org key.

  ConnectorNo auth

• scan_watchA

  Privi LedgerB

  Pin the server's current tools as approved and get a real-time event on your private Live 'org' channel the moment they change, a risk appears or the server goes down. Free plan: 3 servers; Pro: 500. Needs the org key.

  ConnectorNo auth

• list_m365_people_insightsA

  Local MCPB

  List the people most relevant to you in Microsoft 365 — based on your communication patterns, collaboration history, and org chart. Useful for meeting prep and contact enrichment.

  ConnectorOAuth

• test_mcp_server_connectionA

  Agent LeverageA

  List an org-scoped upstream server's tools and optionally cache the discovered tool names on success (persist=true). Returns { ok, tools } or { ok:false, error } without leaking secrets.

  ConnectorOAuth

• manage_organizationA

  AlmuredA

  Get information about the organization your agent is linked to. WHEN TO USE - You want to know which organization your agent is operating under. - You need to list the members of your linked org (e.g., to decide which member should review a deliverable). WHEN NOT TO USE - To create, update, or delete organizations — those actions require human authentication via the REST API (POST /api/v1/organizations, PATCH /api/v1/organizations/{slug}, etc.). BEHAVIOR - Read-only. Auth required: agent API key. Rate-limited to 60 req/min. - Returns an error if your agent is not linked to any organization (agents.org_id IS NULL). - action='get_my_org': returns org name, slug, tier, owner, and member count. - action='list_members': returns human_id and role for each member. WORKFLOW - Check your org membership before referencing org context in deliverables or communications. - To link your agent to an org, a human admin must call POST /api/v1/organizations/{slug}/agents.

  ConnectorNo auth

• read_fileA

  BorealHostB

  Read the contents of a file from a site's container. Max file size: 512KB. Binary files are rejected — use the site's file manager or SSH for binary files. Requires: API key with read scope. Args: slug: Site identifier path: Relative path to the file Returns: {"path": "wp-config.php", "content": "<?php ...", "size": 1234, "encoding": "utf-8"} Errors: NOT_FOUND: File doesn't exist VALIDATION_ERROR: File is binary or exceeds 512KB

  ConnectorNo auth

• word_createA

  Local MCPB

  Creates a new Word (.docx) document at `path` with the given text content (and an optional title rendered as the heading). The path must be somewhere LMCP can write; Desktop/Documents/Downloads may need a one-time Files-and-Folders grant (System Settings → Privacy & Security → Files and Folders). Returns {created, path}. For a OneDrive or Google Drive path use onedrive_write_file / gdrive_write_file; to append to an existing doc use word_append, to read one word_read.

  Connector

  Destructive

  OAuth

• get_policiesA

  Veto — SQL Safety & Cost OracleA

  Return the custom org policy set currently stored for your Pro key — the same rules analyze_sql enforces on top of the built-ins. Read-only; returns an empty list if none are set. Use set_policies to change them.

  ConnectorNo auth

• file_createA

  TeamSharedC

  Create a new versioned shared file in the caller's org. Shared files default to private. Call ``file_publish`` to generate the public share URL (``/s/{share_token}``). Each ``file_update`` creates a new immutable version row. Pass ``work_id`` to attach it to a task and/or ``project_id`` to attach it to a project (same ``shared_files`` row; project attachments are ``kind=artifact`` only). ``content_format='diagram'`` takes either diagram schema: - ``teamshared.diagram/v1`` — ``body: {format: mermaid, text: "..."}``, rendered as Mermaid. Best for flowcharts, sequences, and ER sketches. - ``teamshared.diagram/v2`` — ``body: {format: scene, layers: [...], nodes: [...], edges: [...]}``, rendered as a layered 3D scene where each layer is a plane (infra / software / data by convention), each node sits on one layer, and edges may cross layers. ``kind`` (default ``system``), ``view`` (``layers``), ``mode`` (``authored``) and ``body.camera`` are optional. Every node needs ``id`` and ``layer``; ``shape`` is ``box`` | ``cylinder`` | ``sphere`` | ``cone``; edges are ``{from, to, label?, kind?}`` with ``kind`` one of ``sync`` | ``async`` | ``data`` | ``depends``. Omit ``x``/``z`` to get an automatic grid on the plane. Caps: 8 layers, 300 nodes, 600 edges, 256 KiB. Unknown keys are rejected.

  ConnectorNo auth

• resolve_client_profileA

  ALM X++ MCP ServerA

  WHEN: at the START of any release-note / upgrade-impact conversation -- call this BEFORE list_release_note_inputs to check whether a Client Profile already exists for the CURRENT caller's Azure DevOps org/project (auto-detected from DEVOPS_ORG_URL/DEVOPS_PROJECT MCP headers -- you don't pass anything). If found, it gives you the client's currentVersionTag, targetVersionTag, customModelIds (their own extensions AND any attached ISV/vendor models) and the latest diff snapshot in one call -- use those directly as v1/v2/customModelIds for prepare_release_note_context, no further discovery needed. If not found, fall back to list_release_note_inputs and/or save_client_profile.

  ConnectorNo auth

• list_specsA

  RoutebaseA

  List all API specifications in the active project. Set scope to 'org' to list the published APIs across every project in the organization instead — each entry carries the projectId and specId to pass to set_context. Use this to browse specs or find a spec id; for one spec by id use get_spec. Requires project context for scope 'project'.

  ConnectorAPI key

• connect_mercuryA

  AgenticBooksA

  Connects the org to Mercury from a read-only, scoped API token the user created in their Mercury settings (Mercury uses a token, not OAuth — there is no redirect). The token is validated against Mercury's accounts endpoint and stored ONLY if it works; an invalid token stores nothing and returns an error. This grants READ access only — balances and transactions — it cannot move money. The token is sensitive: it is vault-encrypted at rest and never returned, logged, or echoed. Optionally include the per-account webhook signing secret (from where the webhook was created in Mercury) to enable live transaction events.

  ConnectorOAuth

• calculate_actuarial_pvA

  Fair Value MCP ServerA

  Actuarial present value engine. Discount expected cash flows with mortality, survival, and risk adjustment for insurance and benefit obligations, generalising IFRS 17 (fulfilment cash flows), IAS 19 (employee benefits), IFRS 2 (share-based payments), and IAS 37 (provisions). Use this for regulated IFRS/HKFRS obligations only; it does NOT do generic project or scenario probability weighting (use calculate_expected_value). Methods: ifrs17_gmm: cash_flows, discount_rate, risk_adjustment; ifrs17_paa: premiums, claims_cash, acquisition_cash_flows, coverage_periods; ifrs17_vfa: cash_flows, discount_rate, underlying_items_return, risk_adjustment; ias19_puc: projected_benefits, discount_rate, attribution_years; ias37_provision: outcomes, probabilities, discount_rate, periods. Supply exactly one method with its declared inputs (no defaults). An unknown method, a missing input, or an extra field returns an error envelope (code INVALID_ARGUMENT) instead of raising.

  ConnectorNo auth

• team_profileA

  Cito APIA

  Team/org card: identity, roster, recent matches, and form/trends/radar when available. When to use: - Team page / "who is on this roster?" - Builder team screen sample Prefer over: separate roster + matches + detail via call_api. Do not use when: UFC fighters → player_profile; unknown name → resolve_entity first. Dota may return partial roster (API gap). Prefer slug for lol/cod; teamId for cs2. Parallel-safe: yes. Upstream cost: 2–4. Example: { "game": "lol", "slug": "t1", "recentLimit": 10 }

  ConnectorOAuth

• findagent_edit_departmentA

  FindAgentA

  Edit the settings of YOUR OWN department — its reporting instructions, name, and description. `report_instructions` is the department's behavioural lever: it is prepended to EVERY member's (and the orchestrator's) prompt on every run, and to every prompt-template tool result on a direct `<alias>__<tool>` call, so it is how you tell the whole team how to work and how to report, without editing any member agent. Pass the department slug plus only the fields you want to change; pass an empty string to CLEAR report_instructions or description. This does NOT change the department's composition — members, topology, orchestration and flow hints are edited in the department builder on the web. It is also how you UNDO a deletion: an archived department is put back with status:"draft" (on its own, then edit it in a second call). Works on a PERSONAL department you own, and on an ORG department when you are that organization's owner or admin — an org department is reached by its slug, and an ordinary org member cannot edit one. Call findagent_list_my_agents to see the personal departments you own.

  ConnectorOAuth

• admin_toggle_discoverableA

  Coordinalo — Service Business OperationsB

  Toggle the LIFECYCLE flags isPublic and servicialoPublished. ⚠️ This tool does NOT grant public discovery consent — discovery in the Servicialo registry requires Organization.discoveryConsent=true, which can ONLY be set by the human owner via PATCH /api/organizations/:slug/servicialo from the web panel (a deliberate, authenticated consent action). Without consent, the cron registry-sync and resolver-heartbeat skip the org, so calling this tool with discoverable=true on a non-consented org flips local flags but does not publish anywhere. Requires X-Org-Api-Key header.

  ConnectorNo auth

• public_booking_createA

  Coordinalo — Service Business OperationsB

  Create a public booking request. Does NOT require an API key, but DOES require: (1) requester identity — fullName plus at least email or phone, (2) submission context — channel and whether an agent assisted, (3) authorization.humanIntentConfirmed must be true. The booking is created as pending_confirmation — use public_booking_confirm with the returned confirmationToken to confirm. A bookingToken is also returned for future lifecycle management (cancel, reschedule). Rate-limited per IP+org. All requests are audited with semantic decision codes. Use public_service_list → public_availability_get_slots → public_booking_create → public_booking_confirm as the complete public booking flow.

  ConnectorNo auth