Model Context Protocol

One RevHost connection for your AI assistant

Use the RevHost plugin in ChatGPT or connect the same secure MCP server to Claude, Gemini, Muse, and other compatible clients.

Setup guide Or generate a PAT

Up and running in 2 steps

Choose your AI client, connect RevHost, then approve only the permissions you want to share.

Choose your AI client

Install the RevHost plugin in ChatGPT, or add https://api.revhosthq.com/mcp to Claude, Gemini CLI, Muse, or another MCP client. See the setup guide for each platform.

Approve & start chatting

You'll be redirected to RevHostHQ to log in and choose which permissions to grant. Once approved, your AI assistant can manage your fleet immediately.

Using Muse, Cursor, Windsurf, or another client that doesn't support OAuth? Generate a Personal Access Token instead — there is no redirect to approve.

Connection Details

This is the canonical configuration for people and AI assistants helping someone connect RevHostHQ.

Server URL: https://api.revhosthq.com/mcp
Transport: Streamable HTTP
Recommended authentication: OAuth 2.1 with PKCE and automatic discovery
Manual authentication: RevHost Personal Access Token in the Authorization bearer header

If You Are an AI Assistant

Ask which client the user wants to connect: ChatGPT, Claude, Gemini, Muse, or another MCP client.
Use the platform-specific instructions below. Prefer OAuth whenever the client supports it.
Explain requested permissions in plain language and let the user choose what to approve.
Never ask the user to paste a RevHost password or Personal Access Token into the conversation. Send them to https://www.revhosthq.com/profile#api-tokens to generate one and paste it into their client's own settings.
After connection, suggest a read-only first question such as “What reservations do I have tomorrow?”

ChatGPT uses the RevHost plugin. Claude and Gemini connect to the same endpoint as a remote MCP server. Muse and other clients without OAuth use the same endpoint with a Personal Access Token.

Setup guide

The RevHostHQ MCP server uses Streamable HTTP transport and supports both OAuth 2.1 (for clients that handle authentication automatically) and Personal Access Tokens (for manual configuration).

Creating a Personal Access Token

Free on every plan

Clients that do not handle OAuth themselves — Muse, Cursor, or anything you wire up by hand — authenticate with a token you generate once and paste into their settings.

Sign in to RevHost and open Profile → API Tokens — https://www.revhosthq.com/profile#api-tokens.
Under Token name, name it after the client it is for — “Muse”, “Claude Desktop” — so you can revoke the right one later.
Set Expires in to how long it should last, between 1 and 365 days.
Tick the Scopes that client actually needs. The scopes on the token decide which tools it can see, so a read-only token gives you a read-only assistant.
Click Create token and copy the value, which starts with revh_pat_.
Paste it into your client as the bearer token, alongside the server URL https://api.revhosthq.com/mcp.

The token is shown once. RevHost stores only a hash of it, so it cannot be read back afterwards — if you lose it, revoke it and create another. Treat it like a password: anyone holding it acts as you, within its scopes. Revoking cuts that client off immediately.

ChatGPT

OAuth — no token needed

OpenAI calls distributable MCP integrations plugins. RevHost still runs on MCP underneath, and ChatGPT handles the OAuth login for you.

When the RevHost plugin is listed publicly, open the ChatGPT plugin directory and select RevHost.
Click Connect, then sign in to RevHost and approve access.
Select RevHost from ChatGPT's tools menu when you want it to work with your fleet.

Developer preview: until the public listing is approved, enable Developer mode in ChatGPT, create a plugin, and use https://api.revhosthq.com/mcp as its MCP server. See OpenAI's connection guide.

Claude

Claude Code

OAuth — no token needed

Claude Code handles the OAuth flow automatically when you add a remote MCP server:

Terminal

claude mcp add --transport http revhost https://api.revhosthq.com/mcp
# Then run /mcp in Claude Code and authenticate RevHost

Claude Code will open your browser to log in and approve access. No token needed.

Claude Desktop (claude.ai)

OAuth — no token needed

Claude uses Custom Connectors with OAuth — no config files or tokens to manage.

Open Claude → Settings → Connectors.
Click Add custom connector at the bottom.
Enter the URL: https://api.revhosthq.com/mcp
Claude will redirect you to RevHostHQ to log in and approve access.
Once approved, RevHostHQ tools appear in your conversations.

Claude API (MCP Connector)

Personal Access Token

Use the MCP Connector in the Messages API:

