Skip to main content
Agents do not read your marketing site the way humans do. They pattern-match from training data, guess package names, and recommend tools they have never verified. UseAgents gives you a structured place to define your software so agents can find it, understand it, and recommend it correctly.

​
The problem

When an agent needs a tool, it often:
  • Invents package names that sound plausible but do not exist
  • Recommends outdated libraries or wrong SDKs for the stack
  • Links to docs that moved, repos that forked, or APIs that changed
  • Misses your tool entirely because it was never in the agent’s context
Prompt engineering alone cannot fix this. Agents need a searchable source of truth with accurate metadata, canonical links, and ownership signals.

​
What UseAgents does

UseAgents is a registry and MCP server for developer tools. You publish structured metadata about your CLI, SDK, library, or API. Agent builders connect the MCP server once, and their agents search the registry when they need a tool. You define:
  • What your tool does and who it is for
  • Canonical website, repository, and documentation links
  • Categories, languages, frameworks, and tags for discovery
  • Verification signals that prove your organization owns the listing
Agents get grounded search results instead of guesses.

​
Why publish your tool

Publishing is free during our public beta. You keep ownership of your tool and can update metadata anytime.

​
How the workflow fits together

1

Create a draft

Add your tool from the dashboard with a name, slug, and basic links. The tool starts as a draft — invisible to search until you publish.
2

Write agent-ready metadata

Fill in descriptions, categories, tags, and links that explain what your tool does and when to use it. See Editing Your Tool for field guidance.
3

Review changes

Compare your draft against the live version on the Changes page before deploying.
4

Publish

Deploy to make your tool searchable in the registry and available through the MCP server. See Publishing & Deployments.
5

Verify discovery

Search the registry or call search_tools through the MCP server to confirm agents can find your tool for relevant queries.

​
Design principles for good listings

  • Describe capability, not hype. Agents need to know what your tool does and which integrations it supports.
  • Use canonical links. Point to your real docs and repository, not landing pages that redirect elsewhere.
  • Tag for how people search. Categories, languages, frameworks, and tags should match how developers describe the problem your tool solves.
  • Keep metadata current. When APIs, packages, or docs change, update your listing so agents do not recommend stale paths.

​
Who this is for

  • SDK and library maintainers who want agents to recommend the right package
  • API and platform teams who need agents to link to current docs
  • CLI and developer tool authors who want discoverability beyond word of mouth
  • DevRel and growth teams who care about how AI assistants represent their product

​
Get started

Add Your Tool

Create a draft and fill in the metadata agents need.

Editing Your Tool

Field reference, validation rules, and best practices.

​
Next steps