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

# Build with Sure

> Your calendar, your frontend, your way of organizing time.

Sure provides calendar building blocks for people, companies, and their agents.
Automate what you want to automate. Control what you want to control.

Start with a simple booking page. Change its copy, availability, or questions
through MCP. Give your coding agent a normal Git remote to reshape the entire
frontend. Preview your work, then publish when you want it live.

These initial public contracts describe shipped behavior, reviewed September 28,
2026\. Account access currently requires an invitation.

## Start small

Follow the [quickstart](/quickstart) to connect an agent and publish one change.
The owner creates a page and project token inside Sure; the agent uses that token
to work on that one page.

| You want to… | Use |
| - | - |
| Read private calendars, review source edits, or define labels | [Calendar MCP](/calendar) |
| Edit copy, colors, availability, or intake questions | [Project MCP and configuration](/configuration) |
| Build an entirely different frontend | [Sure-hosted Git and source files](/projects#hosted-git) |
| Preview, commit, publish, or roll back | [Project MCP](/projects) |
| Find a time, book, reschedule, or cancel | [Public booking RPC](/booking) |

Project MCP and Git edit the same project source. A Git push updates the draft. Publishing
is a separate action; the normal Sure Publish button commits a changed draft for
you.

## Choose the right access

**The owner's calendar agent** uses a calendar access token with
`https://mcp.sure.day/mcp`. It can read that owner's connected sources. Applying
event changes needs both an editable agent grant and separate source-management
permission. [Connect a calendar agent](/calendar).

**The owner's frontend agent** uses a project token with
`https://app.sure.day/project-mcp` or that project’s Git remote. It can read and
edit source, change scheduling policy, and publish. Keep the token in the agent’s
secret configuration, never in public frontend code or a Git remote URL.

**The booker or their agent** uses `https://app.sure.day/booking-rpc`. Reading
slots and creating a booking require no owner login. Changing an existing booking
requires its private management token. Availability does not expose event titles
or attendees.

Use the direction the owner or booker has given you. After a timeout, check the
current state and reuse the same idempotency key for the same booking request.
A pending operation is not a confirmed booking.

## Read these docs with an agent

* [Project MCP and Git reference](/projects)
* [Calendar MCP and source edits](/calendar)
* [Frontend and scheduling configuration](/configuration)
* [Booking RPC reference](/booking)
* [Project MCP tool schemas](https://sure.day/docs/mcp-tools.json), generated from the implemented project catalog;
  authenticated `tools/list` is authoritative.
* [Agent index](https://sure.day/llms.txt) and
  [complete reference as text](https://sure.day/llms-full.txt).

Mintlify’s documentation search MCP, if enabled for this site, searches these
pages. It does not authorize either calendar or project operations. Calendar MCP
and project MCP use separate endpoints, tokens, and tool catalogs.

## What is available today

Projects host static HTML, CSS, and JavaScript with one scheduling offer per
project. Git accepts fast-forward updates to `main`. Public booking supports
creation, rescheduling, and cancellation of Sure-created Google Calendar bookings
after the owner selects a destination and grants booking write access.

External project MCP does not expose private calendar reads, account connections,
concierge conversations, memory, worker control, or voice. Private calendar reads
and supported source-event changes use the separate owner-authorized calendar MCP.
Concierge conversations, memory, workers, and voice remain inside Sure. Payments,
team routing, and webhooks are future possibilities, not current public contracts.