Connect ChatGPT to Slackalendar

Check access and choose the right connection

Use ChatGPT on the web with an account and workspace that allows custom remote MCP servers. Available menus, plans and administrator controls vary. Full custom MCP support is documented for Business and Enterprise/Edu; Pro has more limited read/fetch support. If the custom-server option is missing, check your plan and workspace permissions rather than changing Slackalendar security settings.

• This connects your existing Slackalendar data to ChatGPT. It is not a public OpenAI marketplace listing and does not add an OpenAI-powered assistant inside Slackalendar.
• Each person authorizes their own company and teams. Do not share an administrator's credentials or grant across a workspace.
• Claude, Gemini and Perplexity use separate connections. Connecting ChatGPT does not change their access.

Add the remote MCP server in ChatGPT

1. 01Sign in to Slackalendar, open Settings → AI connections, and copy Remote MCP. On Slackalendar.com it is https://slackalendar.com/mcp.
2. 02In ChatGPT web, open Plugins → plus → Add custom MCP server when available. Older interfaces use Settings or Workspace settings → Apps → Create, sometimes behind Developer mode. Only use controls your account is authorized to access.
3. 03Name the connection Slackalendar and paste the Remote MCP endpoint as the public HTTPS server URL.
4. 04Choose OAuth and dynamic client registration (DCR) if a registration choice is shown. Slackalendar supports public-client authentication (none) with S256 PKCE. Leave optional Client ID and Client Secret inputs blank when using DCR. Do not paste a Slackalendar API credential or OpenAI API key.
5. 05Review ChatGPT's custom-server risk notice, then create or scan the connection and follow its authorization prompt. Labels may include Create as a plugin or Scan Tools.

Approve read-only access

1. 01On the Slackalendar authorization page, sign in if prompted, return to the authorization tab and choose Continue.
2. 02Select one company, the specific teams and an access duration from 1 to 90 days (30 by default).
3. 03Leave task-status changes unchecked. Read access is required, but an optional write request does not grant writes unless you approve them.
4. 04Choose Allow access and wait for the return to ChatGPT. A brief Access approved page provides a Continue button if automatic navigation does not finish. Review the discovered tools. A read-only grant exposes five tools and no change_task_status tool.
5. 05Enable or install the connection for your own conversation if prompted. Organization-wide publishing is a separate workspace-admin decision, not necessary proof that personal authorization worked.

Confirm communication and understand capabilities

Start a new chat, select Slackalendar or @mention it when the interface offers that option, and send: 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 discovers approved teams you can still access.
• get_team_workflow reads ordered team statuses and tags.
• list_tasks searches authorized tasks by title, description, tags and metadata, with status/archive filters and pagination.
• get_task reads a task and saved custom values; get_task_activity reads comments and history.
• For a follow-up, ask: Using Slackalendar, open the first task and summarize its description and recent activity. Do not change anything. Explicitly select the connection again if ChatGPT requires it for new tool calls.
• No task creation, deletion, description/comment edits, assignment/date changes, billing, membership or administrator actions are available. Read-only access cannot change team or Project Dashboard statuses.

Troubleshoot and manage access

1. 01If approval stalls, close the old authorization tab and start a fresh connection attempt. Do not reuse a consumed approval link.
2. 02If a request is denied, check the Slackalendar account, selected teams, current membership and connection expiry. Do not broaden access just to troubleshoot.
3. 03In Settings → AI connections, review company, teams, permissions and expiry. Revoke only the ChatGPT connection if you want to stop its access; do not revoke the working Claude grant.
4. 04If a long-unused connection cannot renew or reports invalid_client, create a fresh connection and approve access again.
5. 05If tools change in a future release, a workspace administrator may need to refresh and approve the tool list in ChatGPT. This does not require changing the existing Claude connection.