# Use Marfa from Claude or ChatGPT (/use/claude-and-chatgpt)

Add your instance to your Claude or ChatGPT account as a custom connector, so you can find and save your items from a chat.



Claude and ChatGPT reach your instance from their own servers, not from your device, so **your instance needs a public `https` address**, which [Give your instance an address](/run/address) sets up. You add that address to your Claude or ChatGPT account, the chat signs in to your instance, and it reaches only what you approve.

Claude calls what you add a custom connector. That's Claude's word: it has nothing to do with a Marfa [connector](/use/connect-a-service), which brings in records from another service.

## Add it to Claude [#add-it-to-claude]

Any Claude plan can add a custom connector; on the Free plan, it's your only one. Because Claude connects from its own servers, the connector works in every Claude app, the phone apps included, once it's on your account.

On a Team or Enterprise plan, an owner of the organization adds it first, in **Organization settings** > **Connectors**. Each member then finds it, labeled **Custom**, in **Customize** > **Connectors** and selects **Connect**.

### Add the connector [#add-the-connector]

On claude.ai, open **Customize** > **Connectors**, select **+ Add**, then **Add custom connector**. Name it `Marfa`, enter your instance's address followed by `/mcp`, such as `https://marfa.example.com/mcp`, and select **Continue**. Claude shows the sign-in it found; keep it, select **Continue**, then **Add**.

### Approve it [#approve-it]

Select **Connect**. Your instance's approval page opens. Sign in as the owner if you aren't already, then choose **Full access**, or **Choose access** to give less, such as reading your files and nothing else, and select **Approve**.

### Try it [#try-it]

In a new chat, select **+** > **Connectors** and check that Marfa is on. Ask Claude what it can see in Marfa: it answers with the types and tags you approved.

## Add it to ChatGPT [#add-it-to-chatgpt]

ChatGPT connects custom MCP servers only on the Business, Enterprise and Edu plans, and only on chatgpt.com, not in its phone apps. On Business, an admin or owner of the workspace adds the server; on Enterprise and Edu, so can a member an admin has allowed to.

### Add the server [#add-the-server]

Open **Plugins**, select the plus button, then **Add custom MCP server**. Name it `Marfa`, enter your instance's address followed by `/mcp` under **Connection**, and choose OAuth for authentication. Read the warning, select **I understand and want to continue**, then **Create as a plugin**.

### Approve it [#approve-it-1]

Your instance's approval page opens. Sign in as the owner if you aren't already, choose **Full access** or **Choose access**, and select **Approve**.

### Try it [#try-it-1]

Install the plugin, then in a new chat type `@`, select Marfa, and ask what it can see in Marfa.

## Save a file from a chat [#save-a-file-from-a-chat]

In ChatGPT, **attach a file and ask it to save the file to Marfa**. ChatGPT gives Marfa a link to the file, and your instance fetches it and keeps it as a file item, such as a `core.file.image` for a photo. The link works for a short time, so if the save fails, attach the file again.

In either chat, you can also ask it to save a file from a public web address, such as a PDF on a website. Your instance fetches only public addresses, and never follows a redirect. To stop agents from having your instance fetch files, turn the setting off:

```bash
marfa config set mcp_fetch_enabled false
```

## What the chat can do [#what-the-chat-can-do]

The chat reaches only the types you approved, and changes only those you let it change. **It asks before it deletes:** moving items to the bin first shows what would go, and the chat shows you before anything moves. Nothing it does deletes an item for good, exports your data or changes your instance's settings. [Work from an agent](/use/from-an-agent) has more to ask for.

## Disconnect it [#disconnect-it]

Removing the connector or plugin in the chat app stops the chat from calling your instance, but **the sign-in it holds still works until you end it** on your instance. List your sign-ins, find the chat by its name, and end its sign-in with the ID at the start of its line:

```bash
marfa sign-ins list
marfa sign-ins end <id>
```

Its next request is refused, and what it saved stays. [See and cut access](/use/see-and-cut-access) covers every sign-in and key.
