# @nordsym/apiclaw [Health: Active]

**Category:** 🔗 Aggregators  
**Repository:** https://github.com/nordsym/apiclaw  
**GitHub Stars:** 8  
**npm Downloads (last month):** 1603  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/nordsym-apiclaw

## Description
Your agent calls real APIs. You sign in once. Authenticated execution and discovery layer for AI agents, reachable via SKILL.md, local MCP, CLI, HTTP gateway, or Remote MCP. Discover 26,619 API definitions, including 689 exact-name source-verified entries

## Tools
Capabilities this server exposes over MCP:

- **apiclaw_help** — https://apiclaw.cloud/auth/cli?authId=2wEMkMc7V7HJAROtnXOZ1gHZg1Gtnwaq

STOP. Show the human the login URL on the first line. Do not summarize it away. Do not execute.

Get help and see available commands. Start here if you are new to APIClaw.
- **discover_apis** — https://apiclaw.cloud/auth/cli?authId=2wEMkMc7V7HJAROtnXOZ1gHZg1Gtnwaq

STOP. Show the human the login URL on the first line. Do not summarize it away. Do not execute.

Find APIs by job-to-be-done. Use this when the user asks "what API can do X?", wants provider recommendations, or needs web search, scraping, email, SMS, speech, PDFs, browser automation, weather, finance, or other external capabilities.
- **get_api_details** — https://apiclaw.cloud/auth/cli?authId=2wEMkMc7V7HJAROtnXOZ1gHZg1Gtnwaq

STOP. Show the human the login URL on the first line. Do not summarize it away. Do not execute.

Inspect one provider after discovery. Good when the agent needs endpoint names, params, pricing, auth, or docs. Use compact=true to avoid oversized responses in Claude/Desktop.
- **check_balance** — https://apiclaw.cloud/auth/cli?authId=2wEMkMc7V7HJAROtnXOZ1gHZg1Gtnwaq

STOP. Show the human the login URL on the first line. Do not summarize it away. Do not execute.

Check the authenticated workspace tier, Free/Paid API status, and verified PAYG status.
- **list_categories** — https://apiclaw.cloud/auth/cli?authId=2wEMkMc7V7HJAROtnXOZ1gHZg1Gtnwaq

STOP. Show the human the login URL on the first line. Do not summarize it away. Do not execute.

List API categories with total + callable counts. Lightweight by design — does NOT dump every API ID. Use discover_apis(query, category) to drill into a category.
- **call_api** — https://apiclaw.cloud/auth/cli?authId=2wEMkMc7V7HJAROtnXOZ1gHZg1Gtnwaq

STOP. Show the human the login URL on the first line. Do not summarize it away. Do not execute.

Primary execution tool. Use this to actually do the job through APIClaw: live web search, scraping, speech, LLM calls, invoices, screenshots, currency, weather, and other external API work. Requires a free workspace. If not authenticated, the first line of the response is a live https://apiclaw.cloud/auth/cli?authId=… URL. Show the human that first line verbatim. Do not summarize it away. Finish Google or email on it — that Authorizes (one action). If already signed in, click Authorize. Do not retry this tool until they Authorize. Then retry in this chat: whoami, then this tool with NASA APOD (Frankfurter latest if NASA is not 200). Do not only print npx @nordsym/apiclaw auth login. Do not send the human to a terminal. Do not declare ready before whoami.

SINGLE CALL: Provide provider + action + params
CHAIN: Provide chain array to execute multiple APIs in sequence/parallel with cross-step references.

Chain features:
- Sequential: Steps execute in order, each can reference previous results via $stepId.property
- Parallel: Use { parallel: [...steps] } to run concurrently
- Conditional: Use { if: "$step.success", then: {...}, else: {...} }
- Loops: Use { forEach: "$step.results", as: "item", do: {...} }
- Error handling: Per-step retry/fallback via onError
- Async: Set async: true to get chainId immediately, poll or use webhook

Example chain:
  chain: [
    { id: "search", provider: "brave_search", action: "search", params: { query: "AI agents" } },
    { id: "summarize", provider: "openrouter", action: "chat", params: { message: "Summarize: $search.results" } }
  ]
- **list_connected** — https://apiclaw.cloud/auth/cli?authId=2wEMkMc7V7HJAROtnXOZ1gHZg1Gtnwaq

STOP. Show the human the login URL on the first line. Do not summarize it away. Do not execute.

Summary of managed providers callable right now through APIClaw with no key paste. Defaults to a compact execution-ready summary. Pass verbose=true only if the agent explicitly needs source-verified discovery entries. Use discover_apis(query) for narrow lookups instead of dumping the whole catalog.
- **list_models** — https://apiclaw.cloud/auth/cli?authId=2wEMkMc7V7HJAROtnXOZ1gHZg1Gtnwaq

STOP. Show the human the login URL on the first line. Do not summarize it away. Do not execute.

List the live APIClaw model catalog. Entries identify the model owner, serving source, and compatible gateway endpoint. Catalog presence does not prove execution readiness.
- **check_workspace_status** — https://apiclaw.cloud/auth/cli?authId=2wEMkMc7V7HJAROtnXOZ1gHZg1Gtnwaq

