---
title: Twelve Month Calendar agent instructions
description: When and how an authorized agent should use the calendar MCP and REST interfaces.
canonical: https://twelvemonthcalendar.com/agents.md
last-updated: 2026-09-01
---

# Twelve Month Calendar agent instructions

Twelve Month Calendar is a private, user-owned calendar for seeing and changing a whole year of events. Calendar data is never available through public pages.

## When to use this

Use this service when a user asks you to understand or change their Twelve Month Calendar, summarize the shape of a year, filter travel or time off by person, compare family or work plans, or find potential conflicts. Do not use it for a calendar the user has not authorized.

## Supported interfaces

- Prefer the remote MCP server at `https://mcp.twelvemonthcalendar.com/mcp` when the client supports Streamable HTTP and MCP protocol `2025-11-25`.
- Use the public documentation MCP server at `https://mcp.twelvemonthcalendar.com/docs/mcp` to search integration guidance without sending credentials.
- Otherwise use the generated REST API at `https://api.twelvemonthcalendar.com/v1` and its OpenAPI 3.1 document at `https://api.twelvemonthcalendar.com/v1/openapi.json`.
- Read the complete integration context at `https://twelvemonthcalendar.com/llms-full.txt` and the reusable skill at `https://twelvemonthcalendar.com/skills/twelve-month-calendar/SKILL.md`.

Prefer OAuth for private MCP and REST operations. Follow the protected-resource metadata to the authorization server, use its advertised client-registration method, and complete Authorization Code with S256 PKCE through human browser consent. The public MCP handshake and tool catalog contain no calendar data. Personal access tokens are a fallback only for scripts or clients that cannot complete OAuth. Respect the granted scopes and resources.

## Safety rules

1. Search in a bounded date range and resolve exact resource IDs before changing or deleting anything.
2. Ask the user to disambiguate when more than one event could match. Never mutate from a fuzzy title match alone.
3. Supply a stable idempotency key for each intended mutation. Include the latest resource version for updates and deletes.
4. Preserve all-day inclusive end dates and timed exclusive end instants with explicit IANA time zones.
5. On a version conflict, re-read the resource and ask before overwriting a material change.
6. Never expose an access token, refresh token, PKCE verifier, or private calendar content in a public file, URL, log, or unrelated prompt.

Google Calendar import, transactional email delivery, webhooks, and a change feed are not supported in this release. Do not claim or attempt those capabilities.