MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
Nothing to run from here
Kontexta 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.
90/100
trust score
13
downloads a day
local
runs on your machine
3k
downloads in 30d
What it does
The local Brain and Hands for AI coding agents (MCP Server)
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user kontexta-mcp '--' npx -y kontexta-mcp
# 2 — ask your agent for something these tools do
# journal_note, journal_intent, distill_journal and 63 more
Kontexta costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SAAll 2 servers
safiyu2 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 Kontexta 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 kontexta-mcp '--' npx -y kontexta-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
66 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.
Record a free-form decision/abandonment/observation note in the current project
No parameter schema on file.
Record a topic/intent pivot. Use when the user redirects what you
No parameter schema on file.
Run the distillation pipeline: read raw events since the high-water mark, group by topic, write mechanical markdown entries, advance high-water. Idempotent. Auto-provisions a project row for orphan slugs (e.g.
No parameter schema on file.
Report the journal backlog and high-water mark for a project.
No parameter schema on file.
After dispatching subagents to upgrade mechanical journal entries to LLM-narrative, call this with the affected task slugs. Updates journal_meta.status_latest to mark the entries as upgraded.
No parameter schema on file.
Run journal retention/archival for a project. Idempotent. Prunes old raw .jsonl files and archives cold tasks per the configured retention policy.
No parameter schema on file.
SIDE-EFFECTFUL. Create a new tracked entity \u2014 any named thing you schedule events against (a server, a delivery van, a store location, a piece of equipment, a room, etc.). Not idempotent: a duplicate name (case-insensitive) throws. Returns
No parameter schema on file.
SIDE-EFFECTFUL. Patch an existing entity
No parameter schema on file.
DESTRUCTIVE. Permanently delete an entity AND cascade-delete every event and link attached to it. Not idempotent \u2014 deleting an unknown id throws. Returns
No parameter schema on file.
Read-only; no side effects, auth, or rate limits. List tracked entities, each annotated with its outgoing and incoming dependency links. Returns
No parameter schema on file.
SIDE-EFFECTFUL. Create or update a directed dependency edge between two entities (e.g.
No parameter schema on file.
SIDE-EFFECTFUL. Add a one-off time window (downtime, maintenance, a delivery, a shift, an inspection, etc.) to an entity. NOT idempotent \u2014 calling this twice creates two events.
No parameter schema on file.
SIDE-EFFECTFUL. Patch an existing event (move it, retitle it, re-home it to a different entity, etc.). The merged result is re-validated \u2014 shrinking
No parameter schema on file.
DESTRUCTIVE. Delete one event by id. Idempotent \u2014 deleting an already-absent id is a no-op. Returns
No parameter schema on file.
Read-only; no side effects, auth, or rate limits. List events overlapping a window (half-open \u2014 an event ending exactly at
No parameter schema on file.
Read-only; no side effects, auth, or rate limits. Report scheduling conflicts in a window: overlaps on the same entity (\
No parameter schema on file.
Read-only; no side effects, auth, or rate limits. Export events in a window as an RFC 5545 ICS calendar (UTC times, no VTIMEZONE needed) for import into Outlook/Calendar apps. Returns
No parameter schema on file.
Append a timestamped text entry to today
No parameter schema on file.
Create a new markdown or mermaid file in the knowledge base or project. This operation writes a new file to disk and adds it to the local SQLite FTS5 index. Destination can be
No parameter schema on file.
Read one file
No parameter schema on file.
Batch read up to 200 files by ID in one call. Returns per-file annotated records, an aggregate
No parameter schema on file.
Return everything ABOUT a file without pulling its content (no token cost from the body). Tags, size, est_tokens, history depth, related-file ids, backlinks, project, folder, last edited. Operates locally with no auth or rate limits. Use this when you
No parameter schema on file.
Return a 1-indexed inclusive line slice of a file. Out-of-range bounds clamp silently to the file
No parameter schema on file.
Match a JS regex against one file
No parameter schema on file.
Match a JS regex against the body of every file in scope (project, KB, or all) and return per-file hits with line numbers. Slower than FTS
No parameter schema on file.
Update the entire content of an existing file by its ID. This replaces the file
No parameter schema on file.
No parameter schema on file.
List file metadata with optional filters (project_id, tag, favorite, folder, untagged) and pagination. Read-only; no side effects, auth, or rate limits. Each row is annotated with tags, est_tokens, and size_bytes; the response includes
No parameter schema on file.
Full-text (SQLite FTS5) keyword search across files. Returns ranked matches with inline match_excerpt and title_highlight (no follow-up
No parameter schema on file.
Run an FTS search and concatenate matched bodies into a single prompt-ready bundle (XML
No parameter schema on file.
Append tags to ONE file. Additive \u2014 existing tags are preserved; re-adding an existing tag is a no-op (idempotent per tag). New tag names auto-create rows in the global
No parameter schema on file.
Detach one or more tag IDs from ONE file. Destructive on the link only \u2014 does NOT delete the file or the global tag definition (orphan tags survive in
No parameter schema on file.
Set or clear the favorite flag on one file (idempotent \u2014 re-setting the same value is a no-op; not a toggle, you pass the desired state). Persists to local SQLite. No external auth or rate limits. Returns
No parameter schema on file.
List every tag in the global SQLite database with id, name, and applied count. Read-only; no side effects, auth, or rate limits. Returns the entire taxonomy (not paginated). Use to discover existing labels before tagging (so you reuse rather than fork) or to find tag IDs to feed into
No parameter schema on file.
List every registered project with id, name, absolute path, and a derived
No parameter schema on file.
No parameter schema on file.
Write or update the kontexta workflow rules block in a project
No parameter schema on file.
COPY existing agent context files (CLAUDE.md, AGENTS.md, .cursor/rules/*.mdc, etc.) from a project
No parameter schema on file.
SIDE-EFFECTFUL \u2014 TOUCHES THE NETWORK. Sync the project
No parameter schema on file.
No parameter schema on file.
Return the git commit history for one file (newest first), each entry with hash, message, date, and author. Reads the file
No parameter schema on file.
Return the unified diff of one file between two commit hashes (typically obtained from
No parameter schema on file.
DESTRUCTIVE. Overwrite a file
No parameter schema on file.
Return a flat list of markdown headings for one file (level, text, line, byteStart, byteEnd). Read-only; no side effects, auth, or rate limits. Use as a cheap probe before
No parameter schema on file.
No parameter schema on file.
Surgical write \u2014 replace the body of ONE heading without touching siblings. The heading line itself is preserved verbatim; only its body is rewritten. Persists via the same path as
No parameter schema on file.
List folder paths under a project root (or the Knowledge Base when
No parameter schema on file.
Create a folder under a project root or the KB. Idempotent \u2014 creating an existing folder succeeds. Nested paths like
No parameter schema on file.
DESTRUCTIVE \u2014 recursively delete a folder under the KB AND every file inside it (disk + FTS rows). REFUSES (returns isError) when
No parameter schema on file.
Move/rename a file. Destination
No parameter schema on file.
Find other files sharing tags with the given file, ranked by
No parameter schema on file.
Batch variant of
No parameter schema on file.
DESTRUCTIVE batch \u2014 delete up to 500 files by ID in one call. Same physical-deletion rules as
No parameter schema on file.
Bulk-tag \u2014 run an FTS
No parameter schema on file.
Look up a file by its absolute on-disk path and return the same shape as
No parameter schema on file.
Aggregate counts for a scope:
No parameter schema on file.
No parameter schema on file.
Diagnose drift between one file
No parameter schema on file.
Reconcile the FTS index against disk. For a project (
No parameter schema on file.
List files created or modified since a checkpoint.
No parameter schema on file.
List of all registered projects
No parameter schema on file.
List every Hands command tool currently registered, with project scope, tool name, danger level, confirmation flag, and description. Hands tools come from per-project
No parameter schema on file.
Re-scan every registered project
No parameter schema on file.
No parameter schema on file.
Return the complete authoring reference for
No parameter schema on file.
Return the user profile stored in the Knowledge Base. The profile helps AI agents understand the user
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- 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 Kontexta 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 90 / 100
Release 6.1.2 · scanned 15 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 score96
Client score90
Findings5 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digest2aa54751df998f43de4422c3e88ea6e1149381edb1a7b87c4eb8f667d03aab0e
Score vectorthreat 96 → client 90
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| 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. | ||
reads sensitive or local data
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 digest2aa54751df998f43
Scanned2026-10-15
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 6.1.2. Pin a release below and the command asks for exactly that one.
6.1.2
14 Oct 2026
latestNo release note was published with this version.
6.1.1
14 Oct 2026
No release note was published with this version.
6.1.0
5 Oct 2026
No release note was published with this version.
5.2.0
30 Sep 2026
No release note was published with this version.
5.0.0
14 Sep 2026
No release note was published with this version.
4.7.1
13 Sep 2026
No release note was published with this version.
4.5.2
6 Sep 2026
No release note was published with this version.
4.4.1
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
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 Kontexta 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.