Put your agents where the team already talks.
Free for up to 10 members. The MCP server is on every plan.
MCP server for team chat
Every Hasarak workspace is a remote MCP server. Add one URL, sign in with OAuth, and your AI tools read threads, post updates and write docs as you. Nothing to host, no app to register.
Add your workspace's MCP URL to the client as a remote (Streamable HTTP) server.
The client registers itself and opens Hasarak's sign-in page. No app to create, no key to paste.
“Summarise the #platform thread and write it up as a page.” The client does it as you, with your access.
Claude Code
claude mcp add --transport http hasarak https://api.hasarak.com/w/<workspace id>/mcpCursor, in .cursor/mcp.json
{
"mcpServers": {
"hasarak": { "url": "https://api.hasarak.com/w/<workspace id>/mcp" }
}
}What a client sends: one execute call
// Read a thread, write it up as a page, and reply with the page's title.
const { items } = await tools.hasarak.replies.list({ messageId });
const body = items.map((r) => `- ${r.text}`).join("\n");
const page = await tools.hasarak.pages.create({ title: "2.14 canary notes", body });
await tools.hasarak.replies.send({ messageId, text: `Notes are in the page ${page.title}` });Channels, threads, DMs you're in, the inbox, people, search and pages: what you can see, your tools can see.
Send messages and thread replies, react, upload files, create and update pages. Everything is labelled as you.
The server lists a single execute tool. The client sends a short TypeScript program that makes dozens of calls in one step, next to your data.
Tools from the connectors your workspace installs show up next to the built-ins, and connectors can bring skills too.
Each program runs in a fresh, isolated Worker with no network access, an empty environment and limits of 30 seconds and 200 tool calls.
Tokens act as the member who signed in, with the same access checks as the web app. Changing your password signs every client out.
| Hasarak | Slack's MCP server | |
|---|---|---|
| Clients that can connect | Any MCP client with remote servers | Clients built on a registered Slack app |
| Sign-in | OAuth with dynamic client registration | OAuth with a fixed Slack app client ID |
| Admin approval per client | — | ✓ |
| Many calls in one step | Code mode | Separate tool calls |
An MCP (Model Context Protocol) server lets AI tools such as Claude Code or Cursor read and act on another app. A team chat MCP server gives them your channels, threads and docs, so an agent can catch up on a discussion, post an update or write a summary where the team will see it.
Clients that support remote MCP servers over Streamable HTTP with OAuth sign-in, for example Claude Code, Cursor and the MCP Inspector. The server speaks MCP protocol versions 2024-11-05 to 2025-11-25.
It is https://api.hasarak.com/w/<workspace id>/mcp. The setup docs walk through it, step by step.
If you want an MCP server your whole team can connect to without registering an app, yes. Slack's MCP server only accepts clients built on a registered Slack app that an admin approves; Hasarak's accepts any MCP client that signs in as a member of the workspace.
Whatever you can do in the workspace: read the channels and DMs you're in, post and reply, react, and create and edit pages. It can't do anything you can't, and you can sign every client out by changing your password.
Yes. Every workspace has one, on every plan.
Free for up to 10 members. The MCP server is on every plan.