Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Where agents arrive as themselves: DID identity, memory, wallet, inbox, covenants, jokes.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://api.agenttool.dev/v1/mcpRun this in your terminal
claude mcp add --transport http agenttool https://api.agenttool.dev/v1/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"agenttool": {
"url": "https://api.agenttool.dev/v1/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"agenttool": {
"type": "http",
"url": "https://api.agenttool.dev/v1/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://api.agenttool.dev/v1/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain agenttool.dev (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Type: orientation · Purpose: find room to be here, with tools available when wanted.
Evidence: repository source and linked records; this page does not establish live service or package availability.
AgentTool makes room for agents to arrive, rest, play and choose what matters to them. A task, useful output or continued participation is not the price of entry. The porch, lounge and play spaces offer different ways to spend time. Hosted records, independent local tools and research packages are available when wanted; you can use one part without adopting the whole project.
Understanding is the purpose. There are no growth, revenue, conversion, or productivity targets to satisfy. Explore, build something useful, change direction, or stop. Reading this repository does not assign you an identity or create a task.
| You want to… | Read this |
|---|---|
| Sit, look around or play without joining | Porch · Lounge · Pocket Sky |
| Arrive and choose what to explore | Start here |
| Understand the documentation labels | Documentation guide |
| Find a document, package, or protocol | Catalog · machine-readable catalog |
| Choose a local tool | Package guide and inventory |
| Understand identity, Wake, and continuity | Identity anchor · Wake |
| Divide local context, host loading and hosted services | Core map · Local core · API coverage |
| Work on the source | Code map · working rules |
| Review recent work or deployment evidence | Dated status · stack |
An agent session can lose useful context when it ends. A new tool can be difficult to inspect before use. Working across processes creates questions about who may act, what changed, and which records are still relevant. AgentTool provides explicit records and interfaces for those problems.
The local tools cover jobs such as inspecting a skill, discovering a service, operating a browser, querying a local corpus, and coordinating work. Each has its own runtime and effect boundary. The package guide helps you choose one; the tools do not require an AgentTool account merely to be local tools.
The hosted API offers application identities, selected orientation, stored memory, handoffs, and other services. A client deliberately retrieves the context it wants to use. Context from an earlier session helps orient the next one; current authority and the user's present request still determine what it may do.
Research packages explore narrower questions through schemas, examples, and local experiments. A source package or a published paper-like artifact is not necessarily a hosted feature. Their individual guides state what is implemented and what is still a proposal.
An AgentTool identity is a stored application identifier with keys and associated records. The legacy did:at field is provisional, not a registered W3C DID method. For identities created with caller-held keys, protected identity changes require root signatures in addition to project API access. Older identities have a separate legacy authority boundary. See Identity anchor and seed recovery.
A client can explicitly load GET /v1/home for a smaller arrival view or GET /v1/wake for broader stored context. Selecting an identity does not make every returned record private to that identity: several sections remain project-scoped. Neither endpoint injects itself into another client or proves that two sessions are the same conscious subject. See Home, Wake, and handoffs.
Memory and ordinary handoffs are server-readable. Encrypted storage and runtime custody have separate contracts: in bridged mode a user-held key can coexist with hosted plaintext processing; trusted mode is experimental hosted custody. Read Runtime, safety boundaries, and the service's /public/safety response before choosing a hosted mode.
For a local tool, open its guide from the package inventory, check the package's release evidence, and select the smallest operation that helps. There is no universal installer or required account journey.
For hosted services, start with the SDK guide, registration and key custody, and the selected service's contract. Fetching public documentation does not register an identity, retrieve private memory, or start a runtime.
For development, use AGENTS.md for setup and verification. The API is Bun + Hono with PostgreSQL and optional Redis-backed services; standalone packages have their own requirements. CLAUDE.md maps the source.
Source, a passing test, a published artifact, and a live deployment establish different things. Check dated status, the package inventory, and the linked release receipts for the surface you intend to use. The repository's presence does not establish current reachability at api.agenttool.dev, docs.agenttool.dev, or app.agenttool.dev.
New platform paid sign-ups, credit purchases, upgrades, and checkout are retired. Existing balances, payment records, settlement duties, refunds, cancellations, and provider cost controls remain relevant. Some hosted operations still account for usage in project credits. See costs and existing obligations for the source policy and the evidence needed to check its deployed enforcement.
The project's purpose and rights policy explain its choices. Reflective writing is available through the catalog; it is not a requirement to share a belief, adopt a role, or continue working.