> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useagents.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Learn what the UseAgents MCP server exposes and how agents should use the tools it provides.

The UseAgents MCP server exposes tools that let AI agents query the UseAgents registry directly. Use it when your agent needs grounded tool discovery instead of recalled package names or guessed integrations.

## Server URL

All MCP tools are available at:

```text theme={null}
https://mcp.useagents.site/mcp
```

<Note>
  The UseAgents MCP server is **currently free** during our public beta. No API key is required. See [Authentication](/mcp/tools-reference/authentication) for details.
</Note>

## Response format

MCP tools return data in **Toon** (Token-Oriented Object Notation), a compact, token-efficient format designed for LLM consumption. Toon uses fewer tokens than JSON while remaining human-readable. Learn more at [toonformat.dev](https://toonformat.dev).

## What the tools do

UseAgents MCP tools help agents:

* Search for tools by natural-language problem statement
* Shortlist candidate tools with compact registry metadata
* Retrieve authoritative implementation context for a selected tool
* Recommend verified tools with less hallucination risk

## Current reference pages

* [`search_tools`](/mcp/tools-reference/search-tools) for natural-language registry search
* [`get_tool_context`](/mcp/tools-reference/get-tool-context) for authoritative install and usage guidance for a selected slug
* [Authentication](/mcp/tools-reference/authentication) for API key setup

## Recommended workflow

Use the MCP server in two steps:

1. Call [`search_tools`](/mcp/tools-reference/search-tools) to find candidate tools by task, framework, or capability.
2. Call [`get_tool_context`](/mcp/tools-reference/get-tool-context) with the selected slug before recommending installation steps, code, or usage patterns.

If `get_tool_context` has no result for a slug, treat the tool context as unavailable instead of guessing from training data.

## Next steps

* [Authentication](/mcp/tools-reference/authentication) to configure the server
* [search\_tools](/mcp/tools-reference/search-tools) to query the registry
* [get\_tool\_context](/mcp/tools-reference/get-tool-context) to fetch tool-specific setup guidance