> ## Documentation Index
> Fetch the complete documentation index at: https://terminal49.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Claude to Terminal49

> Connect claude.ai or Claude Desktop to the Terminal49 MCP server with OAuth — no API key required.

Connect Claude to the Terminal49 MCP server so it can answer questions with live container and shipment tracking data.

<Note>
  **No API key required.** The Terminal49 MCP server supports OAuth 2.1. When you connect, Claude opens a browser sign-in page — log in with your Terminal49 credentials and you're done.
</Note>

<Tip>
  Using Claude Code? See the [Claude Code guide](/docs/mcp/setup/claude-code) — it's one command from your terminal.
</Tip>

## claude.ai and Claude Desktop

Custom connectors are managed in the same place on claude.ai (web) and in the Claude Desktop app.

<Steps>
  <Step title="Open connector settings">
    In Claude, go to **Settings → Connectors**. On claude.ai you can also [open the Add custom connector dialog directly](https://claude.ai/new?modal=add-custom-connector#settings/customize-connectors) and skip the next click.
  </Step>

  <Step title="Add the Terminal49 connector">
    Click **Add custom connector**, then enter:

    | Field | Value                        |
    | ----- | ---------------------------- |
    | Name  | `Terminal49`                 |
    | URL   | `https://mcp.terminal49.com` |

    Leave the advanced OAuth fields (Client ID / Client Secret) empty — Claude registers itself automatically.
  </Step>

  <Step title="Sign in to Terminal49">
    Click **Connect**. A browser window opens with the Terminal49 sign-in page. Log in with your Terminal49 account and approve access.
  </Step>

  <Step title="Enable the connector in a chat">
    In a new chat, open the tools menu and make sure **Terminal49** is enabled. Then ask:

    > "Using Terminal49, search for container CAIU1234567 and summarize its status."
  </Step>
</Steps>

<Note>
  Custom connectors are available on Claude Free, Pro, Max, Team, and Enterprise plans (Free is limited to one custom connector). On Team and Enterprise plans, an organization Owner must add the connector first under **Organization Settings → Connectors**; each member then connects their own Terminal49 account.
</Note>

## Test your connection

Ask Claude:

> "List the tools available in the Terminal49 MCP server and what they're for."

Claude should list tools such as `search_container`, `track_container`, and `get_container`. See the [tools reference](/docs/mcp/home#tools-reference) for the full list, and [Test Numbers](/docs/api-docs/useful-info/test-numbers) for containers you can use during development.

## Troubleshooting

| Symptom                             | How to fix                                                                                            |
| ----------------------------------- | ----------------------------------------------------------------------------------------------------- |
| Connector fails to add              | Confirm the URL is exactly `https://mcp.terminal49.com` (no path)                                     |
| Sign-in window never opens          | Pop-up blocked — allow pop-ups for claude.ai and retry                                                |
| `401 Unauthorized` after connecting | Disconnect and reconnect the connector to refresh the OAuth token                                     |
| Connector not selectable in chat    | Enable it in the chat's tools menu; on Team/Enterprise ask an Owner to enable it for the organization |

## Related guides

* [Claude Code](/docs/mcp/setup/claude-code) – Add the server from your terminal
* [MCP Overview](/docs/mcp/home) – Tools, prompts, and resources reference
* [MCP Server Quickstart](/docs/api-docs/in-depth-guides/mcp) – Full setup, including API-key and local stdio options
* [Other MCP clients](/docs/mcp/setup/other-clients) – Generic configuration for any client