Skip to main content
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. 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”.
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.
To connect the control plane, see 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.
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.

​
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 is generated from the schemas the server actually registers, so a tool that is not there does not exist.
  • The error reference is generated from the error code union, so a code that is not there cannot reach you.
  • The API overview 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.

​
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.
  • 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.
  • 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.
  • 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.