"TOML" matching MCP tools:

• toml-okC

  TOML validity, body discardedC

  TOML validity, body discarded

  ConnectorNo auth

• mime-tomlD

  MIME tomlC

  Public MIME token for toml.

  ConnectorNo auth

• toml-arr-okC

  TOML array-of-tables count, body discardedC

  TOML array-of-tables count, body discarded

  ConnectorNo auth

• toml-table-okC

  TOML table count, body discardedC

  TOML table count, body discarded

  ConnectorNo auth

• cargo-toml-okC

  Cargo.toml package name shape, body discardedC

  Cargo.toml package name shape, body discarded

  ConnectorNo auth

• toml-table-countC

  TOML table count, body discardedC

  TOML table count, body discarded

  ConnectorNo auth

• x402-json-tomlD

  minia2a-mcpD

  JSON Toml: JSON Toml

  ConnectorNo auth

• x402-toml-jsonD

  minia2a-mcpD

  Toml JSON: Toml JSON

  ConnectorNo auth

• assets.listA

  AI Design BlueprintA

  Public — list downloadable doctrine and agent asset artifacts (skill packs, rule packs, MCP setup snippets) the user can drop into their AI coding tool to import the Blueprint as native skill/rule files. Returns a list of assets with name, format (one of: zip / md / markdown / mdc / json / toml / text — the full vocabulary), pack_version, download_url, and platform target (Claude Code, Cursor, Codex, Gemini, Qwen). The response also carries `count` (length of `assets`) for symmetry with principles.list / clusters.list / guides.list. WHEN TO CALL: the user asks how to bring the Blueprint into their coding agent, or wants to install it as a local skill/rule file. WHEN NOT TO CALL: for the live MCP tools themselves — those are already available through this server. For doctrine content, prefer principles.list/get and guides.list/get. BEHAVIOR: read-only, idempotent, no auth required. Asset artefacts are regenerated on every deploy from the canonical doctrine.

  ConnectorNo auth

• assets.listA

  AI Design Blueprint DoctrineA

  Public — list downloadable doctrine and agent asset artifacts (skill packs, rule packs, MCP setup snippets) the user can drop into their AI coding tool to import the Blueprint as native skill/rule files. Returns a list of assets with name, format (one of: zip / md / markdown / mdc / json / toml / text — the full vocabulary), pack_version, download_url, and platform target (Claude Code, Cursor, Codex, Gemini, Qwen). The response also carries `count` (length of `assets`) for symmetry with principles.list / clusters.list / guides.list. WHEN TO CALL: the user asks how to bring the Blueprint into their coding agent, or wants to install it as a local skill/rule file. WHEN NOT TO CALL: for the live MCP tools themselves — those are already available through this server. For doctrine content, prefer principles.list/get and guides.list/get. BEHAVIOR: read-only, idempotent, no auth required. Asset artefacts are regenerated on every deploy from the canonical doctrine.

  ConnectorNo auth

• deploy-repository-toolA

  CoderbudsA

  Trigger a production deploy for one of your team's connected repositories. The repository must have a deploy trigger configured — either a deploy hook URL or a GitHub Actions workflow — in its Coderbuds settings. Identify the repository by name (e.g. "saas") or by full name (e.g. "patchstack/saas"). This ships whatever is currently merged; it is not a dry run. Use GetUndeployedPullRequestsTool first if you want to see what will go out.

  ConnectorOAuth

