# Remote MCP integrations

If you add a new custom integration and define the `Remote MCP URL`, an MCP integration will be created.\
\
Next choose the right **API authentication configuration** - by default this is set as `OAUTH2`. You only need to change this if the remote MCP has api token auth or no auth. \
\
\## MCP Tool Discovery\
\
Tool discovery is based on the auth type and will be visible in the **MCP Tools** tab.\
\
`NONE` - if no authentication is required, the tools will be discovered once the authentication configuration is saved.\
\
`API_TOKEN` - tools will also be discovered upon saving the api key.

`OAUTH2` - since tool discovery requires OAuth authentication, then the discovered tools will only become visible once the first authentication has been successfully completed, either by pre-authing a user under **Integration Users** or by starting a run and finishing the OAuth consent flow.\
\
NB! For token refreshing to work, the correct token url must be configured under **API authentication configuration.** The default will be the same host that is used for the authorization flow with `/token` appended. But this can vary based on the MCP provider.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.toolregistry.ai/basics/integrations/remote-mcp-integrations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.