Chroma’s official MCP server: vector search and collection management for RAG workflows.
Nothing to run from here
letin: Power Query (M) is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
trust score
2
downloads a day
local
runs on your machine
48
downloads in 30d
What it does
Inspect, refactor, lint, run and version Power Query (M) in Excel workbooks and Power BI projects.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user letin-power-query-m-mcp '--' uvx letin
# 2 — ask your agent for something these tools do
# list_sources, list_queries, get_query and 28 more
letin: Power Query (M) costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SCAll 4 servers
S-CurveLabs4 servers
3 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts letin: Power Query (M) as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user letin-power-query-m-mcp '--' uvx letinReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take LETIN_HOME (Folder for query snapshots. Defaults to %LOCALAPPDATA%\letin.) if you want to set it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
31 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List workbooks open in Excel and models open in Power BI Desktop (both usable as source), and explain the other source forms.
No parameter schema on file.
Every query with its kind (query/function/parameter), step count, load destination, and what it depends on / is used by.
No parameter schema on file.
Full M code of one query plus its parsed steps, data sources, dependencies and dependents.
No parameter schema on file.
Query-to-query lineage. With query, only its upstream and downstream. format: 'json' or 'mermaid'.
No parameter schema on file.
Inventory of every external source (files, folders, servers, URLs) each query reads, and whether it is hard-coded or parameterised.
No parameter schema on file.
Search the M of every query. scope: all | code | strings | comments. Returns query, step and line for each hit.
No parameter schema on file.
Audit queries for folding breakers, hard-coded paths/servers, dead steps, brittle column lists, untyped columns,
No parameter schema on file.
Replace a query's M (or create it with create_if_missing). Rejects unbalanced brackets/strings before writing.
No parameter schema on file.
Delete a query. Refuses when other queries reference it unless force=true.
No parameter schema on file.
Rename a query and rewrite every reference to it in all other queries (token-aware: strings, comments and
No parameter schema on file.
Rename a step inside a query and every reference to it.
No parameter schema on file.
Delete a step and rewire the steps that used it to the step it read from.
No parameter schema on file.
Find and replace across all (or the listed) queries in one go, e.g. repoint a server or folder.
No parameter schema on file.
Turn a hard-coded text value (path, server, URL) into a Power Query parameter and reference it everywhere.
No parameter schema on file.
Catalog of guided actions for apply_transform (unpivot, pivot, group_by, merge, filter, types, ...) with their params.
No parameter schema on file.
No parameter schema on file.
Copy queries between workbooks / projects / folders, bringing the queries they depend on along.
No parameter schema on file.
Write every query to folder as one .pq file each plus pq-manifest.json: ready to commit to git and diff in a PR.
No parameter schema on file.
Load .pq files from folder back into source. mode='update' changes/adds queries; mode='sync' also deletes
No parameter schema on file.
Compare the queries of two sources (workbook vs workbook, workbook vs exported folder, PBIP vs PBIP ...).
No parameter schema on file.
Snapshots taken automatically before each write to this source, newest first.
No parameter schema on file.
Roll back to a snapshot. With queries, only those are restored; otherwise the whole query set is put back
No parameter schema on file.
No parameter schema on file.
Pretty-print M (an expression or a section document): one step per line, long calls broken at their arguments,
No parameter schema on file.
Format one query, or every query, in place (same guarantees as format_m).
No parameter schema on file.
Look up the M standard library (generated from the real engine: 850+ members). Give an exact name
No parameter schema on file.
No parameter schema on file.
Freshly evaluate a query, or the query only up to step, and return columns, types and sample rows. Use it to get real
No parameter schema on file.
Evaluate EVERY step of a query in one engine call and describe each one (columns, types, first rows rows, or the
No parameter schema on file.
Refresh one query in an open Excel workbook and wait for it; returns the mashup engine's error text if it fails.
No parameter schema on file.
Column names and first rows of a query that is loaded to a worksheet table (open Excel workbook only).
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install letin: Power Query (M) or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 93 / 100
Release 0.2.0 · scanned 13 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings1 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digestb92c2242886e9b1660d8b3ff8ac915e87eebeb764ababc75be6a8e32c6dae626
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (31 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_sources | no tags | |
| list_queries | no tags | |
| get_query | no tags | |
| dependency_graph | no tags | |
| list_data_sources | no tags | |
| find_in_queries | no tags | |
| lint_queries | no tags | |
| set_query | no tags | |
| delete_query | state-write | state-write: declares destructiveHint: true |
| rename_query | no tags | |
| rename_step | no tags | |
| remove_step | no tags | |
| replace_in_queries | no tags | |
| extract_parameter | no tags | |
| list_transforms | no tags | |
| apply_transform | no tags | |
| copy_queries | no tags | |
| export_queries | no tags | |
| import_queries | no tags | |
| diff_queries | no tags | |
| list_snapshots | no tags | |
| restore_snapshot | no tags | |
| validate_m | no tags | |
| format_m | no tags | |
| format_queries | no tags | |
| m_function_help | no tags | |
| evaluate_m | no tags | |
| evaluate_query | no tags | |
| evaluate_steps | no tags | |
| refresh_query | no tags | |
| preview_query | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestb92c2242886e9b16
Scanned2026-10-13
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.2.0. Pin a release below and the command asks for exactly that one.
0.2.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish letin: Power Query (M) can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.