Planning Center MCP server
Planning Center in any MCP client, through Memtro: Planning Center does not publish this server. Memtro's Planning Center connector reads Planning Center through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Planning Center church management: people (name, status, membership) and their workflow cards, lists, workflows with card counts, service types and plans with who is scheduled to serve, calendar event instances, groups and check-in headcounts. Can add a note to a person, add a person, rename a person or change membership, add an email address, put a person on a workflow, move, assign, remove or restore a workflow card and add a note to it, and add a member to a group, each only when asked.
Reads
planningcenter_peoplePlanning Center People: find people by name or email, or read one person by id with their workflow cards (workflow, step, overdue, snoozed).planningcenter_listsPlanning Center People lists (saved searches): name, description, how many people match, status and when last refreshed.planningcenter_workflowsPlanning Center People workflows (follow-up processes such as first-time guests): name, steps, cards ready, overdue, unassigned and completed.planningcenter_service_plansPlanning Center Services: without service_type_id, the service types (e.g. Sunday Morning); with it, that type's plans (title, series, dates…planningcenter_plan_teamWho is scheduled to serve on a Planning Center Services plan: name, position, and status (C confirmed, U unconfirmed, D declined).planningcenter_calendar_eventsPlanning Center Calendar event instances in a window, earliest first: name, start, end, location, all-day, recurrence and whether cancelled.planningcenter_groupsPlanning Center Groups: name, schedule, member count (left out where members are confidential), visibility and whether archived.planningcenter_headcountsPlanning Center Check-Ins headcounts (attendance totals counted by hand) recorded in a window, with the attendance type and event time, and the total.
Acts, when you ask
These change something in Planning Center. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
planningcenter_create_noteAdd a note to a person's profile in Planning Center People, in a note category.planningcenter_create_personAdd a person to Planning Center People, with an optional email address.planningcenter_update_personChange a person's first name, last name, nickname or membership in Planning Center People.planningcenter_add_emailAdd an email address to a person in Planning Center People.planningcenter_add_to_workflowPut a person on a Planning Center People workflow (a card at its first step).planningcenter_workflow_card_actionAct on a person's workflow card in Planning Center People: promote (complete this step, move to the next), go_back (previous step), skip_step…planningcenter_assign_workflow_cardAssign a person's workflow card to someone in Planning Center People.planningcenter_add_workflow_card_noteAdd a note to a person's workflow card in Planning Center People, visible to whoever can see the workflow.planningcenter_add_group_memberAdd a person to a Planning Center group as a member.
Connect it
First connect Planning Center on Dashboard → Connections, then add Memtro to your client once. The Planning Center tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Planning Center connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › Who is serving on Sunday morning this week?
- › Which positions still need people for next Sunday?
- › How many first-time guest cards are overdue?
- › What was our headcount over the last month?
- › Put Maya Okafor on the first-time guests workflow
Questions
- Is this an official Planning Center MCP server?
- No. It is Memtro's MCP server with Memtro's Planning Center connector behind it: the connector reads Planning Center through its API with the credentials you connect on Dashboard → Connections, and Planning Center publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Planning Center?
- Only when you ask, and only what it has been granted: add a note to a person's profile (people subscribed to the note category may be told); add a person to Planning Center People; change a person's name, nickname or membership; add an email address to a person; put a person on a workflow (the assignee may be told); move a workflow card forward or back, skip a step, remove, restore or unsnooze it; assign a workflow card to someone (they may be told); add a note to a workflow card; add a person to a group as a member. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.