> For the complete documentation index, see [llms.txt](https://docs.storylane.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storylane.io/mcp/storylane-mcp/connect-storylane-mcp.md).

# Connect Storylane MCP

Set up Claude, ChatGPT, Copilot, or a custom client with OAuth or client credentials.

**Jump ahead:**

* [Public LLM clients (Claude, ChatGPT, Copilot)](#id-1.-public-llm-clients-oauth-clients)
* [M2M authentication (Custom clients)](#id-2.-m2m-authentication-custom-clients-and-automations)
* [Troubleshooting](#troubleshooting-if-it-does-not-connect)

#### Which method do you need

**Most people want Public LLM clients.** If you are using Claude, ChatGPT, or Microsoft Copilot, sign in and approve. No keys, no configuration.

**Use M2M authentication** if you are connecting Cursor, n8n, or your own automation, and need server-to-server access without a user session.

Once you’re connected, see Workflows & Prompts for routines you can run on a schedule.

#### 1. Public LLM clients (OAuth clients)

For Claude, ChatGPT, and Microsoft Copilot. Uses OAuth — no API keys required.

{% tabs %}
{% tab title="Claude" %}

1. In Claude, open **Settings → Connectors**.
2. Select **Add custom connector**.
3. Paste the Storylane MCP server URL.
4. Sign in to Storylane and approve access.
5. In a conversation, select **+ → Connectors** and enable Storylane.
6. Open connector settings and set **Tool permissions** to **Always allow** — this lets workflows run end to end without stopping to ask for confirmation on every action.

{% hint style="info" %}
**For Personal Accounts:** "Add Custom Connector" is always available.

**For Company Accounts:** "Add Custom Connector" is only available for account admins. A non-admin member cannot add a Custom Connector in a Company Account.
{% endhint %}
{% endtab %}

{% tab title="ChatGPT" %}

1. For write actions, enable Developer Mode in **Workspace Settings → Permissions & Roles → Connected Data**.
2. Open **Settings → Apps & Connectors** and create a connector.
3. Set the name to `Storylane`.
4. Select OAuth authentication and add the Storylane MCP server URL.
5. Publish the connector, then authorize it from **Apps & Connectors**.

{% hint style="info" %}
**Free accounts:** Custom Connector is not available.

**Personal (paid) accounts and company accounts:** Custom Connector is available.
{% endhint %}

{% hint style="warning" %}
Write actions require Developer Mode. It is currently in beta for Business and Enterprise plans. Read-only tools work on all plans.
{% endhint %}
{% endtab %}

{% tab title="Microsoft Copilot" %}

1. In Microsoft Copilot Studio, open your agent and go to **Tools → Add tool → New tool**.
2. Select **Model Context Protocol**.
3. Paste the Storylane MCP server URL.
4. Under **Connection**, select **Create new connection**, then sign in to Storylane and approve access.
5. Save the tool, then publish or roll out the agent to yourself or your team.

{% hint style="info" %}
Unlike Claude or ChatGPT, Microsoft Copilot doesn't have a direct "Settings → Connectors" toggle — MCP servers are added through Copilot Studio and made available via an agent your org publishes or rolls out to users.
{% endhint %}
{% endtab %}
{% endtabs %}

#### 2. M2M authentication (Custom clients and automations)

For Cursor, n8n, custom automations, and any tool that connects via client credentials. Use M2M when you need server-to-server access without a user session.

Go to **Settings → Integrations → MCP** and click **Request credentials** to generate your `client_id` and `client_secret`. Credentials are unique to your account and workspace.

{% hint style="warning" %}
Store your `client_secret` securely — it is only shown once. If exposed, generate new credentials from **Settings → Integrations → MCP** and revoke the old ones.
{% endhint %}

**Cursor and similar platforms**

Add the following to your `mcp.json` file:

```json
{
  "mcpServers": {
    "storylane": {
      "name": "Storylane",
      "description": "Storylane MCP",
      "url": "https://mcp.storylane.io/mcp"
    }
  }
}
```

{% hint style="info" %}
M2M credentials are scoped to your account and workspace. `switch_workspace` and `list_workspaces` are not available to M2M clients for security reasons.
{% endhint %}

### Troubleshooting: If it does not connect

| Symptom                             | Likely cause                                              |
| ----------------------------------- | --------------------------------------------------------- |
| Connector added but no tools appear | Not enabled in the conversation                           |
| Sign-in loops or fails              | Signed into a different Storylane account in that browser |
| Read works, writing fails           | ChatGPT Developer Mode is off                             |
| Add custom connector is greyed out  | Company account, non-admin member                         |
| Tools appear but every call errors  | MCP not available on your plan                            |
| Workspace switching unavailable     | Expected on M2M credentials                               |


---

# 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://docs.storylane.io/mcp/storylane-mcp/connect-storylane-mcp.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.
