Validate Formhaus form definitions and simulate multi-step paths against the real engine.
Nothing to run from here
Apicircle Cli 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.
99/100
trust score
12
downloads a day
local
runs on your machine
281
downloads in 30d
What it does
Command-line interface for API Circle Studio. Run mock servers, drive the MCP server, and import OpenAPI / Postman / Insomnia collections from any terminal.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user apicircle-cli-mcp '--' npx -y @apicircle/cli
# 2 — ask your agent for something these tools do
# request.create, request.read, request.update and 66 more
Apicircle Cli costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
APAll 1 server
@apicircle1 server
1 category
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 Apicircle Cli 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 apicircle-cli-mcp '--' npx -y @apicircle/cliReconnect, 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
69 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.
Create a new request from explicit fields and persist it.
No parameter schema on file.
Read a request by id, or list summaries (id, name, method, url) when no id is provided.
No parameter schema on file.
Patch fields on an existing request.
No parameter schema on file.
Delete a request by id.
No parameter schema on file.
Create a folder under an optional parent folder. Optionally seed folder-level
No parameter schema on file.
Read a folder by id, or list all folders when no id is provided.
No parameter schema on file.
Update a folder. Supply
No parameter schema on file.
Delete a folder. Direct children (sub-folders + requests) are reparented to the deleted folder
No parameter schema on file.
Create a new environment (or upsert one with the same name).
No parameter schema on file.
Read environments — pass
No parameter schema on file.
Replace the variables list of an environment.
No parameter schema on file.
Delete an environment by name.
No parameter schema on file.
Set (or clear) the active environment. Pass
No parameter schema on file.
Replace the global environment priority order (highest priority first). Strings are interpreted as local env names. To target a linked env, pass
No parameter schema on file.
Import an environment from the JSON shape produced by
No parameter schema on file.
Create a new execution plan (sequence of request steps).
No parameter schema on file.
Read a plan by id, or list all plans when no id is provided.
No parameter schema on file.
Patch fields on an existing plan (name, steps, envPriorityOrder, stopOnAssertionFailure). Plan variables have their own tool (plan.set_variables).
No parameter schema on file.
Delete a plan by id. Drops history rows referencing this plan.
No parameter schema on file.
Append a step to an execution plan. Optional
No parameter schema on file.
Remove a step from a plan by 0-based index.
No parameter schema on file.
Replace the plan steps with a new permutation. The supplied indices must reference valid current step indices.
No parameter schema on file.
Replace the plan-scoped variables. These live highest-priority during plan runs (above environment vars, below context vars).
No parameter schema on file.
Run a plan headlessly (server-side). Currently returns a not-implemented marker — full execution requires the Desktop or browser runtime which the MCP host does not own. The Desktop integration overrides this tool with a real runner.
No parameter schema on file.
Add an assertion to a request.
No parameter schema on file.
List assertions for a request, or fetch a single assertion by id.
No parameter schema on file.
Replace an existing assertion (matched by
No parameter schema on file.
Remove an assertion from a request.
No parameter schema on file.
Return the full
No parameter schema on file.
Bulk-replace the workspace. Pass
No parameter schema on file.
Create a new environment from an LLM-shaped JSON envelope. The model produces { name, variables: [{ key, value, encrypted }] }; this tool validates and persists it.
No parameter schema on file.
Add an assertion to a request from an LLM-shaped JSON envelope. Useful when the user asks
No parameter schema on file.
Create an execution plan from an LLM-shaped JSON envelope. The model produces { name, stepRequestIds: [...] } and the tool validates that each id exists in the workspace before persisting.
No parameter schema on file.
Create a fully-shaped request from an LLM-shaped JSON envelope: method, url, headers, query params, body, auth, and inline assertions. The model produces a flat object; this tool generates the request id, normalizes auth (defaults to
No parameter schema on file.
Patch an existing request from an LLM-shaped JSON envelope. Provided fields replace the existing values; omitted fields are left untouched. Arrays (headers, queryParams, assertions) are full replacements when supplied. Returns
No parameter schema on file.
Create a recursive folder hierarchy from an LLM-shaped JSON envelope. The model produces
No parameter schema on file.
Append one or more steps to an existing execution plan from an LLM-shaped JSON envelope. The model produces
No parameter schema on file.
Replace the plan-scoped variables on an execution plan from an LLM-shaped JSON envelope. The model produces
No parameter schema on file.
Declare an endpoint
No parameter schema on file.
Scan source code for HTTP route definitions (Express, FastAPI, NestJS, Spring) and return candidate requests for the user to confirm before import.
No parameter schema on file.
Generate runnable code (curl / JavaScript fetch / Node Axios / Python requests / Go net/http / Rust reqwest) that reproduces a workspace request.
No parameter schema on file.
Export an existing folder (and its subtree) to the API Circle exchange JSON format.
No parameter schema on file.
Import an
No parameter schema on file.
Link a workspace by fetching its
No parameter schema on file.
Re-pull a linked workspace
No parameter schema on file.
Create a
No parameter schema on file.
Search the API Circle marketplace for public workspaces tagged with
No parameter schema on file.
Replace a repo
No parameter schema on file.
Register a Global File Asset entry. Bytes are NOT carried — MCP returns the new asset id and the asset enters the
No parameter schema on file.
Rename or re-describe a Global File Asset. Provenance refs (workingBranchRef, baseBranchRef) and binary metadata (slotId, sha256, size, mimeType) are preserved verbatim.
No parameter schema on file.
Delete a Global File Asset. Cascades — every request body and mock-response body that referenced the asset is unbound in the same mutation. The result envelope includes the consumer list that was cleared so the caller can report what changed.
No parameter schema on file.
List request-run history rows in reverse-chronological order. Filter by
No parameter schema on file.
Fetch a single history row in full (headers, body preview, assertion results).
No parameter schema on file.
Delete a single request-run row by id.
No parameter schema on file.
Drop every request-run + plan-run older than
No parameter schema on file.
Parse a
No parameter schema on file.
Parse an OpenAPI / Swagger spec (YAML or JSON) and create one Request per operation. Returns the list of created request ids.
No parameter schema on file.
Parse a Postman v2/v2.1 collection JSON and create one Request per item.
No parameter schema on file.
Parse an Insomnia v4 export and create one Request per resource of type
No parameter schema on file.
Parse an HTTP Archive (.har) JSON and create one Request per recorded entry. Cookies, response, and timings are dropped.
No parameter schema on file.
List the workspaces this workspace links to (consumes). Each entry includes its source repo/branch, scope, pinned version, required secret-key ids, and the current version of its cached release ledger.
No parameter schema on file.
Read one linked workspace by id, including its cached release ledger (the versions available to pin to).
No parameter schema on file.
Update an existing linked workspace
No parameter schema on file.
Unlink a workspace by id. Removes the link, its cached release ledger, every local override for it, the cached collections/environments snapshot, and any per-link session entry. The source repo is untouched.
No parameter schema on file.
List this workspace
No parameter schema on file.
Publish a new release of this workspace. Appends a semver version + markdown notes to the ledger and bumps currentVersion. The release is fingerprinted with a SHA-256 of the workspace at publish time. Rejects invalid semver or a duplicate version. Does NOT create a Git tag or GitHub Release.
No parameter schema on file.
Mark a published version as deprecated (soft signal). Consumers see a warning but the version stays installable. Errors if the version is unknown or no ledger exists.
No parameter schema on file.
Withdraw (yank) a published version (hard signal). Consumers are warned the version is broken / unsafe and told to move to a different one. The entry stays in the ledger. Errors if the version is unknown or no ledger exists.
No parameter schema on file.
List every workspace registered with this server, including which one is currently active.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source is public; its licence metadata reads SEE LICENSE IN LICENSE rather than naming a licence
- 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 Apicircle Cli 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 99 / 100
Release 1.3.0 · 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 score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest064f7f3b2a628bc29aba3efe0e683b5ccf7d10d9fbdfd16f4eae91529dde74aa
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| 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. minimal 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. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
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 digest064f7f3b2a628bc2
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 1.3.0. Pin a release below and the command asks for exactly that one.
1.3.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 Apicircle Cli 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.