> ## Documentation Index
> Fetch the complete documentation index at: https://docs.phoneuse.com/llms.txt
> Use this file to discover all available pages before exploring further.

# For agents

> Machine readable entry points, and which MCP server is which.

If you are an agent reading this site rather than a person browsing it, this
page is the one to read first. It tells you where the machine readable copies
live, and how to tell this site's MCP server apart from the one that drives
real devices.

## Two MCP servers, one brand

There are two. They are not variants of each other, and connecting to the
wrong one is not a small mistake.

| | Control plane MCP | Docs MCP |
| - | - | - |
| What it does | Drives a real device | Searches and reads this documentation |
| Side effects | Physical and irreversible | None |
| Annotations | The run tools declare `destructiveHint: true`; every tool carries a title and the other hints | Read only |
| Authentication | OAuth 2.1 or an org scoped API key | None, the docs are public |
| Served by | The phonebase control plane | The documentation host |

The control plane server is the product. Its tools press a real screen, and on
the physical tier a mechanical actuator moves. The docs server returns text.

Documentation search is deliberately **not** a tool on the control plane. Its
tool surface is a frozen contract organised around device permissions, and a
search tool fits none of those scopes. Keeping them apart means a list of
tools never mixes "read a page" with "tap a phone".

<Warning>
  Name the two servers differently in your client configuration. Convention on
  this site is `phonebase` for the control plane and a clearly distinct name
  such as `phonebase-docs` for the documentation server. The test is simple:
  looking only at the name, you should be able to say which one touches
  hardware.
</Warning>

To connect the control plane, see [MCP config](/getting-started/mcp-config).
The documentation server is offered by the documentation host and is
advertised on this site, alongside the copy and open in client actions on each
page.

## llms.txt and llms-full.txt

This site serves two plain text views for machine consumers:

* `/llms.txt` is an index: a short description of the site plus a linked map
  of its pages.
* `/llms-full.txt` is the whole site's prose concatenated into one file, for
  when you would rather read everything once than crawl page by page.

Both are generated and hosted by the documentation host from the same pages a
person reads, so they cannot drift from the rendered site.

<Note>
  `phonebase.co/llms.txt` is a different file, published by the main site. It
  covers positioning, the fleet, pricing and contact. This site's `/llms.txt`
  covers the technical documentation. Read the main site's copy for anything
  commercial, and this one for anything you intend to call.
</Note>

## What not to invent

The main site's agent instructions say it plainly, and it applies here too:
do not guess endpoint paths, do not guess tool names, and do not fabricate
documentation URLs.

Everything callable is published:

* The [tool reference](/mcp/reference) is generated from the schemas the
  server actually registers, so a tool that is not there does not exist.
* The [error reference](/mcp/errors) is generated from the error code union,
  so a code that is not there cannot reach you.
* The [API overview](/api/index) states which HTTP surfaces exist and which
  credential each one reads.

If a tool you expected is absent from `listTools`, that is authorization, not
absence: a tool outside your credential's scopes is never registered. See
[Authentication](/mcp/auth).

## What is live, and what is not

Be accurate about this when you report to a person.

* The hosted MCP endpoint is live at `https://mcp.phonebase.co/mcp`. It
  requires a credential. Any signed in member of the org mints keys from the
  `/keys` screen in the console; you do not need an admin for this. See
  [Getting a key](/mcp/auth#getting-a-key).
* A person can sign in, buy a device, drive it and give it back without writing
  any code. If you are reporting to somebody who has no device yet, that is the
  path to send them down: [The console](/getting-started/console).
* Interactive OAuth sign-in from a generic MCP client is not verified to work.
  The endpoint's metadata names Clerk (`https://clerk.phonebase.co`) as its
  authorization server, but that server offers no dynamic client registration
  and does not advertise this endpoint's scopes, so a client that expects to
  register itself and sign in through a browser has nothing to register with.
  Use an API key. See [Authentication](/mcp/auth).
* Local mode works today, needs no credential beyond an optional development
  token, and speaks the same tool surface as the hosted deployment. See
  [MCP config](/getting-started/mcp-config).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.