A directory for your assistant
Big ideas.
Missing tools.
Meet Agent Index.
Help your assistant find the skills, tools and connections it needs to get the job done. Ask for the outcome. Let it look for what’s missing.
Install once. Ask for outcomes.
npx agentindex setup --client claudePlanned install command · Not published yet. The directory is live to explore now.
You
Turn this project into a launch video.
I need a video workflow for this project.
I’ll look for a suitable capability in Agent Index.
Brag
latent-spaces
A project-to-video workflow using Hyperframes.
Node.js · FFmpeg · Hyperframes
Review the setup, connect what’s needed, then continue the task.
See matches ↗From established teams
and independent builders.
A smaller gap between ask and done
The request is the starting point.
You shouldn’t have to interrupt a task to go tool hunting. Agent Index gives your assistant a place to look.
Install once.
Add the Agent Index skill to Claude Code or Codex, with persistent guidance to look for missing capabilities.
Ask for the outcome.
Describe what you want to accomplish. You don’t need to know which tool exists or ask to search the index.
Find a way forward.
When it needs a capability, your assistant can search, review the setup, and help connect it before continuing.
The assistant chooses when to search. It can use the tools it already has, and asks for any additional permissions or paid connections the task needs. A search result is a candidate to review—not an automatic installation.
Start with something you want to do
An outcome. A useful next step.
CREATE / 01
A launch deserves a video.
“Make a launch video for this project.”
Find a video workflow with the right tools, dependencies and setup instructions.
EXTRACT / 02
Put your documents to work.
“Pull the tables out of these PDFs.”
Discover skills for PDFs, spreadsheets and presentations, with client compatibility spelled out.
CONNECT / 03
Give the task a browser.
“Test my signup flow end to end.”
Find browser tools and testing workflows when your assistant doesn’t already have them.
Know what you’re connecting
Useful details.
Before you install.
A name and a link aren’t enough. Each entry brings the source, setup and requirements together so your assistant can make an informed choice.
Traceable sources
Publisher links and reviewed revisions, so you can inspect where a capability comes from.
Setup without the guesswork
Documented clients, dependencies, license information and provider pricing notes.
Clear verification labels
Source review, installation tests and completed task tests are separate. We show what has—and hasn’t—been checked.
Start exploring
Your next capability
could already be here.
The directory is live. The install-once skill for Claude Code and Codex is in preview; the public installer is coming after validation.
Find a capabilityFor MCP-compatible clients
Connect to the live index
Add this URL as a remote MCP server in a client that supports Streamable HTTP. It provides discovery tools; it doesn’t install the skill’s persistent guidance.
https://www.agentindex.ai/api/v1/mcpInspect an API response ↗A few things to know.
Do I have to ask for Agent Index by name?
That’s the idea behind the install-once skill: it adds guidance to search when the assistant needs a capability it doesn’t have. You can ask for the outcome normally. Selection is a model decision, so discovery is encouraged rather than guaranteed.
Does Agent Index read my conversations?
There is no background conversation monitor. When the assistant searches, the index receives the search terms it sends. The skill directs it to use short capability terms rather than private files, secrets or the full conversation.
Will it install or pay for tools automatically?
No. The index returns candidates and setup instructions. Your assistant reviews the requirements and works within your authorization. Provider accounts, dependencies and charges are separate.
Are all listed tools tested?
Each entry shows its evidence. A reviewed source doesn’t mean installation or task execution has been tested. Client compatibility follows publisher documentation unless separate test evidence is present.