MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
Nothing to run from here
Aman 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
1
downloads a day
local
runs on your machine
92
downloads in 30d
What it does
MCP server for the aman AI companion ecosystem — identity, tools, workflows, guardrails, evaluation
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user aman-mcp '--' npx -y @aman_asmuei/aman-mcp
# 2 — ask your agent for something these tools do
# identity_read, identity_summary, identity_update_session and 44 more
Aman costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
AAAll 2 servers
@aman_asmuei2 servers
2 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 Aman 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 Node.js — the current LTS (24) is the safe choice; npx 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 aman-mcp '--' npx -y @aman_asmuei/aman-mcpReconnect, 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 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
47 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.
Read the user
No parameter schema on file.
Get a structured summary of the identity: AI name, user name, trust level, personality.
No parameter schema on file.
Update the Session section of core.md with resume, active topics, and recent decisions.
No parameter schema on file.
Update a specific section of core.md by heading name. Replaces the section content.
No parameter schema on file.
Update the Dynamics section of core.md with current personality state. Call this to adapt tone based on time of day, session energy, or conversation signals.
No parameter schema on file.
Generate a deterministic image generation prompt from the AI
No parameter schema on file.
List all installed tools with their status (MCP vs manual).
No parameter schema on file.
Search the tool registry by query string.
No parameter schema on file.
Add a new tool to kit.md.
No parameter schema on file.
Remove a tool from kit.md by name.
No parameter schema on file.
List all defined workflows.
No parameter schema on file.
Get a specific workflow
No parameter schema on file.
Add a new workflow with named steps.
No parameter schema on file.
Update the steps of an existing workflow by name.
No parameter schema on file.
Remove a workflow by name.
No parameter schema on file.
List all rule categories and their rules.
No parameter schema on file.
Check if a proposed action might violate any rules. Returns matching violations.
No parameter schema on file.
Add a new rule to a category. Creates the category if it doesn
No parameter schema on file.
Remove a rule by 1-based index from a category.
No parameter schema on file.
Toggle a rule
No parameter schema on file.
Get current evaluation metrics: sessions count, trust level, trajectory, recent ratings.
No parameter schema on file.
Log a session evaluation with rating and notes.
No parameter schema on file.
Record a milestone achievement in the evaluation log.
No parameter schema on file.
Get a full evaluation report with status, milestones, and summary.
No parameter schema on file.
List all skills (installed and available from built-in registry).
No parameter schema on file.
Search skills by name or description.
No parameter schema on file.
Install a skill by name. Adds it to skills.md.
No parameter schema on file.
Uninstall a skill by name. Removes it from skills.md.
No parameter schema on file.
Read a text file and return its contents. Supports all common text formats (.txt, .md, .json, .js, .ts, .py, .html, .css, .yml, .sql, etc). For binary documents (.docx, .pdf), use doc_convert instead.
No parameter schema on file.
Convert a binary document to readable text. Supports PDF (built-in) and DOCX (built-in). For PPTX, XLSX, images: install Docling (pip install docling) or use
No parameter schema on file.
List files and directories at a given path. Shows file names with sizes. Hides hidden files and node_modules by default.
No parameter schema on file.
Create a new active intention (niyyah). Use when Aman commits to a durable goal across sessions.
No parameter schema on file.
Read a single intention by id.
No parameter schema on file.
List intentions filtered by status (default: active) and/or horizon.
No parameter schema on file.
Patch an intention
No parameter schema on file.
Bump an intention
No parameter schema on file.
Move an intention to complete or abandoned with a reason.
No parameter schema on file.
No parameter schema on file.
Create a new project at LRU position #1. Existing projects shift down; #11 evicts to off-list. Optional createdAt/lastTouchedAt support back-dating during migration of existing work.
No parameter schema on file.
Read a single project by id (full body including sessionLog).
No parameter schema on file.
List projects filtered by status and/or LRU membership. Default: active+inActiveList.
No parameter schema on file.
Fast path — return the position-1 active project, or null. Used by SessionStart hook and
No parameter schema on file.
Load a project by name or id (fuzzy match). Brings to position #1; restores from off-list. Returns disambiguation candidates if ambiguous.
No parameter schema on file.
Bump an in-list project to position #1 and update lastTouchedAt. Returns null if project is off-list (use project_load instead).
No parameter schema on file.
Append a timestamped session note to the project
No parameter schema on file.
Transition project lifecycle to complete / abandoned / paused with reason. Frees LRU slot.
No parameter schema on file.
Patch project metadata (name, niyyah, workspaces, linkedIntentionId). When linkedIntentionId changes, the linked intention
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 Aman 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.9.2 · scanned 14 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 digestb7c1161ee0889f5ecf7b3d4b5498771940599275199218e357fc243734d16070
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 surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, 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 |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
can execute shell commands or code
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 digestb7c1161ee0889f5e
Scanned2026-10-14
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.9.2. Pin a release below and the command asks for exactly that one.
0.9.2
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 Aman 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.