> ## 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 Code to Terminal49

> Connect Claude Code to the Terminal49 MCP server from your terminal with OAuth — no API key required.

Connect Claude Code to the Terminal49 MCP server so it can answer questions with live container and shipment tracking data while you work in your terminal.

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

<Tip>
  Using claude.ai or Claude Desktop instead? See the [Claude guide](/docs/mcp/setup/claude).
</Tip>

## Add the server

<Steps>
  <Step title="Add the server from your terminal">
    ```bash theme={null}
    claude mcp add --transport http terminal49 https://mcp.terminal49.com
    ```
  </Step>

  <Step title="Sign in to Terminal49">
    Inside a Claude Code session, run `/mcp`, select **terminal49**, and choose **Authenticate**. Your browser opens the Terminal49 sign-in page; after you log in and approve access, the server shows as connected.
  </Step>

  <Step title="Use it in a session">
    Ask Claude Code:

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

## Alternative: install the Terminal49 plugin

Instead of adding the MCP server directly, you can install the **Terminal49** plugin, which configures the same MCP connection and adds a `container-tracking` skill that teaches Claude Code how to choose and sequence the Terminal49 tools. See the [Agent plugins guide](/docs/mcp/setup/agent-plugins) for install commands and details.

## Test your connection

Ask Claude Code:

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

It 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                                                                                    |
| ----------------------------------- | --------------------------------------------------------------------------------------------- |
| Server missing from `/mcp`          | Confirm it was added with `claude mcp list`; re-run the `claude mcp add` command if needed    |
| `claude mcp add` fails              | Confirm the URL is exactly `https://mcp.terminal49.com` (no path) and the transport is `http` |
| Sign-in window never opens          | Pop-up blocked or no default browser — allow pop-ups and retry **Authenticate** from `/mcp`   |
| `401 Unauthorized` after connecting | Run `/mcp`, select **terminal49**, and re-authenticate to refresh the OAuth token             |

## Related guides

* [Claude](/docs/mcp/setup/claude) – claude.ai and Claude Desktop connectors
* [Agent plugins](/docs/mcp/setup/agent-plugins) – Terminal49 plugin with the `container-tracking` skill
* [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