# Connect Slack, MCP and your tools to Coworkies

Source: https://docs.coworkies.com/integrations/

> Set up Slack and the hosted MCP server, understand space permissions and API keys, and check the release status of GPT and Claude integrations.

> **My own jobs** is deployed for Slack and the hosted MCP server. GPT/ChatGPT and Claude client integrations remain untested and undeployed.

Use Slack to manage your own jobs or a space’s jobs, MCP to connect compatible tools, or the REST API for your own integration. Each connection has its own authentication and permissions.

## Connecting and publishing

Connect an active, verified Coworkies account and choose **My own jobs**, or a confirmed space you manage. Personal hiring needs no coworking space. Installation alone gives no access to another person’s or space’s jobs.

Job publication is separate: free listings follow Coworkies free-listing rules, while paid jobs use your hiring allowance or require checkout. Creating or rotating a manual API key requires a managed confirmed Pro space; choose **Set up on Coworkies** if you do not have a key.

## Availability

Status reviewed **27 October 2026**.

| Integration | Status | What this means |
| --- | --- | --- |
| REST API v2 | Deployed | Use scoped API keys and the API reference. |
| Slack bot | Deployed | Install the app, then connect each person separately. Native API-key setup has automated coverage; a real member’s native-key submission remains unverified. |
| Hosted MCP server | Deployed | Server-side authentication and tools are available under the access rules below. This does not establish support in every client. |
| GPT / ChatGPT plugin | **Not yet tested or deployed** | Client installation, authentication and real tool use have not been verified. Do not treat package or server tests as a released ChatGPT integration. |
| Claude connector | **Not yet tested or deployed** | Real Claude connection, authentication, tool use and distribution remain pending. |

A deployed MCP server is not a deployed GPT plugin or Claude connector. Custom client installation and publication in a client’s directory also require separate verification.

## Choose a setup guide

- [Slack setup and commands](https://docs.coworkies.com/integrations/slack/): install the app, connect with your account or an API key, change space and disconnect.
- [MCP setup and tools](https://docs.coworkies.com/integrations/mcp/): endpoint, authentication, scopes, eligible spaces and preview-before-write behavior.
- [Permissions and API-key ownership](https://docs.coworkies.com/integrations/permissions/): who can connect, publish, create keys and manage credentials.
- [REST API quick start](https://docs.coworkies.com/api/): build a server-side integration with API v2.

## Before you connect

Coworkies space owners and Team Members with the `staff` role can manage that space’s jobs. Being a coworking member, Slack member or Slack administrator does not grant those rights. Installing the Slack app does not connect everyone in the workspace.

A valid API key delegates its owner’s permissions. Protect it like a password. Publication still depends on the job’s returned status, hiring allowance and any checkout required by Coworkies.

## Report a connection problem

Include the time, integration, action, visible error and request ID if available. Never include an API key, callback URL query, private management link or unredacted screenshot containing credentials. Use [Contact support](https://docs.coworkies.com/contact/).

Coworkies uses Pulse and its unified error pipeline to collect API, MCP and Slack activity. Reports are best effort: an HTTP success, Slack acknowledgement or heartbeat does not prove that a job was published, and missing telemetry does not prove there were no requests.