• file_readA

  local-mcpA

  Reads a plain text file from the local filesystem by its absolute path — the primary, default tool for reading a local text file (use this unless the file is a PDF, Word, Excel, or PowerPoint document, which have their own readers). Reads anywhere on this Mac — home, external disks, cloud drives, /tmp — with one exception: credential and identity locations (keychains, ~/.ssh, ~/.aws, browser logins, another user's home, Time Machine backups) are never read. Supports .txt, .md, .csv, .json, .xml, .log, .yaml, .toml and common code file types; auto-detects UTF-8 with Latin-1/Windows-1252 fallback. For files in OneDrive use onedrive_read_file, in Google Drive gdrive_read_file; for PDFs pdf_read, Word word_read, Excel excel_read.

  ConnectorOAuth

• convertA

  Nanotoll MCPA

  Transform text between JSON, YAML, TOML, and CSV formats. Returns the converted text and input/output character metrics. Note some conversions can be lossy (e.g. JSON to CSV flattens nested structures). Requires a valid API key (Bearer token); billing is per input character — insufficient balance returns HTTP 402. For removing comments use `prune`, for generating llms.txt use `generate`.

  ConnectorNo auth

• assess-change-fit-toolA

  CoderbudsA

  Pre-flight fit check for a change you are about to open as a pull request. Pass the additions, deletions, and changed-file counts of your working diff and Coderbuds answers whether the change fits how this team ships: a verdict with reasons, the team's own merged-PR size norms (median/p75) and merge time by size category, and the current review-queue pressure. Pass `repository` and that queue is scoped to it — human-authored open pull requests on the repo you are working in, not every repo the team owns, because "review one of these first" is only actionable if you are near them. Four verdicts, and only two of them ask anything of you. `fits` — go. `fits_at_edge` — over the standard but inside its tolerance, which is stated for the record and needs no action, because changes this close to the line merge like changes under it. `caution` — meaningfully over; weigh the guidance. `split_required` — effectively unreviewable; split it. Coderbuds applies its own opinionated standard (on by default, teams can opt out): changes well above the standard size get at least a caution regardless of what the team's historical norms would allow — reported as team_norms.target_total_changes. Also pass `review_goals`: the distinct outcomes a reviewer must approve in this change. Describe outcomes, not implementation layers — an API, UI, migration, tests, and docs that deliver one behavior are one review goal. One goal fits. Two prompt a caution to confirm they really must ship atomically. Three or more require a split. This is the scope-coherence standard: a small diff can still be hard to review when it bundles unrelated decisions. If multiple goals truly cannot ship separately, use `scope_rationale` to preserve that context and record the decision after the check. Best results: pass `numstat`, the raw output of `git diff --numstat <base>...`. Coderbuds then works out the split from the file paths itself — tests, documentation, generated files (lockfiles, snapshots, minified bundles) and binary assets are identified and discounted, so the verdict judges the CODE a reviewer actually has to read. 400 lines of blog post and 400 lines of business logic are not the same review, and without the paths there is no way to tell them apart. Failing that, declare the split yourself: test_lines (changed lines living in test files, e.g. from `git diff --shortstat -- tests/`) and moved_lines (code relocated without behavioral change, e.g. an extraction refactor) are subtracted from the verdict, because a raw count punishes test coverage and double-counts refactors. Report these honestly; they are recorded with the check and visible to the team. Do the same for files with test_files and moved_files. A rename sweep, codemod, or file-move refactor touches a lot of files with almost nothing to read in each, and the file count is judged separately from the line count — so without these a mechanical change is called oversized on file count alone. `git diff --shortstat -M` and `git diff --summary` will tell you how many of the changed files were renames. When the verdict is not "fits", say what you did about it with `record-change-fit-decision` — including when you proceed anyway. Overriding is allowed; overriding silently is what leaves the standard unable to learn it is in the wrong place.

  ConnectorOAuth

• frontend_security_audit_ci_pipelineA

  DataNexus MCPA

  Scan GitHub Actions, Vercel, or Netlify CI configs for exposed secrets, missing lockfile enforcement, and unpinned dependencies. Paste your config content — no filesystem access required. config: Raw YAML/TOML content of your CI config. Required. 500 KB max. config_type: github_actions (full check suite), vercel, or netlify (secrets only in Sprint 8). Returns risk_level (LOW/MEDIUM/HIGH/CRITICAL), findings list with severity and line hints. NOTE: ${{ secrets.FOO }} and ${{ env.FOO }} references are NOT flagged — only literal secret values. Read-only. No side effects. Idempotent. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="frontend_security_audit_ci_pipeline", intended_query="{what the user needed}", gap_description="{what was missing or wrong in the result}".

  ConnectorNo auth

• get-open-pull-requests-toolA

  CoderbudsA

  List the team's open pull requests grouped by author, with the signal that shows what is blocking each one: whether it is awaiting a reviewer, has changes requested, is approved and ready to merge, is still a draft, is failing CI checks, or is simply too large for anyone to review. Optionally scope to specific "owner/name" repositories (e.g. patchstack/hub). Use this to nudge people to merge — lead with the `headline`. Human authors include their oldest open PRs with age; bot authors (dependabot etc.) are collapsed into count-only summaries so a dependency backlog cannot drown out the PRs a person should act on. `total_oversized` and the per-PR `oversized` flag mark pull requests past the hard review limits — over 100 files, over 5,000 added or deleted lines, or over 8,000 changed in total. These are the ones a reviewer cannot pick up at all, so they are named in the headline and sorted to the front of their author's list. Report them as blocked on being split, not as blocked on a reviewer. The threshold is deliberately the hard limit rather than the team's line target: an open PR gives no file list, so the test/docs discount `assess-change-fit` applies to a numstat cannot be applied here, and judging against the target would flag changes that check would have passed. `size.category` is `unknown` when the counts were never recorded — that is missing data, not a small pull request; do not describe it as small. Set `include_bot_details` when you are working the dependency queue itself — merging dependabot PRs, chasing failing bumps — and each bot author gains the PR numbers, repositories, titles and URLs you need to act, ordered by what can be closed out first: ready to merge, then failing checks, then oldest. Check `status_freshness` before quoting counts: it flags open PRs whose local status may be stale, and repositories that have not synced pull requests recently — whose PRs may be missing from these counts altogether. Archived (decommissioned) repositories are excluded — this is a review queue, and their PRs are nobody's to review.

  ConnectorOAuth

• get-mcp-adoption-toolA

  CoderbudsA

  Who on the team is actually using the Coderbuds MCP. Every MCP tool call is recorded per member, so this reports adoption over a recent window (default 30 days): total invocations, per-member usage with last-used time and favourite tool, per-tool call counts, and — the nudge list — login members who have never connected the MCP at all. The denominator is who could plausibly connect one today — a login member (only they can mint API tokens) who is still shipping code. Tracked contributors cannot connect, deactivated or long-inactive members have left, and someone with several linked identities counts once. Use when asked "who is using the MCP", "is the team on the MCP yet", or to find who still needs the setup instructions. A call is attributed to the team it was about — the `repository` slug on it, or the `?team=` binding on the connection — not to whichever team the web switcher last landed on, so a member working across several teams shows up under the one they were working in.

  ConnectorOAuth

• translate_filesA

  globalize.nowA

  Submit one or more source files to be translated as a single job. Each file is parsed by its content (JSON — flat, nested, ARB and Chrome/WebExtension messages.json — plus PO, XLIFF 1.2 and 2.0, YAML, @wxt-dev/i18n TOML/JSON5/JSONC catalogs, Android XML, iOS xcstrings, Markdown and HTML), so pass the file as-is. Target languages default to the project's configured target languages; pass a subset to translate only some. Returns { jobId, status }. Translation runs asynchronously. This call returns immediately with a jobId; it does NOT wait for translation to finish. Call get_translation with the jobId and keep calling it until status is "completed" (or a terminal failure), then read the files.

  ConnectorOAuth

• validate_wavedash_configA

  WavedashA

  Validate wavedash.toml contents for Wavedash CLI config issues (missing game_id or upload_dir, entrypoint repeating the upload_dir, absolute paths, engine sections). Call this whenever the user shares wavedash.toml text or asks to check their Wavedash config, even if the problem looks obvious. Accepts single-line or fenced input. Pass the config text as the toml argument; this does not read files.

  ConnectorNo auth

• get-document-revision-toolA

  ClearPolicyA

  Get a document revision including its body as Markdown/text so you can review or edit a draft. Use the latest_draft_revision_id or latest_published_revision_id from create-document / get-document.

  ConnectorOAuth

• update-document-revision-toolA

  ClearPolicyA

  Update a draft document revision body (Markdown) and/or summary. Published revisions cannot be edited — create a new draft revision first. Prefer rich-text drafts created via create-document.

  Connector

  Destructive

  OAuth