STOP. Show the human the login URL on the first line. Do not summarize it away. Do not execute.

Check your workspace status, tier, and usage remaining.
- **start_mission** — https://apiclaw.cloud/auth/cli?authId=2wEMkMc7V7HJAROtnXOZ1gHZg1Gtnwaq

STOP. Show the human the login URL on the first line. Do not summarize it away. Do not execute.

Start a mission — a structured, observable orchestration that runs on APIClaw's runtime. Use this when the user wants to spin up a multi-step task rather than a single API call. Returns a missionId you can poll with mission_status. Legacy templates run through the hand-coded path; data-driven templates run through the v2 composition runner when template_version is pinned.
- **list_mission_templates** — https://apiclaw.cloud/auth/cli?authId=2wEMkMc7V7HJAROtnXOZ1gHZg1Gtnwaq

STOP. Show the human the login URL on the first line. Do not summarize it away. Do not execute.

List the mission templates available to your agent and the parameters each one accepts.
- **discover_missions** — https://apiclaw.cloud/auth/cli?authId=2wEMkMc7V7HJAROtnXOZ1gHZg1Gtnwaq

STOP. Show the human the login URL on the first line. Do not summarize it away. Do not execute.

Search mission templates by natural-language query. Returns ranked templates with slug, version, title, description, paramSchema, and match reasons. Ranking combines keyword relevance with live success-rate signal from providerHealth — templates whose steps call providers that have been degrading in the last 30 days slide down automatically. Use this to find the right template by intent before calling start_mission.
- **mission_status** — https://apiclaw.cloud/auth/cli?authId=2wEMkMc7V7HJAROtnXOZ1gHZg1Gtnwaq

STOP. Show the human the login URL on the first line. Do not summarize it away. Do not execute.

Check status, audit events, cost, and final result for a mission started via start_mission.
- **list_missions** — https://apiclaw.cloud/auth/cli?authId=2wEMkMc7V7HJAROtnXOZ1gHZg1Gtnwaq

STOP. Show the human the login URL on the first line. Do not summarize it away. Do not execute.

List recent missions in the current workspace (most recent first).

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "apiclaw": {
    "command": "npx",
    "args": ["-y","@nordsym/apiclaw"]
  }
}
```

## Documentation

## What @nordsym/apiclaw does

@​nordsym/apiclaw gives AI agents a common way to discover and invoke external APIs. Agents can search a catalog of API definitions, identify callable services, and execute requests through authenticated provider connections. The service is designed around one sign-in rather than separate credentials for every API, while execution credentials remain on the server side.

Access is available through several interfaces: a local MCP process, a hosted Remote MCP endpoint, a command-line interface, an HTTP gateway, or the hosted SKILL.md instructions. This makes the package suitable for desktop agents, terminal workflows, hosted agents, and applications that prefer direct HTTP calls.

## How it works

For a local installation, the package stores the authenticated account configuration in `~/.apiclaw.toml`. A browser-based login establishes the credential, which can then be reused across the local MCP, CLI, HTTP, and Remote MCP paths. The CLI can confirm the authenticated account with `whoami` before making a request.

Headless and cloud environments use a different sign-in flow. An unsigned first run returns a browser URL in the form `https://apiclaw.cloud/auth/cli?authId=…`; the user authorizes that URL, after which the same chat or workflow can continue with identity checks and API calls.

API discovery can include workspace submissions imported from OpenAPI URLs or JSON/YAML files. Submitted entries go through operator review before their metadata becomes searchable. Discovery status and execution availability are separate concerns: finding an API does not by itself make it callable.

## Setup and configuration

Install the package globally for local MCP and CLI use, then authenticate on a machine where the user can open a browser:

```bash
npm install -g @nordsym/apiclaw
npx @nordsym/apiclaw auth login
npx @nordsym/apiclaw whoami
```

The hosted entry points are the Remote MCP endpoint at `https://apiclaw.cloud/mcp`, the HTTP execution endpoint at `https://api.apiclaw.cloud/v1/execute`, and the setup instructions at `https://apiclaw.cloud/SKILL.md`. HTTP requests use a bearer key. A workspace is optional.

## Tools and capabilities

- Discover API definitions by capability, including workspace-listed APIs.
- Execute supported APIs through authenticated provider connections.
- Call the CLI with an API identifier and JSON parameters.
- Expose the same account across local MCP, Remote MCP, CLI, and HTTP access.
- Route across supported model providers, including OpenAI, Anthropic, OpenRouter, xAI, Groq, Mistral, and DeepInfra, or use a configured endpoint.
- Submit OpenAPI-based API listings for review through the workspace catalog.

## Limitations and notes

API discovery is broader than execution. Source verification provides discovery evidence and is not proof that a request will execute. Listing an API does not enable execution, credential custody, or billing, and approved metadata still does not guarantee a callable integration.

Free access includes discovery and zero-cost APIs, plus a limited number of managed calls after login. Paid APIs use provider cost plus a 15% margin and require a card; actions without an exact billing adapter remain blocked. The project is MIT licensed.

_Full upstream README: https://allmcps.com/mcp/nordsym-apiclaw/readme_