mcp-server-tripit

mcp-server-tripit exposes the TripIt API as an MCP server.

It is built on top of the tripit-cli project and uses the published tripit package to access the full TripIt API.

Deploy this server directly to MCP Nest

Install

Run it directly with:

npx -y mcp-server-tripit

Related MCP server: mcp-travelcode

Usage with Claude

Add it to your MCP configuration:

{
  "mcpServers": {
    "tripit": {
      "command": "npx",
      "args": ["-y", "mcp-server-tripit"],
      "env": {
        "TRIPIT_USERNAME": "your-tripit-username",
        "TRIPIT_PASSWORD": "your-tripit-password"
      }
    }
  }
}

If you want to supply the optional client id too:

{
  "mcpServers": {
    "tripit": {
      "command": "npx",
      "args": ["-y", "mcp-server-tripit"],
      "env": {
        "TRIPIT_USERNAME": "your-tripit-username",
        "TRIPIT_PASSWORD": "your-tripit-password",
        "TRIPIT_CLIENT_ID": "your-tripit-client-id"
      }
    }
  }
}

Configuration

The server reads TripIt credentials from environment variables:

Required:

• TRIPIT_USERNAME

• TRIPIT_PASSWORD

Optional:

• TRIPIT_CLIENT_ID

If TRIPIT_CLIENT_ID is set, it is passed through to the tripit client. If it is omitted, the server does not pass it.

If you use fnox, you can also run it like this:

fnox x -- npx -y mcp-server-tripit

What it can do

Built on top of dvcrn/tripit-cli, this MCP server exposes the TripIt API for common travel workflows, including:

• listing and fetching trips

• creating, updating, and deleting trips

• managing hotel reservations

• managing flights

• managing transport segments

• managing activities

• attaching and removing documents from supported TripIt objects