> For the complete documentation index, see [llms.txt](https://mcp-docs.nichefire.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mcp-docs.nichefire.com/quick-start/supported-integrations/custom-ai-agents.md).

# Custom AI Agents

If you are building a custom agent rather than using a consumer AI client, you can integrate Nichefire MCP as a standard remote MCP server. Once the connection is configured, the tools available to your organization will appear in the agent’s tool list.

### Setup

#### 1. Configure the endpoint

Add the complete Nichefire MCP endpoint to your MCP client configuration. Make sure the URL includes the full path, including `/mcp`, and matches the environment you intend to use.

See [Environments & Access](/overview/environments-and-access.md) for the appropriate endpoint.

#### 2. Configure authentication

Configure one of the supported authentication methods:

* **API key:** Send your key in the `x-api-key` request header. Use the complete key as the value, without a `Bearer` prefix.
* **OAuth 2.1:** Configure the client to complete the authorization flow supported by the Nichefire MCP server.

The authentication credentials must belong to the same environment as the configured endpoint. For example, a sandbox credential cannot be used with the production endpoint.

#### 3. Test the connection

Start the MCP client and confirm that:

* The server connection completes successfully.
* Authentication is accepted.
* The tools included in your organization’s entitlements appear in the agent’s tool list.

As an initial test, call [`get_usage`](/tools/get-usage.md). This confirms that the connection is working without consuming research quota.

If the connection succeeds but some tools are missing, review Capabilities or contact your Nichefire representative to confirm your organization’s entitlements.

### Good practices for agents

* **The search quota is shared across your whole organization.** Avoid redundant searches, and check [`get_usage`](/tools/get-usage.md) before issuing several in a row.<br>
* **Running multiple searches in parallel** (different angles on the same topic) can improve coverage but it also uses more of the quota.<br>
* **Search first, then analyze.** Use [`execute_search`](/tools/firesearch/execute-search.md) to identify relevant trends before calling [`analyze_trend`](/tools/firesearch/analyze-trends.md).\
  The [`analyze_trend`](/tools/firesearch/analyze-trends.md) tool is intended to examine a trend returned by a search. Pass the title and description from the search result rather than generating or inferring a trend independently.<br>
* **Use Saved Data Where Appropriate.** Trend Insights tools and [`get_usage`](/tools/get-usage.md) do not consume the search allowance. Agents can therefore explore the organization’s existing topics and trends without reducing the available research quota.<br>
* **Read-only Access.** All Nichefire MCP tools are read-only. They can retrieve and research information but cannot create, modify, or delete data within the Nichefire workspace.