Integrations
Connect business apps, discover MCP tools and install plugins with skills for your team.
Integrations connect hlix to the services your team uses for code, issues and communication. The Integrations screen brings native business apps, MCP tools and plugin bundles together, with setup and permissions appropriate to each connection.
Prerequisites
Section titled “Prerequisites”- A hlix Workspace, and agency
owneroradmin— connecting and revoking an installation is Workspace administration - Permission to authorize the service you are connecting. Telegram uses a one-time chat link code.
What each one does
Section titled “What each one does”| Integration | Direction | hlix reads | hlix writes back |
|---|---|---|---|
| GitHub | inbound + outbound | granted repositories, branches and newly opened issues | cycle branches and commits, delivered to the preview branch behind one long-lived pull request per project |
| Linear | inbound + outbound | selected team/project issues and their context, plus delegated issues | agent activities for delegated sessions |
| Slack | inbound + outbound | DMs and @mentions in channels the bot is in |
replies and tool activity cards |
| Telegram | inbound + outbound | messages in a linked chat | the agent’s replies in the chat |
Projects can use a managed repository or connect GitHub for your team’s repository and pull-request workflow.
Choose the right connection
Section titled “Choose the right connection”| Type | Purpose | Where to configure it |
|---|---|---|
| Native business app | Managed events, issue sources, repositories or chats | Integrations; each project chooses how to use the workspace connection |
| MCP tool | Tools a coding agent can call during a run | Integrations → Agent tools & plugins; project MCP resources remain in the project’s Environment |
| Plugin | A versioned bundle of MCP tools, skill files and setup instructions | Integrations → Import plugin; choose all or selected projects |
| AI account | Model access and account credentials | Models & accounts |
| App with access to hlix | An outside app authorized to operate hlix | Apps with access to Hlix |
Browse lists native business apps and tools from the official MCP Registry. Open an entry for its provider’s setup requirements. Connected manages installed accounts, bundles, custom MCP servers and web-search providers.
Search MCP servers directly in the Agent tools & plugins section by server or publisher name. Open a result to read its repository README, review setup options and follow its source links. Public GitHub READMEs display inside the detail page; other repositories link to their documentation. Returning to the catalog preserves your search.
A plugin’s tools and skills become available when a new run starts in a selected project. Updates, disabling and removal also apply to subsequent runs. Complete the provider’s setup before using its tools.
Import plugin → Upload ZIP accepts Claude Code plugin layouts (.claude-plugin/plugin.json, .mcp.json, and skill folders) or Agent Skills folders containing SKILL.md and supporting text files. Review the detected tools and skills, enter the setup credentials and choose projects. Advanced JSON accepts the Hlix bundle format for custom tooling.
Enter single-line credential values through the plugin’s setup inputs. Keep the manifest free of credentials; skill documentation and supporting files can include template examples.
skills.sh is a discovery source for reusable Agent Skills. Upload a ZIP containing the chosen skill’s SKILL.md and supporting text files.
To import local files, see Move an existing project to hlix. To connect your AI assistant to your Workspace, use the hosted Hlix MCP server.
Building your own
Section titled “Building your own”Use the dashboard or each integration’s documented connection flow for authorization. Linear source settings, synced issues and plugin management are available through the API reference and TypeScript, Python and Go SDKs.
If an integration will not connect
Section titled “If an integration will not connect”- Permission error: use an agency account with the
owneroradminrole. - Authorization did not complete: restart the connection from Integrations and follow the provider’s sign-in flow.
- Connected chat does not answer: confirm the installation is active and the bot can read the conversation. See the Slack or Telegram guide for chat access.
- Repeated connection failure: contact support with the provider name and the error shown.