goodnight000/api-anything

选用指南

AI 根据 README 整理 · 2026/10/17 13:41:15

使用方式

通过命令行使用，支持 MCP 和 TypeScript 调用。

查看 README 依据

# API Anything [](https://github.com/goodnight000/api-anything/actions/workflows/ci.yml) **Teach your agent a website once. After that, it calls the site like an API instead of driving a browser.** API Anything watches a site's own page make a request and learns which parts of it are your inputs. It saves the result as an operation. Your agent calls that operation with new inputs over MCP, the CLI or TypeScript, and gets JSON back over plain HTTP.

部署要求

需要 Node.js 22.13+，创建操作时需要 Chromium 浏览器。

查看 README 依据

Paste this into Claude Code, Codex or another coding agent: ```text Set up API Anything for me: https://github.com/goodnight000/api-anything/blob/main/INSTALL.md ``` The agent checks Node 22.13+, builds and installs the `api-anything` command, confirms that a call works, then connects the MCP server and the skill to itself. Restart the agent, then ask it something like "What does Goodreads rate Piranesi?" <details> <summary>Install by hand</summary> The package isn't on npm yet. Don't use `npm install -g github:...`, because it fails under npm 11. ```sh

`reason` and a `next` step. Connect an agent with `codex mcp add api-anything -- api-anything mcp`, `claude mcp add --scope user api-anything -- api-anything mcp`, or this MCP entry: ```json { "mcpServers": { "api-anything": { "command": "api-anything", "args": ["mcp"] } } } ``` </details> Over MCP an agent **calls** operations, using four tools: `list_sites`, `list_operations`, `call_operation` and `login`. To **create** operations, an agent needs a shell and the [skill](skills/api-anything/SKILL.md). A Chromium browser is needed only for creating operations

已知限制

仅支持已学习的操作，不覆盖所有网站功能；不解决 CAPTCHA；不包含写操作。

查看 README 依据

- It knows only the operations it was taught. It doesn't support every feature of every site. - Repair can fail. There is no CAPTCHA solving, and if a site challenges real Chrome, you have to clear the challenge by hand. - No write operations are bundled. LinkedIn messaging isn't bundled and hasn't been tested against LinkedIn. Writes are tested only against a local fixture, and they need `--allow-writes`. An HTTP 2xx doesn't prove a message was delivered. - Credentials stay in `~/.api-anything`, and specs hold references, never values. Read each