hasarakMinimalModern

Integrations

Your workspace is an MCP server.

Add your workspace's /mcp URL to any MCP client. It signs in with OAuth as you and gets one typed API for channels, threads, the inbox, pages and every installed connector.

Start freeAll integrations

MCP in Hasarak

  • Built in, on every workspace

    app /mcp

    The server answers at <api url>/w/<workspace id>/mcp over Streamable HTTP. There is nothing to install or host.

  • OAuth sign-in

    Clients register themselves and open Hasarak's sign-in page. Tokens act as the member who signed in, with the same access checks as the apps.

  • Code mode

    One execute tool runs a short TypeScript program in a sandboxed Worker, so a client can do many calls in one step instead of dozens of round trips.

  • Connectors included

    Installed connectors' tools appear next to the built-ins: tools.github.pulls.get(…), tools.linear.issues.get(…).

What the Hasarak MCP server is

The Model Context Protocol is an open standard for letting programs and editors talk to tools. Every Hasarak workspace speaks it at /w/<workspace id>/mcp on its API URL. Any MCP client can use it: an editor extension, a CLI, a script of your own.

Connect a client

Add the URL to your MCP client. On first use the client registers itself (dynamic client registration), opens Hasarak’s sign-in page in your browser and gets an access token that lasts an hour, plus a refresh token. Changing your password signs every MCP client out.

Code mode instead of a hundred tools

The server lists a single tool, execute. A client sends it the body of an async function, and the program sees one global, tools:

  • tools.search({ query }) and tools.describe({ path }) find tools and their TypeScript types.
  • tools.hasarak.* covers the workspace: channels, messages, replies, reactions, the inbox, people and pages.
  • tools.<connector>.* are the tools of each connector you’ve installed.

A program like “post the open PRs linked in #platform this week to a page” is one execute call that runs next to your data, not a long back-and-forth.

Connect Claude Code or Cursor

Step-by-step setup is in the docs; what the server can do, with client configs and a comparison with Slack’s MCP server, is on the MCP page.

Use it for scripts and automation

Because the MCP server acts as you, it’s a convenient way to wire up your own tooling: post a deploy note from CI, keep a release page in sync, or export a channel’s decisions into docs. If you need something that reacts to events in the workspace, build a custom connector instead.

For how this compares with other ways of giving an agent access to team chat, Slack’s included, read the guide How to give an AI agent access to your team chat with MCP.

Related

Your workspace is an MCP server.

Start free