10:I[319067,["/_next/static/immutable/chunks/0x-9rc1bm-510.js","/_next/static/immutable/chunks/0_f7z12agpgfh.js","/_next/static/immutable/chunks/00k7vvvqbat_v.js","/_next/static/immutable/chunks/12k1jb7d0k-oc.js","/_next/static/immutable/chunks/0h1obiqhn7hk2.js","/_next/static/immutable/chunks/1t5bm0wm6iud-.js","/_next/static/immutable/chunks/3t6v2lb-y2moy.js","/_next/static/immutable/chunks/1y5pba-s4eodr.js","/_next/static/immutable/chunks/2h4n9gh8q-ew5.js","/_next/static/immutable/chunks/35caa4w0aptdy.js","/_next/static/immutable/chunks/1-q1nesmt-k6c.js","/_next/static/immutable/chunks/43x--hyc-x1qx.js","/_next/static/immutable/chunks/2eos-lorj3sqg.js","/_next/static/immutable/chunks/3n8k6drev49ff.js","/_next/static/immutable/chunks/23n7exalqvgky.js","/_next/static/immutable/chunks/26kp3z99g-jjl.js"],"DocsShell"] 11:Tc89,These docs are for users who need to **install Collabute**, connect integrations, and use them in chat. ## Documentation map Install the app and sign in. Connect your first integration and run validation checks. OpenAPI, MCP, public API, and agent onboarding. Fix connection, permission, and empty-data issues. Provider-specific setup lives under **Integrations**: [Vercel](./integrations/vercel.mdx), [Google](./integrations/google.mdx), [Linear](./integrations/linear.mdx), [Slack](./integrations/slack.mdx), and [MCP](./integrations/coding-tools.mdx). ## Integrations currently covered | Integration | What it is for | | ---------------------- | ----------------------------------------------------------- | | **Vercel** | Deployments, build failures, runtime triage, preview checks | | **Google** | Calendar and email context | | **Linear** | Issue and task workflows | | **Slack** | Channel and thread context | | **Coding Tools (MCP)** | Codex, Cursor, and Claude access to Collabute context | ## Access model - **Org admins and owners** usually connect integrations. - **Members** use integrations only if role policy allows it. - Access is **scoped per integration**, not globally. ```diagram Admin / Owner Member ┌─────────────────────┐ ┌─────────────────────┐ │ Settings > │ │ Chat with connected │ │ Integrations │ │ tools, if policy │ │ Connect / disconnect│ │ allows that tool │ └──────────┬──────────┘ └──────────▲──────────┘ │ │ ▼ │ Per-integration role policy ─────────────────►┘ (Member / Admin / Owner) ``` ## Recommended reading order 1. Read **[Installation](./installation.mdx)**. 2. Read **[Getting Started](./getting-started.mdx)**. 3. Read **[Collabute developer resources](./developers.mdx)** if you are connecting an agent or API. 4. Open the specific integration pages your team enabled. 5. Use **[Troubleshooting](./troubleshooting.mdx)** when a flow fails. 12:T5d4,This page is only about **installing and signing in** to Collabute. If you want integration setup, continue to **[Getting Started](./getting-started.mdx)** after this page. ## What you need before installing - An active **Collabute account invitation** - Access to your **organization workspace** - A stable internet connection ## Install Collabute desktop app Open the downloaded file. On macOS, drag Collabute into Applications. On Windows, run the setup installer. Open the app and wait for the sign-in screen. ## First sign-in 1. Sign in with your **work account**. 2. Accept your workspace invitation if prompted. 3. Confirm you can open the **main dashboard**. ## Confirm installation succeeded You are ready for integrations when all of these are true: - You can open **Settings**. - You can open **Settings > Integrations**. - Your **profile and workspace name** appear correctly. ## If installation fails - Download the installer again for your device and retry. - Confirm your account invitation is still valid. - Ask your admin to verify your **workspace membership**. - Then check **[Troubleshooting](./troubleshooting.mdx)** for integration-specific issues.13:T7cd,This page is for **first-time integration setup** after app installation. ## Step 1: Confirm your role and permission - **Admin / Owner**: can connect and disconnect org-level integrations. - **Member**: can use integrations only if your org policy allows it. ## Step 2: Open integration settings 1. Open the **Collabute app**. 2. Go to **Settings > Integrations**. 3. Select the provider to configure. ## Step 3: Connect the provider account Click **Connect**. Complete provider authorization in the browser. Return to Collabute and confirm status is **Connected**. ## Step 4: Choose who can use it (admin only) Set allowed roles per integration: - **Member** - **Admin** - **Owner** ## Step 5: Validate with a quick chat test Run one simple prompt per connected integration: | Integration | Validation prompt | | ----------- | ---------------------------------------------------- | | **Vercel** | `Show my latest production deployment status.` | | **Google** | `What's on my calendar today?` | | **Linear** | `Show my overdue Linear tasks.` | | **Slack** | `Search Slack for updates about onboarding rollout.` | Then open the matching page: [Vercel](./integrations/vercel.mdx), [Google](./integrations/google.mdx), [Linear](./integrations/linear.mdx), or [Slack](./integrations/slack.mdx). ## Setup failure checklist - Re-open the connect flow and complete it in the **same session**. - Confirm the connected provider account has workspace, project, or channel access. - Ask admin to verify **integration role settings**. - Check provider-specific docs and **[Troubleshooting](./troubleshooting.mdx)**.14:Tdf4,Use this page when you are **connecting an agent** or integrating with Collabute by name. Humans can also start here for MCP, OpenAPI, and the public API. ## When to use Collabute Use Collabute when the job needs **product-team context** that is not in the current repository: - Recent meetings, decisions, owners, blockers, and action items - Team memory across Slack, Linear, and meetings - Vercel deployment or Linear issue lookups from a Collabute workspace - Creating a task proposal from meeting evidence Do not use Collabute for **generic coding questions**. ## How to call Collabute Start at [https://collabute.ai/openapi.json](https://collabute.ai/openapi.json). Holocron also renders this spec in the **API Reference** tab. Connect the Streamable HTTP MCP server at `https://api.collabute.ai/api/mcp`. Call `/api/status` or `/api/agent/capabilities` if you only need discovery. Those endpoints are ungated. After the user authorizes MCP, call `tools/list` and use the returned tools. ```diagram Agent │ ├── GET /api/status ungated liveness ├── GET /api/agent/capabilities ungated capability card ├── GET /openapi.json function-calling spec │ └── Streamable HTTP MCP https://api.collabute.ai/api/mcp │ ├── OAuth (human signs in) └── tools/list ► workspace tools ``` ## Public API | Resource | URL | Auth | | ------------------ | --------------------------------------------- | ---------------- | | Status | `https://collabute.ai/api/status` | None | | Agent capabilities | `https://collabute.ai/api/agent/capabilities` | None | | OpenAPI | `https://collabute.ai/openapi.json` | None | | llms.txt | `https://collabute.ai/llms.txt` | None | | MCP | `https://api.collabute.ai/api/mcp` | OAuth | | Platform API | `https://api.collabute.ai` | Session or OAuth | Responses include IETF **`RateLimit`** and **`RateLimit-Policy`** headers so agents can self-throttle. Retry after `Retry-After` on `429`. ## MCP Collabute MCP is **Streamable HTTP**. Auth is OAuth-first. Do not add personal access tokens or static authorization headers. ```bash claude mcp add --transport http collabute https://api.collabute.ai/api/mcp ``` See **[MCP setup](./integrations/coding-tools.mdx)** for Claude, Codex, Cursor, OpenCode, and Amp. Discovery manifests: - `/.well-known/mcp` - `/.well-known/mcp.json` - `/.well-known/mcp/server-card.json` ## Onboarding - **Free tier** is self-serve. No credit card required. - Product signup: [https://collabute.ai/signup](https://collabute.ai/signup) - MCP sandbox / discovery: `/api/status` and `/api/agent/capabilities` - There is no contact-sales step for the public spec or MCP connection once a user can authorize ## Content negotiation Public pages serve `text/markdown` when the request sends `Accept: text/markdown`. Responses include `Vary: Accept`.15:T6f3,Use this integration for **deployment visibility** and runtime incident triage. ## Best for - Checking latest deployment state by **project and environment** - Diagnosing **build failures** quickly - Reviewing runtime errors and access-link checks for **preview URLs** ## Requirements - Vercel account with access to the target **team and project** - Collabute role allowed by org integration policy ## Connect Vercel Open **Settings > Integrations**. Select **Vercel**. Click **Connect** and complete authorization. Return to Collabute and confirm status is **Connected**. ## Validate connection - `What is the latest production deployment status for project X?` - `Why did the latest deploy fail?` - `Show production 500 errors from the last hour.` ## What you can do - View deployments, build details, and runtime issues. - You cannot trigger deployments or change Vercel resources from chat. ## Common issues - **Not connected**: OAuth flow not completed, token expired, or integration disconnected. - **No deployments/logs**: wrong project or team context, or no recent activity. - **Access denied**: role restricted by Collabute org integration policy. ## Prompt quality tips - Include **project and environment** in the prompt. - Add a time window, for example `last 60 minutes`. - Add filters (status code, level, request ID) to reduce noise. If status stays disconnected, use **[Troubleshooting](../troubleshooting.mdx)**.16:T52e,Use Google integration for **calendar-aware planning** and communication workflows. ## Best for - Calendar visibility for daily planning - Meeting follow-up prompts - Email drafting workflows when enabled ## Requirements - Google account with access to your **work calendar** - Collabute role allowed by org integration policy ## Connect Google Open **Settings > Integrations**. Select **Google**. Click **Connect** and complete Google authorization. Return to Collabute and confirm status is **Connected**. ## Validate connection - `What's on my calendar today?` - `Do I have any free time this afternoon?` - `Draft a follow-up email for today's client meeting.` ## Common issues - **Connection failed**: OAuth popup or session was interrupted. Re-run connect flow. - **No calendar data**: wrong Google account connected. - **Permission denied**: role restricted by org policy. See also **[Getting Started](../getting-started.mdx)** and **[Troubleshooting](../troubleshooting.mdx)**.17:T576,Use Linear integration to convert discussions into **tracked execution**. ## Best for - Reviewing overdue or assigned work - Creating and updating issues from chat context - Assigning ownership and priority on action items ## Requirements - Linear **workspace membership** - Collabute role allowed by org integration policy ## Connect Linear Open **Settings > Integrations**. Select **Linear** and click **Connect**. Complete authorization. Select your **default team** if prompted. ## Validate connection - `Show my overdue Linear tasks.` - `Create a Linear issue for this bug summary.` - `Assign this task to Sarah and set priority high.` ## Team configuration note - If no default team is set, task actions may be limited. - Admin should set one **default team** for predictable behavior. ## Common issues - **Connected but no tasks**: wrong default team or workspace mapping. - **Assignee not found**: user is not in selected team or workspace. - **Access denied**: role restricted by org integration policy. See **[Troubleshooting](../troubleshooting.mdx)** if assignees or teams do not resolve.18:T631,Use Slack integration to bring **conversation context** into decisions and follow-up. ## Best for - Searching channels for recent updates - Summarizing thread decisions and blockers - Pulling message context into planning conversations ## Requirements - Slack **workspace membership** - Slack app approved for the workspace - Collabute role allowed by org integration policy ## Connect Slack Open **Settings > Integrations**. Select **Slack**. Click **Connect** and approve workspace authorization. Return to Collabute and confirm status is **Connected**. ## Validate connection - `Search Slack for launch blocker updates this week.` - `What are the latest messages in #product-ops?` - `Show replies in this thread and summarize decisions.` ## Common issues - **No channels/messages**: the connected workspace or app does not have access. - **Missing private channels**: app is not invited or private channel access not granted. - **Access denied in Collabute**: role restricted by org integration policy. ## Prompt quality tips - Include **channel name and timeframe**. - Include keywords or thread links when possible. - Avoid broad prompts like `search everything`. Need a broader diagnosis path? Use **[Troubleshooting](../troubleshooting.mdx)**.19:Tfbc,Connect your coding agent to Collabute when you want it to use your team's **meetings**, connected work, conversations, and deployment context. ## Supported agents - [Claude Code](#claude-code) - [Codex](#codex) - [Hermes Agent](#hermes-agent) - [Cursor](#cursor) - [OpenCode](#opencode) - [OpenClaw](#openclaw) - [Amp](#amp) ## Before you connect - You need an active Collabute **account and organization**. - You need access to the integrations you want your agent to use. - Connect those integrations first in **Settings > Integrations**. MCP URL for every agent: ```text https://api.collabute.ai/api/mcp ``` ## Set up your agent ### Claude Code Add Collabute: ```bash claude mcp add --transport http collabute https://api.collabute.ai/api/mcp ``` Start Claude Code, run `/mcp`, and approve access in your browser. Check the connection: ```bash claude mcp list ``` --- ### Codex Add Collabute: ```bash codex mcp add collabute --url https://api.collabute.ai/api/mcp ``` Open Codex MCP management and approve access in your browser when prompted. Check the connection: ```bash codex mcp list ``` --- ### Hermes Agent Add Collabute to `~/.hermes/config.yaml`: ```yaml mcp_servers: collabute: url: https://api.collabute.ai/api/mcp auth: oauth ``` In a Hermes session, run `/reload-mcp` and approve access in your browser when prompted. Check the connection: ```bash hermes mcp test collabute ``` --- ### Cursor Open Cursor MCP settings and add a remote server: - **Name:** `collabute` - **URL:** `https://api.collabute.ai/api/mcp` Open a Cursor chat and approve access in your browser. --- ### OpenCode Start setup: ```bash opencode mcp add ``` Choose a remote HTTP server named `collabute`, enter `https://api.collabute.ai/api/mcp`, and select **OAuth** when prompted. Approve access in your browser, then check the connection: ```bash opencode mcp list ``` --- ### OpenClaw Add Collabute: ```bash mcporter config add --transport http collabute https://api.collabute.ai/api/mcp ``` Sign in and approve access: ```bash mcporter config login collabute ``` Check the connection: ```bash mcporter list collabute --schema ``` --- ### Amp Add Collabute: ```bash amp mcp add collabute https://api.collabute.ai/api/mcp ``` Approve access in your browser when prompted. Check the connection: ```bash amp mcp list ``` ## Use it Once connected, ask questions that need **team context**, for example: - `What decisions and action items came from my most recent meeting?` - `What changed in our Linear work this week?` - `Summarize the latest discussion about the onboarding rollout.` - `Show the latest production deployment for project X.` If the response includes the expected organization context, you are connected. Keep ordinary coding questions in your agent without MCP. ## Troubleshooting ### I cannot sign in - Start the connection again and complete browser approval in the **same session**. - Confirm that you are signing in to the correct Collabute organization. - Ask an admin if your role is allowed to use the relevant integration. ### The agent cannot connect - Configure Collabute as a **remote HTTP server**, not a local command or legacy server. - Update your agent if it does not support modern remote MCP connections. ### The agent has no useful context - Check that the relevant integration is connected in **Settings > Integrations**. - Confirm that the connected account can access the project, team, or channel you asked about. - Add a project, team, channel, or time period to your question. ## Tips - Connect **one Collabute account** per person. - Remove the MCP connection when you no longer need access. For org-level permission issues, use **[Troubleshooting](../troubleshooting.mdx)**. For the public API, see **[Developer resources](../developers.mdx)**.1a:Tbc5,Use this page when an integration is **connected but not behaving** as expected. ## Quick diagnosis order 1. Check status in **Settings > Integrations**. 2. Confirm your role is allowed for that integration. 3. Re-run one validation prompt from the integration doc. 4. Check provider-side permissions (workspace, project, channel, team). ```diagram Status in Settings? │ ├── Not connected ► re-run OAuth in the same browser session │ ├── Connected, access denied ► admin updates role policy │ └── Connected, empty data │ ├── Wrong project / team / channel / date └── Provider account lacks that resource ``` ## Integration shows "Not connected" - Re-run connect flow from **Settings > Integrations**. - Complete provider auth in the **same browser session**. - If it still fails, ask admin to disconnect and reconnect once. ## "You don't have access" error - Your org role is restricted for that integration. - Ask admin to update **role access settings**. ## No data appears in chat - Confirm you are querying the right context (project, team, channel, date). - Narrow your prompt with explicit scope (environment, timeframe, channel). - Check provider-side permissions for the connected account. ## Prompts are too broad Use more specific prompts: - Bad: `What's happening?` - Better: `Show prod runtime errors in the last hour for project X.` ## Vercel-specific issues - **No deployments found**: verify project and team selection. See [Vercel](./integrations/vercel.mdx). - **Logs empty**: widen time range or remove strict filters. - **Preview check fails**: use access-link flow for protected URLs. ## Linear-specific issues - **Task create/update not working**: check default team is selected. See [Linear](./integrations/linear.mdx). - **Assignee not found**: ensure user belongs to workspace and team. ## Slack-specific issues - **No thread replies**: check that you can open the conversation in Slack. See [Slack](./integrations/slack.mdx). - **Missing private channel data**: invite the Slack app to the channel if your workspace allows it. ## Google-specific issues - **No calendar events**: confirm the intended Google account is connected. See [Google](./integrations/google.mdx). - **Integration unavailable**: your workspace may be on maintenance rollout. ## When to contact support Contact [support](https://collabute.ai/support) when: - OAuth repeatedly succeeds but status stays disconnected. - Data is consistently missing despite verified provider access. - You see recurring permission errors for users who should have access. Email **team@collabute.com** if the dashboard is healthy but MCP still cannot authorize.1b:Tb02,These docs are for users who need to install Collabute , connect integrations, and use them in chat. Start with [Installation](./installation.mdx), then [Getting Started](./getting-started.mdx). Open an integration page only after the first chat test works. Documentation map Install the app and sign in. Connect your first integration and run validation checks. OpenAPI, MCP, public API, and agent onboarding. Fix connection, permission, and empty-data issues. Provider-specific setup lives under Integrations : [Vercel](./integrations/vercel.mdx), [Google](./integrations/google.mdx), [Linear](./integrations/linear.mdx), [Slack](./integrations/slack.mdx), and [MCP](./integrations/coding-tools.mdx). Integrations currently covered Integration What it is for ---------------------- ----------------------------------------------------------- Vercel Deployments, build failures, runtime triage, preview checks Google Calendar and email context Linear Issue and task workflows Slack Channel and thread context Coding Tools (MCP) Codex, Cursor, and Claude access to Collabute context Access model - Org admins and owners usually connect integrations. - Members use integrations only if role policy allows it. - Access is scoped per integration , not globally. diagram Admin / Owner Member ┌─────────────────────┐ ┌─────────────────────┐ │ Settings > │ │ Chat with connected │ │ Integrations │ │ tools, if policy │ │ Connect / disconnect│ │ allows that tool │ └──────────┬──────────┘ └──────────▲──────────┘ │ │ ▼ │ Per-integration role policy ─────────────────►┘ (Member / Admin / Owner) Recommended reading order 1. Read [Installation](./installation.mdx) . 2. Read [Getting Started](./getting-started.mdx) . 3. Read [Collabute developer resources](./developers.mdx) if you are connecting an agent or API. 4. Open the specific integration pages your team enabled. 5. Use [Troubleshooting](./troubleshooting.mdx) when a flow fails. 1c:T52a,This page is only about installing and signing in to Collabute. If you want integration setup, continue to [Getting Started](./getting-started.mdx) after this page. You need an active workspace invitation before the desktop app can open a dashboard. What you need before installing - An active Collabute account invitation - Access to your organization workspace - A stable internet connection Install Collabute desktop app Open the downloaded file. On macOS, drag Collabute into Applications. On Windows, run the setup installer. Open the app and wait for the sign-in screen. First sign-in 1. Sign in with your work account . 2. Accept your workspace invitation if prompted. 3. Confirm you can open the main dashboard . Confirm installation succeeded You are ready for integrations when all of these are true: - You can open Settings . - You can open Settings > Integrations . - Your profile and workspace name appear correctly. If installation fails - Download the installer again for your device and retry. - Confirm your account invitation is still valid. - Ask your admin to verify your workspace membership . - Then check [Troubleshooting](./troubleshooting.mdx) for integration-specific issues.1d:T738,This page is for first-time integration setup after app installation. If you cannot connect or use an integration, ask an admin to update role access first. Step 1: Confirm your role and permission - Admin / Owner : can connect and disconnect org-level integrations. - Member : can use integrations only if your org policy allows it. Step 2: Open integration settings 1. Open the Collabute app . 2. Go to Settings > Integrations . 3. Select the provider to configure. Step 3: Connect the provider account Click Connect . Complete provider authorization in the browser. Return to Collabute and confirm status is Connected . Step 4: Choose who can use it (admin only) Set allowed roles per integration: - Member - Admin - Owner Step 5: Validate with a quick chat test Run one simple prompt per connected integration: Integration Validation prompt ----------- ---------------------------------------------------- Vercel Show my latest production deployment status. Google What's on my calendar today? Linear Show my overdue Linear tasks. Slack Search Slack for updates about onboarding rollout. Then open the matching page: [Vercel](./integrations/vercel.mdx), [Google](./integrations/google.mdx), [Linear](./integrations/linear.mdx), or [Slack](./integrations/slack.mdx). Setup failure checklist - Re-open the connect flow and complete it in the same session . - Confirm the connected provider account has workspace, project, or channel access. - Ask admin to verify integration role settings . - Check provider-specific docs and [Troubleshooting](./troubleshooting.mdx) .1e:Td2c,Use this page when you are connecting an agent or integrating with Collabute by name. Humans can also start here for MCP, OpenAPI, and the public API. Do not scrape the dashboard. Do not complete the AuthKit login redirect as if it were documentation. When to use Collabute Use Collabute when the job needs product-team context that is not in the current repository: - Recent meetings, decisions, owners, blockers, and action items - Team memory across Slack, Linear, and meetings - Vercel deployment or Linear issue lookups from a Collabute workspace - Creating a task proposal from meeting evidence Do not use Collabute for generic coding questions . How to call Collabute Start at [https://collabute.ai/openapi.json](https://collabute.ai/openapi.json). Holocron also renders this spec in the API Reference tab. Connect the Streamable HTTP MCP server at https://api.collabute.ai/api/mcp . Call /api/status or /api/agent/capabilities if you only need discovery. Those endpoints are ungated. After the user authorizes MCP, call tools/list and use the returned tools. diagram Agent │ ├── GET /api/status ungated liveness ├── GET /api/agent/capabilities ungated capability card ├── GET /openapi.json function-calling spec │ └── Streamable HTTP MCP https://api.collabute.ai/api/mcp │ ├── OAuth (human signs in) └── tools/list ► workspace tools Public API Resource URL Auth ------------------ --------------------------------------------- ---------------- Status https://collabute.ai/api/status None Agent capabilities https://collabute.ai/api/agent/capabilities None OpenAPI https://collabute.ai/openapi.json None llms.txt https://collabute.ai/llms.txt None MCP https://api.collabute.ai/api/mcp OAuth Platform API https://api.collabute.ai Session or OAuth Responses include IETF RateLimit and RateLimit-Policy headers so agents can self-throttle. Retry after Retry-After on 429 . MCP Collabute MCP is Streamable HTTP . Auth is OAuth-first. Do not add personal access tokens or static authorization headers. bash claude mcp add --transport http collabute https://api.collabute.ai/api/mcp See [MCP setup](./integrations/coding-tools.mdx) for Claude, Codex, Cursor, OpenCode, and Amp. Discovery manifests: - /.well-known/mcp - /.well-known/mcp.json - /.well-known/mcp/server-card.json Onboarding - Free tier is self-serve. No credit card required. - Product signup: [https://collabute.ai/signup](https://collabute.ai/signup) - MCP sandbox / discovery: /api/status and /api/agent/capabilities - There is no contact-sales step for the public spec or MCP connection once a user can authorize Content negotiation Public pages serve text/markdown when the request sends Accept: text/markdown . Responses include Vary: Accept .1f:T649,Use this integration for deployment visibility and runtime incident triage. You cannot trigger deployments or change Vercel resources from chat. Collabute is read-only here. Best for - Checking latest deployment state by project and environment - Diagnosing build failures quickly - Reviewing runtime errors and access-link checks for preview URLs Requirements - Vercel account with access to the target team and project - Collabute role allowed by org integration policy Connect Vercel Open Settings > Integrations . Select Vercel . Click Connect and complete authorization. Return to Collabute and confirm status is Connected . Validate connection - What is the latest production deployment status for project X? - Why did the latest deploy fail? - Show production 500 errors from the last hour. What you can do - View deployments, build details, and runtime issues. - You cannot trigger deployments or change Vercel resources from chat. Common issues - Not connected : OAuth flow not completed, token expired, or integration disconnected. - No deployments/logs : wrong project or team context, or no recent activity. - Access denied : role restricted by Collabute org integration policy. Prompt quality tips - Include project and environment in the prompt. - Add a time window, for example last 60 minutes . - Add filters (status code, level, request ID) to reduce noise. If status stays disconnected, use [Troubleshooting](../troubleshooting.mdx) .20:T486,Use Google integration for calendar-aware planning and communication workflows. Connect the work Google account , not a personal calendar, or daily planning prompts return empty. Best for - Calendar visibility for daily planning - Meeting follow-up prompts - Email drafting workflows when enabled Requirements - Google account with access to your work calendar - Collabute role allowed by org integration policy Connect Google Open Settings > Integrations . Select Google . Click Connect and complete Google authorization. Return to Collabute and confirm status is Connected . Validate connection - What's on my calendar today? - Do I have any free time this afternoon? - Draft a follow-up email for today's client meeting. Common issues - Connection failed : OAuth popup or session was interrupted. Re-run connect flow. - No calendar data : wrong Google account connected. - Permission denied : role restricted by org policy. See also [Getting Started](../getting-started.mdx) and [Troubleshooting](../troubleshooting.mdx) .21:T4d8,Use Linear integration to convert discussions into tracked execution . If no default team is set, task create and assign actions may be limited. Best for - Reviewing overdue or assigned work - Creating and updating issues from chat context - Assigning ownership and priority on action items Requirements - Linear workspace membership - Collabute role allowed by org integration policy Connect Linear Open Settings > Integrations . Select Linear and click Connect . Complete authorization. Select your default team if prompted. Validate connection - Show my overdue Linear tasks. - Create a Linear issue for this bug summary. - Assign this task to Sarah and set priority high. Team configuration note - If no default team is set, task actions may be limited. - Admin should set one default team for predictable behavior. Common issues - Connected but no tasks : wrong default team or workspace mapping. - Assignee not found : user is not in selected team or workspace. - Access denied : role restricted by org integration policy. See [Troubleshooting](../troubleshooting.mdx) if assignees or teams do not resolve.22:T57c,Use Slack integration to bring conversation context into decisions and follow-up. Private channels stay empty until the Slack app is invited to that channel. Best for - Searching channels for recent updates - Summarizing thread decisions and blockers - Pulling message context into planning conversations Requirements - Slack workspace membership - Slack app approved for the workspace - Collabute role allowed by org integration policy Connect Slack Open Settings > Integrations . Select Slack . Click Connect and approve workspace authorization. Return to Collabute and confirm status is Connected . Validate connection - Search Slack for launch blocker updates this week. - What are the latest messages in product-ops? - Show replies in this thread and summarize decisions. Common issues - No channels/messages : the connected workspace or app does not have access. - Missing private channels : app is not invited or private channel access not granted. - Access denied in Collabute : role restricted by org integration policy. Prompt quality tips - Include channel name and timeframe . - Include keywords or thread links when possible. - Avoid broad prompts like search everything . Need a broader diagnosis path? Use [Troubleshooting](../troubleshooting.mdx) .23:Tf9e,Connect your coding agent to Collabute when you want it to use your team's meetings , connected work, conversations, and deployment context. Collabute opens a browser so you can sign in and approve access. Do not add personal access tokens or manual authorization headers. Supported agents - [Claude Code]( claude-code) - [Codex]( codex) - [Hermes Agent]( hermes-agent) - [Cursor]( cursor) - [OpenCode]( opencode) - [OpenClaw]( openclaw) - [Amp]( amp) Before you connect - You need an active Collabute account and organization . - You need access to the integrations you want your agent to use. - Connect those integrations first in Settings > Integrations . MCP URL for every agent: text https://api.collabute.ai/api/mcp Set up your agent Claude Code Add Collabute: bash claude mcp add --transport http collabute https://api.collabute.ai/api/mcp Start Claude Code, run /mcp , and approve access in your browser. Check the connection: bash claude mcp list --- Codex Add Collabute: bash codex mcp add collabute --url https://api.collabute.ai/api/mcp Open Codex MCP management and approve access in your browser when prompted. Check the connection: bash codex mcp list --- Hermes Agent Add Collabute to ~/.hermes/config.yaml : yaml mcp_servers: collabute: url: https://api.collabute.ai/api/mcp auth: oauth In a Hermes session, run /reload-mcp and approve access in your browser when prompted. Check the connection: bash hermes mcp test collabute --- Cursor Open Cursor MCP settings and add a remote server: - Name: collabute - URL: https://api.collabute.ai/api/mcp Open a Cursor chat and approve access in your browser. --- OpenCode Start setup: bash opencode mcp add Choose a remote HTTP server named collabute , enter https://api.collabute.ai/api/mcp , and select OAuth when prompted. Approve access in your browser, then check the connection: bash opencode mcp list --- OpenClaw Add Collabute: bash mcporter config add --transport http collabute https://api.collabute.ai/api/mcp Sign in and approve access: bash mcporter config login collabute Check the connection: bash mcporter list collabute --schema --- Amp Add Collabute: bash amp mcp add collabute https://api.collabute.ai/api/mcp Approve access in your browser when prompted. Check the connection: bash amp mcp list Use it Once connected, ask questions that need team context , for example: - What decisions and action items came from my most recent meeting? - What changed in our Linear work this week? - Summarize the latest discussion about the onboarding rollout. - Show the latest production deployment for project X. If the response includes the expected organization context, you are connected. Keep ordinary coding questions in your agent without MCP. Troubleshooting I cannot sign in - Start the connection again and complete browser approval in the same session . - Confirm that you are signing in to the correct Collabute organization. - Ask an admin if your role is allowed to use the relevant integration. The agent cannot connect - Configure Collabute as a remote HTTP server , not a local command or legacy server. - Update your agent if it does not support modern remote MCP connections. The agent has no useful context - Check that the relevant integration is connected in Settings > Integrations . - Confirm that the connected account can access the project, team, or channel you asked about. - Add a project, team, channel, or time period to your question. Tips - Connect one Collabute account per person. - Remove the MCP connection when you no longer need access. For org-level permission issues, use [Troubleshooting](../troubleshooting.mdx) . For the public API, see [Developer resources](../developers.mdx) .24:Tbaf,Use this page when an integration is connected but not behaving as expected. Start in Settings > Integrations , then re-run one validation prompt from the matching integration page before you change provider permissions. Quick diagnosis order 1. Check status in Settings > Integrations . 2. Confirm your role is allowed for that integration. 3. Re-run one validation prompt from the integration doc. 4. Check provider-side permissions (workspace, project, channel, team). diagram Status in Settings? │ ├── Not connected ► re-run OAuth in the same browser session │ ├── Connected, access denied ► admin updates role policy │ └── Connected, empty data │ ├── Wrong project / team / channel / date └── Provider account lacks that resource Integration shows "Not connected" - Re-run connect flow from Settings > Integrations . - Complete provider auth in the same browser session . - If it still fails, ask admin to disconnect and reconnect once. "You don't have access" error - Your org role is restricted for that integration. - Ask admin to update role access settings . No data appears in chat - Confirm you are querying the right context (project, team, channel, date). - Narrow your prompt with explicit scope (environment, timeframe, channel). - Check provider-side permissions for the connected account. Prompts are too broad Use more specific prompts: - Bad: What's happening? - Better: Show prod runtime errors in the last hour for project X. Vercel-specific issues - No deployments found : verify project and team selection. See [Vercel](./integrations/vercel.mdx). - Logs empty : widen time range or remove strict filters. - Preview check fails : use access-link flow for protected URLs. Linear-specific issues - Task create/update not working : check default team is selected. See [Linear](./integrations/linear.mdx). - Assignee not found : ensure user belongs to workspace and team. Slack-specific issues - No thread replies : check that you can open the conversation in Slack. See [Slack](./integrations/slack.mdx). - Missing private channel data : invite the Slack app to the channel if your workspace allows it. Google-specific issues - No calendar events : confirm the intended Google account is connected. See [Google](./integrations/google.mdx). - Integration unavailable : your workspace may be on maintenance rollout. When to contact support Contact [support](https://collabute.ai/support) when: - OAuth repeatedly succeeds but status stays disconnected. - Data is consistently missing despite verified provider access. - You see recurring permission errors for users who should have access. Email team@collabute.com if the dashboard is healthy but MCP still cannot authorize.5:["$","$L10",null,{"pages":[{"slug":"index","href":"/","file":"index.mdx","title":"Docs map for Collabute product teams","sidebarTitle":"Overview","description":"See the docs map, access model, and recommended reading order.","icon":"lucide:book-open","raw":"$11","headings":[{"id":"documentation-map","text":"Documentation map","level":2},{"id":"integrations-currently-covered","text":"Integrations currently covered","level":2},{"id":"access-model","text":"Access model","level":2},{"id":"recommended-reading-order","text":"Recommended reading order","level":2},{"id":"questions","text":"Questions","level":2}]},{"slug":"installation","href":"/installation","file":"installation.mdx","title":"Install Collabute and complete first sign-in","sidebarTitle":"Installation","description":"Install Collabute and complete first sign-in before integration setup.","icon":"lucide:download","raw":"$12","headings":[{"id":"what-you-need-before-installing","text":"What you need before installing","level":2},{"id":"install-collabute-desktop-app","text":"Install Collabute desktop app","level":2},{"id":"first-sign-in","text":"First sign-in","level":2},{"id":"confirm-installation-succeeded","text":"Confirm installation succeeded","level":2},{"id":"if-installation-fails","text":"If installation fails","level":2}]},{"slug":"getting-started","href":"/getting-started","file":"getting-started.mdx","title":"Connect your first Collabute integration","sidebarTitle":"Getting Started","description":"Connect your first integration and validate end-to-end access.","icon":"lucide:rocket","raw":"$13","headings":[{"id":"step-1-confirm-your-role-and-permission","text":"Step 1: Confirm your role and permission","level":2},{"id":"step-2-open-integration-settings","text":"Step 2: Open integration settings","level":2},{"id":"step-3-connect-the-provider-account","text":"Step 3: Connect the provider account","level":2},{"id":"step-4-choose-who-can-use-it-admin-only","text":"Step 4: Choose who can use it (admin only)","level":2},{"id":"step-5-validate-with-a-quick-chat-test","text":"Step 5: Validate with a quick chat test","level":2},{"id":"setup-failure-checklist","text":"Setup failure checklist","level":2}]},{"slug":"developers","href":"/developers","file":"developers.mdx","title":"Collabute OpenAPI, MCP, and public API","sidebarTitle":"Developer resources","description":"OpenAPI spec, MCP server, public API, auth, and when to use Collabute from an agent.","icon":"lucide:code","raw":"$14","headings":[{"id":"when-to-use-collabute","text":"When to use Collabute","level":2},{"id":"how-to-call-collabute","text":"How to call Collabute","level":2},{"id":"public-api","text":"Public API","level":2},{"id":"mcp","text":"MCP","level":2},{"id":"onboarding","text":"Onboarding","level":2},{"id":"content-negotiation","text":"Content negotiation","level":2}]},{"slug":"integrations/vercel","href":"/integrations/vercel","file":"integrations/vercel.mdx","title":"Vercel deployments and runtime triage in Collabute","sidebarTitle":"Vercel","description":"Deployments, build logs, runtime incidents, and preview checks.","icon":"/icons/vercel.svg","raw":"$15","headings":[{"id":"best-for","text":"Best for","level":2},{"id":"requirements","text":"Requirements","level":2},{"id":"connect-vercel","text":"Connect Vercel","level":2},{"id":"validate-connection","text":"Validate connection","level":2},{"id":"what-you-can-do","text":"What you can do","level":2},{"id":"common-issues","text":"Common issues","level":2},{"id":"prompt-quality-tips","text":"Prompt quality tips","level":2}]},{"slug":"integrations/google","href":"/integrations/google","file":"integrations/google.mdx","title":"Google calendar and email context in Collabute","sidebarTitle":"Google","description":"Calendar and email context in Collabute.","icon":"/icons/google.svg","raw":"$16","headings":[{"id":"best-for","text":"Best for","level":2},{"id":"requirements","text":"Requirements","level":2},{"id":"connect-google","text":"Connect Google","level":2},{"id":"validate-connection","text":"Validate connection","level":2},{"id":"common-issues","text":"Common issues","level":2}]},{"slug":"integrations/linear","href":"/integrations/linear","file":"integrations/linear.mdx","title":"Linear issues and meeting follow-through in Collabute","sidebarTitle":"Linear","description":"Issue and task workflows tied to your meeting outcomes.","icon":"/icons/linear.svg","raw":"$17","headings":[{"id":"best-for","text":"Best for","level":2},{"id":"requirements","text":"Requirements","level":2},{"id":"connect-linear","text":"Connect Linear","level":2},{"id":"validate-connection","text":"Validate connection","level":2},{"id":"team-configuration-note","text":"Team configuration note","level":2},{"id":"common-issues","text":"Common issues","level":2}]},{"slug":"integrations/slack","href":"/integrations/slack","file":"integrations/slack.mdx","title":"Slack channel and thread context in Collabute","sidebarTitle":"Slack","description":"Conversation context and communication workflows.","icon":"/icons/slack.svg","raw":"$18","headings":[{"id":"best-for","text":"Best for","level":2},{"id":"requirements","text":"Requirements","level":2},{"id":"connect-slack","text":"Connect Slack","level":2},{"id":"validate-connection","text":"Validate connection","level":2},{"id":"common-issues","text":"Common issues","level":2},{"id":"prompt-quality-tips","text":"Prompt quality tips","level":2}]},{"slug":"integrations/coding-tools","href":"/integrations/coding-tools","file":"integrations/coding-tools.mdx","title":"Connect coding agents to Collabute MCP","sidebarTitle":"MCP","description":"Connect Codex, Cursor, Claude, and other coding assistants to Collabute context.","icon":"lucide:bot","raw":"$19","headings":[{"id":"supported-agents","text":"Supported agents","level":2},{"id":"before-you-connect","text":"Before you connect","level":2},{"id":"set-up-your-agent","text":"Set up your agent","level":2},{"id":"claude-code","text":"Claude Code","level":3},{"id":"codex","text":"Codex","level":3},{"id":"hermes-agent","text":"Hermes Agent","level":3},{"id":"cursor","text":"Cursor","level":3},{"id":"opencode","text":"OpenCode","level":3},{"id":"openclaw","text":"OpenClaw","level":3},{"id":"amp","text":"Amp","level":3},{"id":"use-it","text":"Use it","level":2},{"id":"troubleshooting","text":"Troubleshooting","level":2},{"id":"i-cannot-sign-in","text":"I cannot sign in","level":3},{"id":"the-agent-cannot-connect","text":"The agent cannot connect","level":3},{"id":"the-agent-has-no-useful-context","text":"The agent has no useful context","level":3},{"id":"tips","text":"Tips","level":2}]},{"slug":"troubleshooting","href":"/troubleshooting","file":"troubleshooting.mdx","title":"Fix Collabute connection and empty-data issues","sidebarTitle":"Troubleshooting","description":"Fix common connection, permission, and data issues.","icon":"lucide:wrench","raw":"$1a","headings":[{"id":"quick-diagnosis-order","text":"Quick diagnosis order","level":2},{"id":"integration-shows-not-connected","text":"Integration shows \"Not connected\"","level":2},{"id":"you-dont-have-access-error","text":"\"You don't have access\" error","level":2},{"id":"no-data-appears-in-chat","text":"No data appears in chat","level":2},{"id":"prompts-are-too-broad","text":"Prompts are too broad","level":2},{"id":"vercel-specific-issues","text":"Vercel-specific issues","level":2},{"id":"linear-specific-issues","text":"Linear-specific issues","level":2},{"id":"slack-specific-issues","text":"Slack-specific issues","level":2},{"id":"google-specific-issues","text":"Google-specific issues","level":2},{"id":"when-to-contact-support","text":"When to contact support","level":2}]}],"searchDocuments":[{"id":"/","title":"Docs map for Collabute product teams","sidebarTitle":"Overview","description":"See the docs map, access model, and recommended reading order.","href":"/","headings":"Documentation map Integrations currently covered Access model Recommended reading order Questions","body":"$1b"},{"id":"/installation","title":"Install Collabute and complete first sign-in","sidebarTitle":"Installation","description":"Install Collabute and complete first sign-in before integration setup.","href":"/installation","headings":"What you need before installing Install Collabute desktop app First sign-in Confirm installation succeeded If installation fails","body":"$1c"},{"id":"/getting-started","title":"Connect your first Collabute integration","sidebarTitle":"Getting Started","description":"Connect your first integration and validate end-to-end access.","href":"/getting-started","headings":"Step 1: Confirm your role and permission Step 2: Open integration settings Step 3: Connect the provider account Step 4: Choose who can use it (admin only) Step 5: Validate with a quick chat test Setup failure checklist","body":"$1d"},{"id":"/developers","title":"Collabute OpenAPI, MCP, and public API","sidebarTitle":"Developer resources","description":"OpenAPI spec, MCP server, public API, auth, and when to use Collabute from an agent.","href":"/developers","headings":"When to use Collabute How to call Collabute Public API MCP Onboarding Content negotiation","body":"$1e"},{"id":"/integrations/vercel","title":"Vercel deployments and runtime triage in Collabute","sidebarTitle":"Vercel","description":"Deployments, build logs, runtime incidents, and preview checks.","href":"/integrations/vercel","headings":"Best for Requirements Connect Vercel Validate connection What you can do Common issues Prompt quality tips","body":"$1f"},{"id":"/integrations/google","title":"Google calendar and email context in Collabute","sidebarTitle":"Google","description":"Calendar and email context in Collabute.","href":"/integrations/google","headings":"Best for Requirements Connect Google Validate connection Common issues","body":"$20"},{"id":"/integrations/linear","title":"Linear issues and meeting follow-through in Collabute","sidebarTitle":"Linear","description":"Issue and task workflows tied to your meeting outcomes.","href":"/integrations/linear","headings":"Best for Requirements Connect Linear Validate connection Team configuration note Common issues","body":"$21"},{"id":"/integrations/slack","title":"Slack channel and thread context in Collabute","sidebarTitle":"Slack","description":"Conversation context and communication workflows.","href":"/integrations/slack","headings":"Best for Requirements Connect Slack Validate connection Common issues Prompt quality tips","body":"$22"},{"id":"/integrations/coding-tools","title":"Connect coding agents to Collabute MCP","sidebarTitle":"MCP","description":"Connect Codex, Cursor, Claude, and other coding assistants to Collabute context.","href":"/integrations/coding-tools","headings":"Supported agents Before you connect Set up your agent Claude Code Codex Hermes Agent Cursor OpenCode OpenClaw Amp Use it Troubleshooting I cannot sign in The agent cannot connect The agent has no useful context Tips","body":"$23"},{"id":"/troubleshooting","title":"Fix Collabute connection and empty-data issues","sidebarTitle":"Troubleshooting","description":"Fix common connection, permission, and data issues.","href":"/troubleshooting","headings":"Quick diagnosis order Integration shows \"Not connected\" \"You don't have access\" error No data appears in chat Prompts are too broad Vercel-specific issues Linear-specific issues Slack-specific issues Google-specific issues When to contact support","body":"$24"}],"currentHref":"/api-reference","activeTab":"API Reference","children":"$L25"}]