Bring theCam into your AI assistant.

01 · Overview

What theCam MCP does

The Model Context Protocol (MCP) is an open standard that lets AI assistants use outside tools. theCam's MCP server gives your assistant the same abilities you have in the app — finding pros, booking, chatting and getting support — without ever handing it your password.

Endpoint

https://api.thecam.app/user-mcp

Transport

Streamable HTTP. The server is stateless and accepts POST only.

Authorization

OAuth 2.1 with PKCE. Sign in with Google, Apple, or email and password, then approve the app.

Access

Your account only: public pro profiles plus your own bookings, favorites, chats and support requests.

Tools

21 tools — 12 read-only, 9 that make changes. No tool takes payment.

02 · Sign-in & consent

How authorization works

1. 1

   Add the endpoint to your AI app

   Use one of the setups below. The app contacts theCam, finds its sign-in server and registers itself automatically — there's no client ID or secret for you to copy.

2. 2

   Sign in on theCam's own page

   Your browser opens a theCam page. Continue with Google, continue with Apple, or use your email and password — whichever you use for theCam today. Your password is entered on theCam, never in the AI app.

3. 3

   Review the request and choose Allow

   The consent screen names the app and what it can do: act as you in theCam to search pros, read your profile, and manage your bookings, favorites, reviews, chats and support requests. Choose Deny and nothing is shared. Apps that registered themselves with an unverified name are flagged — only continue if you started the connection.

4. 4

   The app receives short-lived access

   The app gets an access token that lasts 15 minutes and a refresh token it uses to stay connected. Both are bound to your account and that one app. Every call is made as you, with your permissions.

03 · Connect a client

Connect your AI app

Every client uses the same endpoint. Pick yours below; each one opens theCam's sign-in page the first time it connects.

claude mcp add --transport http thecam https://api.thecam.app/user-mcp

https://api.thecam.app/user-mcp

codex mcp add thecam --url https://api.thecam.app/user-mcp
codex mcp login thecam

[mcp_servers.thecam]
url = "https://api.thecam.app/user-mcp"

https://api.thecam.app/user-mcp

{
  "mcpServers": {
    "thecam": {
      "url": "https://api.thecam.app/user-mcp"
    }
  }
}

{
  "servers": {
    "thecam": {
      "type": "http",
      "url": "https://api.thecam.app/user-mcp"
    }
  }
}

curl https://api.thecam.app/.well-known/oauth-protected-resource/user-mcp

npx -y mcp-remote https://api.thecam.app/user-mcp

04 · Tools

All 21 tools, by workflow

Read tools only look things up. Write tools change something in your account; each needs an idempotencyKey so a retry never books or messages twice, and clients that support confirmations ask you first.

05 · Security & privacy

Built to act as you — and only you

• No API keys, no shared passwords

  You sign in on theCam's page. The AI app never sees your password and there's no long-lived key to leak.

• Explicit consent, per app

  Each app must be approved by you on theCam's consent screen before it gets any access. Unverified app names are flagged.

• User-scoped by design

  Every tool runs as your account. It can read public pro profiles and your own bookings, favorites and conversations — never another user's data, and never admin operations.

• Short-lived, rotating tokens

  Access tokens last 15 minutes. Refresh tokens rotate on each use, and replaying an old one revokes the whole connection.

• Minimal data

  Search returns public profile fields only. Credentials and sign-in parameters are kept out of logs, and tokens are stored only as one-way digests.

• Safe retries

  Idempotency keys stop a retried request from booking or messaging twice. Errors come back as short, generic messages.

• You stay in control

  Disconnect any app from the app itself, or contact support to revoke every connection at once.