> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kolaria.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations Overview

> Connect GitHub, Linear, Slack, Granola, Google Search Console, Framer, Raycast, and MCP servers to Kolaria

Integrations live at **Integrations** in the dashboard sidebar (`app.kolaria.com/{org-slug}/integrations`). The page has four tabs: **All**, **Input**, **Output**, and **Extensions**. Below the tabs, a section called **From the integration store** lists MCP servers published by the Kolaria community.

## Input sources

Input sources feed data into Kolaria. GitHub and Linear power the Studio content pipeline (changelogs, blog posts, social posts). Slack gives you a chat channel with the Kolaria agent. Granola brings meeting notes into chat and content workflows. Google Search Console feeds GEO prompt suggestions.

<CardGroup cols={2}>
  <Card title="GitHub" icon="github" href="/integrations/github">
    Install the Kolaria GitHub App and pick repositories. Commits, merged pull requests, and releases become changelogs, blog posts, and social posts.
  </Card>

  <Card title="Linear" icon="infinity" href="/integrations/linear" iconType="duotone">
    Authorize a Linear workspace with OAuth. Completed issues are a data source next to GitHub activity.
  </Card>

  <Card title="Slack" icon="slack" href="/integrations/slack">
    Install the Kolaria agent in your workspace. Mention it in a thread to chat, draft, and approve content from Slack.
  </Card>

  <Card title="Granola" icon="microphone" href="/integrations/granola">
    Connect Granola with an API key. The agent can read meeting notes, AI summaries, and transcripts.
  </Card>

  <Card title="Google Search Console" icon="google" href="/integrations/google-search-console">
    Turn the search queries you already rank for into suggested GEO prompts. Managed from the GEO Prompts page.
  </Card>
</CardGroup>

## Output destinations

<CardGroup cols={2}>
  <Card title="Framer" icon="square" href="/integrations/framer" iconType="duotone">
    Pull posts into a Framer site with the Kolaria plugin from the Framer Marketplace. Uses a read-only API key.
  </Card>
</CardGroup>

<Info>
  Framer is the only output integration in the dashboard today. Other publishing paths run through Kolaria itself: social posts publish to X and LinkedIn from the Content page, and any CMS can read posts through the [API](/api/getting-started).
</Info>

## Extensions

<CardGroup cols={2}>
  <Card title="Raycast" icon="terminal" href="/devtools/raycast">
    Search posts, copy content, and manage workflows from Raycast. The Integrations page shows a setup guide; the extension itself needs a read and write API key.
  </Card>
</CardGroup>

## MCP servers

The **MCP Servers** card on the Integrations page opens `integrations/mcp`, where you connect external MCP servers so the Kolaria agent can use their tools and data.

* **Custom servers**: add any remote MCP server by name and URL (`https://` is prepended for you). Authentication is one of **None** (public server), **Headers** (an API key, bearer token, or custom headers), or **OAuth** (you are redirected to the server to approve access, and Kolaria stores an encrypted refresh token and renews access automatically).
* **Integration store**: servers published by the Kolaria community appear under **From the integration store**. Connecting one either needs no credentials, asks for your own headers, or starts an OAuth flow, depending on how the listing was published. Deep links of the form `app.kolaria.com/{org-slug}/integrations/{listing-slug}` open the connect dialog for a listing directly.
* Kolaria tests the connection while you add a server. Each connected server can be enabled, disabled, deleted, or have its tool list refreshed from its card.

<Note>
  This is the reverse direction from Kolaria's own MCP server, which lets AI tools like Claude or Cursor call Kolaria. For that, see [MCP Server](/devtools/mcp).
</Note>

## Community integrations

<CardGroup cols={2}>
  <Card title="Featul" icon="list" href="/integrations/featul">
    Import Kolaria changelog content into Featul. Built and supported by Featul.
  </Card>

  <Card title="Kontentspace" icon="robot" href="/integrations/kontentspace">
    A former community connector for the Kolaria MCP. The service is no longer reachable.
  </Card>
</CardGroup>

## Content types from input sources

When you create content from GitHub or Linear activity, Kolaria can generate:

<Steps>
  <Step title="Changelog">
    Release notes grouped from merged pull requests, pushes, and releases.
  </Step>

  <Step title="Blog post">
    Long-form articles about a feature or release.
  </Step>

  <Step title="X post">
    Short updates announcing releases and features.
  </Step>

  <Step title="LinkedIn post">
    Professional updates about product and engineering progress.
  </Step>
</Steps>

Each repository you add through the GitHub App starts with changelog, blog post, and X post outputs enabled. LinkedIn posts and images are available when you create content or schedules.

## Getting started

<Steps>
  <Step title="Connect a source">
    Install the GitHub App, or connect Linear, and pick what Kolaria can read.
  </Step>

  <Step title="Generate content">
    Open **Content** and create a changelog, blog post, or social post from recent activity. Pick the repositories and Linear workspaces to include.
  </Step>

  <Step title="Automate">
    Use [schedules](/automation/scheduled) for recurring content, or [event triggers](/automation/event-based) that fire on GitHub webhooks.
  </Step>

  <Step title="Publish">
    Review drafts in the dashboard, publish social posts, or pull posts into Framer or your own site through the API.
  </Step>
</Steps>

## Permissions and security

<Note>
  * **Read access to your sources**: GitHub, Linear, Granola, and Google Search Console are read-only connections. Slack needs write access to post replies in threads.
  * **Selective access**: you choose which repositories the GitHub App can see, which Search Console property to analyze, and which Slack channels the agent may respond in.
  * **Encrypted credentials**: access tokens, API keys, webhook secrets, and MCP OAuth refresh tokens are encrypted at rest.
  * **Remove anytime**: every integration can be disabled or deleted from its page in the dashboard.
</Note>

## Next steps

<CardGroup cols={2}>
  <Card title="Connect GitHub" icon="github" href="/integrations/github">
    Install the GitHub App and pick repositories
  </Card>

  <Card title="Create automation" icon="wand-magic-sparkles" href="/automation/overview">
    Schedules and event triggers for generated content
  </Card>
</CardGroup>