> For the complete documentation index, see [llms.txt](https://developers.make.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.make.com/mcp-server/connect-using-api-key.md).

# Connect using API key

You can connect Make MCP server to clients using a connection URL with an API key.

### Obtain an API key

To obtain an API key:

1. In the top-right corner of your Make account, click your name.
2. Click **Profile**.
3. Navigate to the **API access** tab.
4. In **Tokens**, click **+ API token**, which opens a dialog.
5. Select your desired scopes, including the `mcp:use` scope if you want to make your scenarios available as tools.
6. In **Label**, name your API key.
7. Click **Add**.

You've now obtained an API key for your client. Include this key in the connection URL.

To complete the connection, refer to the Usage page of your MCP client. For example, [Usage with Cursor](/mcp-server/connect-using-api-key/usage-with-cursor.md).

{% hint style="danger" %}
An API key is a secret key. Treat it as sensitive information and share it only with trusted parties.
{% endhint %}

### Access control

To control which scenarios are available as tools through your API key, see [Scenarios as tools access control](/mcp-server/connect-using-api-key/scenarios-as-tools-access-control.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.make.com/mcp-server/connect-using-api-key.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.