Connect Perplexity to Slackalendar

Check connector access and privacy

Use a Perplexity account that offers custom remote connectors. In an organization, an administrator must enable Allow members to add custom connectors for personal connectors. Only administrators can add organization-wide connectors. Menus and availability can vary by account.

• Start with an individual connector and your own Slackalendar authorization. Do not authenticate once on behalf of an entire organization: this could share access under the authorizing user's identity.
• Review Perplexity's privacy and data settings before sharing task information. This is a custom MCP connector, not a public marketplace listing or a Perplexity-powered assistant inside Slackalendar.
• Claude, ChatGPT and Gemini use separate approvals. Keep their working connections unchanged.

Add the remote MCP connector in Perplexity

1. 01Open Perplexity on the web → Plugins in the sidebar. Older interfaces use Customize → Connectors.
2. 02Choose Add custom → Add MCP connector → Remote. Name it Slackalendar and enter https://slackalendar.com/mcp as the MCP server URL.
3. 03Under Advanced, use OAuth authentication, Streamable HTTP transport and Public network access. Do not choose SSE, API Key or None for this setup.
4. 04Slackalendar supports OAuth discovery and dynamic client registration (DCR), using a public OAuth client with S256 PKCE. Client ID and Client Secret should not need manual entry. If your interface requires them and offers no DCR path, stop and share only the field labels, not credentials.
5. 05Review the custom-connector risk notice, select its acknowledgement checkbox and choose Add. Then select the connector card to start authentication and enable it.

Authorize selected teams with read-only access

1. 01Sign in to Slackalendar if prompted, return to the authorization tab and choose Continue.
2. 02Review the requesting client and callback destination. Choose one company, the specific teams to share and an access duration from 1 to 90 days (30 by default).
3. 03Leave task-status changes unchecked. Read access is required; optional writes are not authorized just because a client requests them.
4. 04Choose Allow access. The brief Access approved page returns automatically; if it stays open, use Continue to Perplexity (or the displayed client name).
5. 05Enable the connector in Perplexity if needed. Expect five read tools and no change_task_status tool.

Verify task reads and follow-up communication

Enable or select Slackalendar in Perplexity and ask: Using Slackalendar, list the teams I can access, then show up to five tasks from [your team name]. Do not change anything.

• For a follow-up, ask: Using Slackalendar, open the first task and summarize its description and recent activity. Do not change anything.
• list_teams finds approved teams you can still access. get_team_workflow reads ordered team statuses and available tags.
• list_tasks searches authorized tasks by title, description, tags and metadata, with status/archive filters and pagination.
• get_task reads task details and saved custom values. get_task_activity reads comments and history.
• Read-only grants cannot change team or Project Dashboard statuses. No task creation, deletion, editing, assignment/date changes, billing, membership or administrator actions are available.

Troubleshoot or disconnect Perplexity

1. 01If Add is unavailable, check the name, HTTPS server URL and acknowledgement checkbox. If the custom-connector option is missing, check account availability and organization administrator permissions.
2. 02If server validation fails, check the exact /mcp URL, OAuth and Streamable HTTP settings. Do not disable authentication or broaden permissions to fix a connection.
3. 03If approval stalls, start a fresh connection attempt instead of reusing an old authorization URL. On Access approved, try the visible Continue link.
4. 04If a redirect error occurs, share only the error text or a screenshot without the address bar. Do not send full authorization URLs or invent a callback. Slackalendar validates the exact callback registered through DCR.
5. 05If Perplexity answers without using Slackalendar, enable/select the connector and explicitly name it in the prompt. Check current team membership, approved scope and connection expiry if access is denied.
6. 06Use the connector's ellipsis menu in Perplexity to modify or remove it. In Slackalendar Settings → AI connections, Revoke only Perplexity to invalidate its grant. Removing a card is not evidence that its Slackalendar grant was revoked.
7. 07If a long-unused connection cannot renew or reports invalid_client, create a fresh Perplexity connection and approve access again.