> ## Documentation Index > Fetch the complete documentation index at: https://docs.slipity.com/llms.txt > Use this file to discover all available pages before exploring further. # AI Assistants > Let Claude and other AI assistants on your Mac read your library, build services and, if you allow it, run the show. Slipity Pro on the Mac can connect to an AI assistant on the same Mac, such as Claude Code, Claude Desktop, Cursor or any other app that supports MCP (the Model Context Protocol). Ask it to build Sunday's service from a sermon outline, write the slides for a new song, or check which songs are missing a CCLI number. It works with your real library while Slipity Pro is open. It's off until you turn it on, and you choose how far an assistant may go. > [!NOTE] > > AI assistants are on the Mac only. An iPhone or iPad can't host the connection. ## Turning it on 1. Open **Settings › Integrations** and find **AI Assistants**. 2. Choose an **Access** level: | Access | What an assistant can do | | - | - | | **Off** | Nothing. No assistant can reach Slipity Pro. | | **Read Only** | Search the library, read songs and services, and see what's on the screens. | | **Prepare Services** | Read, plus build services and songs: add, swap and remove songs, add Scripture, make a new song from lyrics, and rewrite a song's words. Nothing on the screens changes. | | **Full Control** | Prepare, plus run the show: slides, hot keys, clearing, blackout, countdowns, Looks, overlays, stage layouts and messages, audio playlists and macros. | 3. The first time, Slipity Pro asks permission. It explains what an assistant can read and where it may send it: to the company that runs its AI, such as Anthropic. Choose **Allow** to go on. 4. Connect your assistant, as below. Turn it back to **Off** at any time to disconnect every assistant at once. **Turn Off and Forget Permission** also takes back your permission, so Slipity Pro asks again before it's next turned on. > [!NOTE] > > Slipity Pro sends nothing to any AI company itself. The assistant you connect reads what you ask about, and sends it on under its own company's privacy policy. ## Connecting Claude Code Click **Copy Claude Code Command**, paste it into Terminal and press Return. Then start Claude Code and ask it about your library. ## Connecting Claude Desktop 1. In **Settings › Integrations › AI Assistants**, click **Install in Claude Desktop…**. 2. Claude Desktop opens and shows Slipity Pro as an extension. Click **Install**. That's all: Slipity Pro now appears among Claude's extensions, and Claude can use it in any conversation. If Slipity Pro isn't open when Claude needs it, the extension opens it in the background. If you make a new token later, the extension picks it up without being installed again. If Claude Desktop isn't on this Mac yet, the button shows the extension file, **Slipity Pro.mcpb**, in Finder. Open it once Claude Desktop is installed. > [!NOTE] > > Install the extension again if you move Slipity Pro to another folder, so Claude can find it to open it. ## ChatGPT ChatGPT can't connect yet. Its connectors only reach MCP servers on the internet, and Slipity Pro's stays on your Mac, where only you can reach it. Claude Desktop, Claude Code, Cursor and other apps that run on your Mac can connect. ## Other assistants Any assistant that supports MCP over HTTP can connect to the address shown under **Status** (normally `http://127.0.0.1:47100/mcp`), sending the token from Claude Code's command as an `Authorization: Bearer` header. ## What it can do | Tool | Access | | - | - | | Search the library, read a song or presentation, list services, see what's in a service, see what's on the screens, list countdowns, Looks, overlays, stage layouts, audio playlists and macros | Read Only | | New service, open a service, add, swap or remove a song, add Scripture, make a new song from lyrics, change a song's words | Prepare Services | | Next and previous slide, go to a hot key, clear, blackout, hide or show slides, start and stop a countdown, make a Look live, show an overlay or stage layout, send and clear a stage message, play and stop audio, run a macro | Full Control | Lyrics are written the way the [Flow editor](https://docs.slipity.com/building/songs.md) reads them: a heading line such as *Verse 1* or *Chorus* starts a group, and an empty line ends a slide. ## With Planning Center's MCP Planning Center has an MCP server of its own, which lets an assistant read your church's Planning Center account (Services, People, Check-Ins, Giving and more), with the same permissions you have there. Connect both to the same assistant and it can read what's planned in Planning Center and build it in Slipity Pro, in one conversation. **Connecting both:** * **Claude Desktop:** add Planning Center from Claude's connector directory, and install Slipity Pro as below. * **Claude Code:** run Slipity Pro's command from Settings, then add Planning Center's: ```bash theme={null} claude mcp add --transport http planning-center https://mcp.planningcenteronline.com/mcp ``` The first time it's used, Planning Center asks you to sign in and choose which products the assistant may read. See Planning Center's guide, [Connect AI tools to Planning Center](https://help.planningcenter.com/en/151880-connect-ai-tools-to-planning-center.html). **Things to ask:** | Ask | What happens | | - | - | | "Which songs in Sunday's plan aren't in Slipity Pro yet?" | Reads the plan in Planning Center and searches Slipity Pro's library for each song. | | "Make the songs that are missing, from the lyrics in Planning Center." | Makes each missing song in Slipity Pro from its words, where Planning Center has them. Needs **Prepare Services**. | | "Do the CCLI numbers in Sunday's plan match the songs in Slipity Pro?" | Compares the two, so your CCLI reporting is right. | | "Build Sunday's service in Slipity Pro from the plan, with the Scripture reading the plan lists." | Adds the songs and the passage to the service in order. Needs **Prepare Services**. | | "Who's leading worship on Sunday, and which songs has our church sung most in the last three months?" | Answered from Planning Center; Slipity Pro isn't needed for this one. | > [!TIP] > > To bring a whole plan in and keep it in step with Planning Center as it changes, use Slipity Pro's own Planning Center link in **Settings › Integrations**: it imports the plan in one go and keeps both in step. Use the two MCP servers together for questions, cross-checks and filling the gaps. Planning Center's MCP server only reads Services, so an assistant can't change your plan in Planning Center this way. Changes are made in Slipity Pro. ## Staying in control * **Only this Mac.** The connection listens on this Mac alone, never the network, and refuses web pages. Every request needs the token. * **New Token** makes a fresh token. Assistants set up with Claude Code's command must be connected again; Claude Desktop picks it up by itself. * **Undo.** A song or service an assistant changed can be undone with **Edit › Undo** in Slipity Pro. * **Activity.** Click **Activity…** to see everything assistants have done since Slipity Pro opened, and what each call said back. * **On the screens.** With Full Control, each change an assistant makes to the screens shows a notice in the window, with a button back to these settings. > [!WARNING] > > With **Full Control**, an assistant can change what the room sees. Use **Prepare Services** for planning, and turn Full Control on only when you mean an assistant to run part of the show. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.