# Claude Desktop & claude.ai

Add AutoUncle Data Services to Claude as a custom connector. A connector added on claude.ai is also available in Claude Desktop for the same account.

## Prerequisites

- A Claude plan that allows custom connectors. Free plans can add one.
- A verified AutoUncle account that is a member of the workspace you want to use.
- On Team and Enterprise plans, an organization Owner adds the connector first.

## Connect with OAuth (recommended)

**Pro, Max and Free plans:**

1. Open **Customize → Connectors** and choose **Add custom connector**.
2. Enter the URL `https://data-services.autouncle.com/mcp`.
3. For authentication, choose to sign in. For the OAuth client, choose **Register automatically**. AutoUncle supports dynamic client registration; it does not publish a client ID metadata document, so "Claude's published identity" falls back to the same automatic registration.
4. Sign in with your AutoUncle account, choose the organization and approve the scopes.

**Team and Enterprise plans:** an Owner adds the connector under **Organization settings → Connectors → Add → Custom → Web** with the same URL. Each member then chooses **Connect** and signs in as themselves.

OAuth valuations are **live** and use the chosen organization's credits. Claude requests the scope the server advertises in its `401` response; approve only the scopes you want the connector to have.

Authentication settings cannot be edited after the connector is created. To change them, remove the connector and add it again.

## Connect with an API key (limited beta)

Claude offers request headers for connectors as a beta for a limited set of organizations. If your organization has it:

1. Add the custom connector with the URL above and choose **No sign-in**.
2. Under **Request headers**, add a header named `authorization` with the value `Bearer au_test_...`. Claude adds no prefix, so include `Bearer `.

You cannot set an `Authorization` header on a connector that also uses OAuth. If request headers are not available to you, use OAuth, or use [Claude Code](/docs/mcp/claude-code), which supports API key headers.

## Claude Desktop configuration file

Claude's documentation routes remote servers through **Connectors** and describes `claude_desktop_config.json` as the mechanism for local servers. If you must use the file, run a local bridge such as `mcp-remote`; see [other MCP clients](/docs/mcp/other-clients#mcp-remote-for-stdio-only-clients).

## Verify the connection

Start a new chat, make sure the connector is enabled for it, and ask:

> Use AutoUncle Data Services to call get_account. Which organization is connected, what is the key mode, and how many credits are left?

Then ask for a valuation and check that Claude reports the price basis, currency, interval and precision grade.

## Troubleshooting

| Symptom | Fix |
| --- | --- |
| Sign-in loops or fails | Make sure your AutoUncle email is verified and that you are a member of the organization you choose. |
| "Wrong resource" or token rejected | The URL must be exactly `https://data-services.autouncle.com/mcp`. Remove and re-add the connector. |
| Valuations use credits | OAuth is always live. Use an API key header with a test key (if available to you) or Claude Code to test for free. |
| `insufficient_scope` | Reconnect and approve the missing scope. |

## Next steps

- [Agent prompts & examples](/docs/mcp/examples)
- [Safety & spend control](/docs/mcp/safety)

Sources: [Claude remote MCP connectors](https://claude.com/docs/connectors/custom/remote-mcp), [Claude connector authentication](https://claude.com/docs/connectors/building/authentication).