Help and Instructional Videos / API & AI assistants
API & AI assistants
Use an API token to read and edit schedules and altar servers from your own software or an AI assistant.
Planners can use a personal API token to read and edit their congregation's data from their own software or an AI assistant. This feature is available with Premium, Sponsor and active demo contracts. A token can do exactly what the planner who created it can do.
Create a token
As a planner, open More → API access in the app or the API access item in the web interface menu; both lead to the same token management. Give the token a recognizable name, choose Read or Write, and set an expiry date. A write token can also read. Copy the token to a secure password manager immediately: its full value is shown only once. Other planners in your congregation can see and revoke the token, but cannot read its secret. An expired or revoked token no longer works.
Call the API
The OpenAPI document lists the endpoints available to tokens. Signed-in planners can also use the Swagger view. For example, list schedules:
curl -H "Authorization: Bearer $MESSDIENERPLAN_API_TOKEN" \
https://messdiener-plan.de/api/v1/schedules
JSON responses contain a data field; PDF and CSV exports return files. GET requires at least a read token; POST, PUT and DELETE require a write token. A 401 response means the token is invalid or expired, 403 means insufficient permissions or an unavailable contract. Never put the token in public source code.
Connect an AI assistant (MCP)
Messdiener-Plan comes with its own MCP server. MCP (Model Context Protocol) is an open standard that lets AI assistants such as Claude Code or Cursor use tools. Connect your assistant to this address:
https://messdiener-plan.de/api/v1/mcp
It authenticates with the same API token, sent as the header Authorization: Bearer <your token>. Create a separate token for each assistant so that you can revoke its access independently. A read token is enough if the assistant only needs to answer questions.
Claude Code
In the terminal:
claude mcp add --transport http messdienerplan https://messdiener-plan.de/api/v1/mcp \
--header "Authorization: Bearer YOUR_TOKEN"
Claude Code stores the token in its configuration on your computer. To share the server in a project without sharing the token, create a .mcp.json file and read the token from an environment variable:
{
"mcpServers": {
"messdienerplan": {
"type": "http",
"url": "https://messdiener-plan.de/api/v1/mcp",
"headers": {
"Authorization": "Bearer ${MESSDIENERPLAN_API_TOKEN}"
}
}
}
}
Run claude mcp list, or /mcp in the chat, to check the connection.
Cursor
Add the server to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):
{
"mcpServers": {
"messdienerplan": {
"url": "https://messdiener-plan.de/api/v1/mcp",
"headers": {
"Authorization": "Bearer ${env:MESSDIENERPLAN_API_TOKEN}"
}
}
}
}
Set the environment variable MESSDIENERPLAN_API_TOKEN before starting Cursor. Do not write the token directly into a file that is shared with others or committed to a repository.
What the assistant can do
Read: list and show schedules, get the PDF address of a schedule, search altar servers and list the regular service times. With a write token, also: create a schedule, generate masses for a schedule, assign servers automatically, add an altar server and record an absence. Write tools only run when the assistant explicitly confirms the step; ask it to show you what it is going to change first. All tools see only your congregation's data and never have more permissions than your account.
Other clients work the same way if they let you enter an MCP address over HTTP with a custom header. For claude.ai and ChatGPT in the browser you do not need a token, see the next section.
Connect Messdiener-Plan in claude.ai / ChatGPT
In claude.ai and ChatGPT you add Messdiener-Plan as a connector without any token; you sign in with your normal Messdiener-Plan account.
1. In claude.ai, open the settings under Connectors and choose Add custom connector. In ChatGPT, add your own MCP server in the settings under Apps or Connectors. Depending on the plan, developer mode must be switched on first or your organisation's admin must allow the connector. 2. Enter https://messdiener-plan.de/api/v1/mcp as the address and leave client ID and secret empty. 3. Click Connect. The Messdiener-Plan sign-in opens; sign in as usual (password, login link or Google). 4. The consent page shows which congregation is connected. The assistant has the same rights as you as a planner. Confirm with Allow.
Only planners with Premium, Sponsor or a running demo can connect; Basic and Free see a hint to change the package. The connection appears under More → API access as "AI connector", counts towards the 10 active tokens and can be revoked there at any time.
Data protection
Through the MCP server, personal data of your congregation reaches your AI provider's language model, including data about minors: names, assignments, absences and, where stored, contact details. Your congregation chooses the AI provider and, as the controller, is responsible for this transfer. Before connecting, check whether you have a data processing agreement with the provider, where it processes the data and whether it uses input for training. Give the assistant only as much access as it needs and revoke the token as soon as you no longer need it. Details are set out in our terms and our privacy policy.