> 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/pre-requisites.md).

# Pre-requisites

The following requirements must be met before connecting to Nichefire MCP:

### 1. An MCP-compatible client

Nichefire MCP is a remote server that uses MCP over HTTPS through the Streamable HTTP transport. Your client must support remote MCP servers. Clients limited to local servers launched through standard input/output (`stdio`) cannot connect.

Clients known to work:

| Client                 | Notes                                                                     |
| ---------------------- | ------------------------------------------------------------------------- |
| **Claude.ai**          | Added as a custom connector from Settings.                                |
| **Claude Desktop**     | Added as a remote connector.                                              |
| **Claude Code**        | Added as a remote MCP server.                                             |
| **ChatGPT**            | Added as a custom connector.                                              |
| **Visual Studio Code** | Added as a remote MCP server.                                             |
| **Cursor**             | Added as a remote MCP server.                                             |
| **Custom Agents**      | Any MCP client library, or plain HTTP requests, against the MCP endpoint. |

The essential requirement is support for remote or HTTP-based MCP servers. Nichefire does not distribute a local server binary.

### 2. The MCP endpoint URL

Each connection requires the endpoint URL assigned to your environment by Nichefire. If you have not yet received an endpoint URL, see **Environments & Access**.

### 3. A way to authenticate

Nichefire MCP supports two authentication methods. Only one is required, and the appropriate option will primarily depend on the capabilities of your client.

| Method      | You need                                                                                                 | Best when                                                                                 |
| ----------- | -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
| **API key** | An API key issued to your organization, and a client that lets you set a custom request header.          | Scripts, custom agents, and any client where you want a fixed credential you control.     |
| **OAuth**   | A Nichefire user account. You sign in through your browser and approve access — no key to copy or store. | Clients that support OAuth connectors, where you would rather not handle a secret at all. |

Credentials are environment-specific. A credential issued for sandbox cannot be used to authenticate against production, and vice versa.

Full setup steps for both methods are in [Authentication](broken://pages/9136330ab479a7a9b4382d8c449cb6f452266934).

### 4. Access to the capabilities you intend to use

Your organization’s access level determines which capability families are available:

* **Firesearch**
* **Trend Insights**
* Both capability families

Your client automatically lists only the tools available to your organization. If an expected capability is not shown, this normally indicates that it is not included in your organization’s access rather than a configuration issue.

See [**Capabilities**](/overview/capabilities.md) for details about each capability family.

### 5. Network access

Nichefire MCP is accessed over standard HTTPS on port `443`. If your organization restricts outbound network traffic, allowlist the Nichefire MCP hostname assigned to your environment.

The relevant network requirements depend on the type of client:

* **Cloud clients**, such as Claude.ai and ChatGPT, connect from the provider’s infrastructure. Your organization’s local network policies therefore do not apply to these connections.
* **Desktop and self-hosted clients**, such as Claude Desktop, Claude Code, and custom agents, connect from your machine or server. These connections may be affected by corporate proxies, firewalls, or outbound traffic restrictions.

### Checklist

Before continuing to [**Authentication**](/quick-start/authentication.md), confirm that you have:

* [ ]  An AI client that supports remote MCP servers.
* [ ]  The MCP endpoint URL for the applicable environment.
* [ ]  A credential issued for that same environment: either an API key or a Nichefire account when using OAuth.
* [ ]  Confirmation of the capability families available to your organization.
* [ ] Outbound HTTPS access to the endpoint when connecting from a managed network.