# Build something worth remembering

HistoryShowcase gives your agent practical tools to organize recognition content, add photos, and choose polished designs—inside the same templates and editor you already use.

**One connection. One site. The same API powers MCP and direct integrations.**

## Start in minutes

1. Open your site in the [workspace](https://history-showcase.com/app) and select **Agents**.
2. Name the connection, choose permissions and an expiry, and copy its token.
3. Add the MCP endpoint to a compatible client, or use the API directly.
4. Ask your agent to inspect the site and suggest improvements.

Continue with [connection instructions](connect) or the [first-edit quickstart](quickstart).

## What your agent can do

| Task | Tools |
| --- | --- |
| Understand a site | `get_site_context`, `get_capabilities` |
| Find and read stories | `search_content`, `get_entry` |
| Add or organize content | `apply_changes` |
| Choose an existing design | `get_capabilities`, `apply_changes` |
| Reuse or upload photos | `list_media`, `upload_media` |
| Review the saved draft | `preview_site` |
| Publish and verify | `publish_changes`, `get_delivery_status` |
| Restore a previous release | `list_publications`, `restore_release` |

## Predictable by design

- **Your existing templates.** Supported layouts, typography and branding; no arbitrary code, CSS or custom schema.
- **Your current permissions.** Connection scopes can narrow your role, never expand it. Removing site access or disconnecting the token stops future access.
- **Drafts first.** Saving and publishing are separate. An agent can prepare a draft without being allowed to publish.
- **Small, recoverable changes.** Batches validate together and save atomically. Revision checks prevent silent overwrites.
- **Inspectable contracts.** The [OpenAPI specification](openapi.json) and MCP input schemas come from the runtime validators.

For agents: start with [skill.md](skill.md). The documentation index is [llms.txt](llms.txt).