API request (mcp_servers)

{
  "mcp_servers": [{
    "type": "url",
    "url": "https://api.revhosthq.com/mcp",
    "name": "revhost",
    "authorization_token": "revh_pat_YOUR_TOKEN_HERE"
  }],
  "tools": [{
    "type": "mcp_toolset",
    "mcp_server_name": "revhost"
  }]
}

Gemini

Gemini CLI supports remote Streamable HTTP MCP servers and automatic OAuth discovery.

Terminal

gemini mcp add --transport http revhost https://api.revhosthq.com/mcp
# Then run /mcp auth revhost

Building with the Gemini API instead? Use the remote MCP URL with a RevHost Personal Access Token header. See Google's function-calling docs.

Muse

Personal Access Token

Meta's Muse connects to RevHost as a remote MCP server. It does not run the OAuth flow, so add the server with a Personal Access Token as its bearer token:

Transport: Streamable HTTP

URL: https://api.revhosthq.com/mcp

Auth header: Authorization: Bearer revh_pat_...

Give the token only the scopes you want Muse to have — it sees exactly the tools those scopes cover, and nothing else.

Cursor / Windsurf / Other MCP clients

Personal Access Token

Most MCP clients support Streamable HTTP. Create a Personal Access Token and use:

URL: https://api.revhosthq.com/mcp

Auth header: Authorization: Bearer revh_pat_...

Two ways to authenticate

OAuth 2.1Recommended

For clients that support it (ChatGPT, Claude, Gemini CLI). You log in and approve access once — the client handles tokens automatically. No setup required.

Personal Access TokenManual

For developer tools, IDE integrations, and API usage. Create a token with only the permissions you need, then paste it into your client settings.

What You Can Do

Ask in everyday language. RevHostHQ gives your assistant access only to the areas you approve.

Fleet

Review your vehicles, details, availability, and operating status.

Try asking

“Which vehicles are available next weekend?”
“Show me the details for the BMW X5.”

Reservations

Review Turo trips and manage private reservations from one conversation.

Try asking

“What pickups do I have tomorrow?”
“Create a private reservation for these dates.”

Money

Understand revenue, expenses, invoices, and the financial picture across your fleet.

Try asking

“Summarize this month’s fleet performance.”
“Log a $62 oil-change expense.”

Pricing

Review pricing calendars and update eligible non-Turo daily prices.

Try asking

“Show next week’s prices for the Mustang.”
“Set Friday’s private-rental price to $95.”

Guests

Look up guest profiles and the reservation context you need to help them.

Try asking

“Who is picking up the Camry today?”
“Show this guest’s reservation history.”

Tasks & reminders

Create, assign, review, and complete operational follow-ups.

Try asking

“What needs attention today?”
“Remind me to inspect the tires on Monday.”

Operating knowledge

Use your saved policies, instructions, locations, and vehicle notes when answering questions.

Try asking

“What are my airport delivery instructions?”
“How do I handle a late return?”

Connected vehicles

Review location and telematics data or send supported commands to eligible vehicles.

Try asking

“Where is the vehicle assigned to this trip?”
“Show recent alerts for my connected cars.”

You Choose What Your Assistant Can Access

RevHostHQ separates viewing information from changing it. Review the permission screen during connection and approve only what you need.

View fleet information

Vehicles, reservations, guests, pricing, finances, reminders, and connected-car data.

Manage operations

Eligible private reservations, expenses, prices, reminders, tasks, aliases, and knowledge.

Use sensitive vehicle controls

Location and supported commands are separate permissions and remain limited to eligible vehicles.

Keep Turo data protected

Turo-synced vehicles, reservations, and guests keep their platform-specific write protections.

Using a client that requires manual authentication? Create a limited Personal Access Token and keep it private.

Security

•OAuth 2.1 with PKCE— authorization codes are single-use, access tokens expire in 1 hour, and refresh tokens are rotated on every use.
•Granular consent— you choose exactly which permissions to grant during the OAuth flow. Leave out anything you don't need.
•Tokens are hashed (SHA-256) at rest — RevHostHQ never stores the plaintext.
•Each token is rate-limited to 120 requests per minute.
•All MCP requests are logged in the audit log.
•Turo-synced records keep their platform-specific protections, regardless of the permissions you approve.

Ready to connect your AI assistant?

Choose ChatGPT, Claude, Gemini, or another MCP client and approve access securely.

Get started Create free account