Connect Claude to Slackalendar

Before you connect

Slackalendar uses a remote Model Context Protocol (MCP) connection. It works with compatible Claude web and desktop connector interfaces; an existing connector can also be used in supported Claude mobile clients. No local server, desktop computer control, Slack bot installation or shared API key is required. Your Claude account must offer custom remote connectors; menu names and availability can vary.

1. 01Sign in to Slackalendar with the account whose team access Claude should use. Company membership alone is not team access, and a dashboard-only invitation does not grant access to source-team tasks.
2. 02Open Settings → AI connections. Copy the Remote MCP endpoint shown there. For Slackalendar.com it is https://slackalendar.com/mcp, not the homepage or API resource.
3. 03If AI connections are not active, ask the Slackalendar system administrator to review service activation. Creating a Claude connector does not activate the service. If settings cannot load, use Retry rather than deleting an existing connection.

Add and authorize the Claude connector

1. 01In Claude, open Settings → Connectors. Choose the add/custom connector option, name it Slackalendar, and paste the Remote MCP endpoint. If Slackalendar already appears, select it and choose Connect instead of creating a duplicate.
2. 02Choose Connect and complete the Slackalendar authorization page in the browser. Sign in if prompted, then return to the authorization tab and choose Continue.
3. 03Select one company and the teams Claude may access. Choose an access duration from 1 to 90 days; the default is 30 days.
4. 04Leave task-status changes unchecked for read-only access. A client requesting that permission does not receive it unless you explicitly approve it.
5. 05Choose Allow access and let the browser return to Claude. A brief Access approved page provides a Continue button if automatic navigation does not finish. Slackalendar should appear connected and expose the tools available for your permission set. A read-only connection exposes five tools.
6. 06Start a Claude conversation and enable Slackalendar in that conversation's connector/tool controls if needed.

Check read-only access

Try: Use Slackalendar to list the teams I can access, then show up to five tasks from [your team name]. Do not change anything.

• list_teams lists approved teams that you can still access.
• get_team_workflow reads ordered team workflow statuses and available tags.
• list_tasks searches accessible tasks by title, description, tags and task metadata, with status and archive filters and paginated results.
• get_task reads an accessible task and its saved custom values.
• get_task_activity reads accessible task comments and history, with pagination.

Optional status changes and their limits

Read-only access is sufficient for questions and task summaries. To enable status changes later, review the existing grant in Settings → AI connections, revoke it if replacing its permissions, then reconnect from Claude and explicitly approve task-status changes. Reconnect any other affected clients after revoking a shared grant. Changing a prompt alone cannot upgrade permissions.

• The optional change_task_status tool changes a task's team-workflow status and checks its expected current status to prevent stale writes. It does not edit independent Project Dashboard statuses.
• Normal assignment defaults, automations, recurrence and notifications can run after a status change. Confirm the task and destination status before requesting a real change.
• Claude cannot create or delete tasks, edit descriptions or comments, change assignees or due dates, manage members, change billing, or perform administrator actions through this connection.

Review, disconnect and troubleshoot

1. 01In Slackalendar Settings → AI connections, review the connection's company, teams, permissions and expiry. Use Revoke to stop that grant's access. Do not assume hiding a tool in Claude revokes its server-side authorization.
2. 02If access expires or Claude asks to reconnect, start a fresh Connect flow and approve only the permissions you still need. Tokens can expire before the overall approval does; the client handles supported refresh or asks you to authorize again.
3. 03If Allow access stalls, close the old authorization tab and start a fresh Connect attempt from Claude. Do not reuse old approval links. Report the visible error if it still fails, without sharing codes or tokens.
4. 04If no teams appear or a read is denied, check the authorizing Slackalendar account, selected company/team grant, membership and expiry. Do not grant broader access just to fix an error.