Skip to content

Developers

One address for every AI you work with

Q is built into Route Royal. Claude, ChatGPT, Codex and Cursor connect through our MCP server: add the address, sign in, and ask. Every call works in your organisation and is checked against your permissions.

The MCP server

https://api.routeroyal.com/api/v1/mcp
Connect your AIBook a demo

Q is built into Route Royal. Claude, ChatGPT, Codex and Cursor connect to Route Royal through its MCP server.

QBuilt in
MCP server
ClaudeSign in with OAuth
ChatGPTSign in with OAuth
CodexPlugin
CursorKey

Connect

Q is already here. The rest take a minute.

Q needs nothing connecting. For the others, add the address to the AI, sign in with your Route Royal account and choose the organisation. Route Royal is not in any AI’s app directory yet, so you add it yourself.

Q, built in

Built in

Q is Route Royal’s own AI, inside the product on every page. It knows the record you are looking at, reads and searches across your organisation, and prepares changes for you to approve.

  • The Ask Route Royal button on every page, AI Chat under Tools, and Ask Q on tasks.
  • Every change Q prepares waits for you to choose Do this now.
  • No address, no sign-in, no key: Q works as you, in the organisation you are in.
  1. 1

    Add the address

    Paste the MCP server’s address into your AI as a custom connector, an app or an MCP server, or install the Route Royal plugin.

  2. 2

    Sign in and choose

    Sign in with your Route Royal account and choose the organisation. The AI works there, with your role’s permissions and no more.

  3. 3

    Ask

    Ask about your deals, bookings, projects or posts in your own words. The AI picks the tools it needs and tells you what it did.

Where to add it

  • Claude
    Sign in with OAuth

    Settings, Connectors, Add custom connector, then paste the address and sign in. On Team and Enterprise plans an owner adds it once for everyone. In Claude Code, install the Route Royal plugin.

  • ChatGPT
    Sign in with OAuth

    Settings, Apps & Connectors, Advanced: turn on developer mode, then create an app with the address and OAuth sign-in.

  • Codex
    Plugin

    Add the Route Royal plugin from its marketplace, in the Codex app or the codex command line, and sign in when it asks.

  • Cursor
    Key

    Create a key on Route Royal’s integrations page, then add the address and the key to Cursor’s MCP settings.

Claude, ChatGPT and Codex register themselves when you sign in. These are the AIs Route Royal works with today.

With a key

A key, for clients that take one

Cursor, and any other MCP client that connects to a server over HTTP, uses a key made in Route Royal in place of signing in.

  • Make the key on the integrations page, or under Settings, Developer, MCP / AI access.
  • A key can read and search unless you give it more: choose the kinds of tool it may use.
  • Or name the tools it may use, one by one.
  • Keep the key in the client’s settings, never in a shared file or a repository.

Kinds of tool

  • READ
  • SEARCH
  • CREATE
  • UPDATE
  • DELETE
  • ACTION

A new key may use the first two.

mcp.json
{
  "mcpServers": {
    "routeroyal": {
      "url": "https://api.routeroyal.com/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer your key"
      }
    }
  }
}

What it reaches

Hundreds of tools across the platform

The server describes every tool to your AI: what it does, what it needs and whether it reads, changes or sends. These are a few of them, by the part of Route Royal they work in.

Reference data, as resources

Your deal stages, booking types and other lists your AI needs to get a call right are offered as MCP resources, so it can read them before it acts.

  • routeroyal://reference-data/deal-stages
  • routeroyal://reference-data/booking-types
  • routeroyal://reference-data/booking-statuses
  • routeroyal://reference-data/enquiry-channels
  • routeroyal://reference-data/task-priorities

Your permissions

An AI gets no more than you have

The server checks every call, whichever AI makes it.

  • Signed in with OAuth, the AI works in the organisation you chose, with your role’s permissions. What you cannot see or change, it cannot either.
  • An agency acts for a client only through an active service grant, and only with permissions both in the grant and in its own role.
  • Every tool says whether it reads, changes something or reaches outside Route Royal, so your AI can ask you before it acts.
  • A tool that changes something takes a key for the operation, so if an answer is lost and the AI tries again, the change is not made twice.
  • Requests are rate limited, and a connected AI is limited per minute and per session.
Next stopEvery integration

Questions

Questions about the MCP server

Does connecting an AI cost extra?

Connecting Claude, ChatGPT or Codex with your Route Royal sign-in needs nothing more from us than your plan. Your AI’s own subscription is between you and its maker. Q’s work counts towards your plan’s monthly AI allowance, on the pricing page.

Is Route Royal in Claude’s or ChatGPT’s directory?

Not yet. You add it yourself: in Claude as a custom connector, in ChatGPT as an app in developer mode, in Codex and Claude Code as a plugin, and in Cursor with a key.

Do I need developer access?

Not to sign in from Claude, ChatGPT or Codex: any member of an organisation can, with their own permissions. Keys under Settings, Developer are part of developer access, which we switch on per organisation.

Can I connect another MCP client?

A client that connects to a remote MCP server over HTTP can use a key made in Route Royal, with the address and the key in its settings. Claude, ChatGPT, Codex and Cursor are the ones we support today.

Can I keep an AI to reading?

Yes. A key reads and searches unless you choose more. Signed in with OAuth, the AI has your role’s permissions, so a member whose role only reads connects an AI that only reads.

Where are the tools documented?

The server describes every tool to your AI as it connects: its name, what it does, what it needs and whether it reads or changes. There is no public reference to read separately.

Are there limits?

Yes. Requests are rate limited, by the kind of tool, per minute and per session. If a limit is reached, the AI is told when to try again.

How is Q different?

Q is built into Route Royal, so it needs no connecting. It reads and searches as you, and every change it prepares waits for you to choose Do this now. Some work, such as campaigns, websites and orders, is reached over MCP only.

Your first session

Ask your AI about your business

Copy the address, add it to the AI you already use and sign in. Q is waiting inside Route Royal already.

The MCP server

https://api.routeroyal.com/api/v1/mcp
Book a demoStart a free trial

YouWhat did we publish last month?

  1. Built in: nothing to connect

  2. tools/call search_posts

    Four posts last month, and two drafts waiting for review.

Answered by Route Royal