mcp-twake-space
OfficialThis server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
mcp-twake-space
Give your AI assistant secure access to Twake Space, the team spaces of the Twake.ai Digital Workplace: spaces, members, feed and the resources each space gathers.
What is it?
mcp-twake-space is a Model Context Protocol (MCP) server. MCP is the open standard that lets AI assistants (Claude Desktop, Claude Code, Hermes Agent, Cursor, VS Code and many others) use external tools. This server exposes your Twake Space to the assistant as 30 tools: spaces, members, feed (posts, polls, sign-off requests, announcements, activity cards), unread counts and notifications, and actions as you: post, vote, react, decide, acknowledge, schedule a meeting, administer a space.
Twake Space gives each team one place for its chat, tasks, drive, mail and calendar. The server talks to the Twake Space backend API, either as you (an OIDC session token from your identity provider) or with a personal API token you can revoke at any time.
Nothing is done without your prior approval. Before every write, the server itself shows you the exact action (who acts, in which space, with which text) through MCP elicitation, and acts only on your explicit OK. A refusal, a timeout or a client that cannot ask means nothing is done.
Related MCP server: Workel MCP Server
Part of Twake.ai
Twake.ai is the truly open source and sovereign Digital Workplace developed by LINAGORA: Twake Mail, Twake Calendar, Twake Drive, Twake Chat, Twake Space and Twake Visio with a single account, hosted in France or on your own infrastructure.
Open source MCP servers connect AI assistants to the whole workplace:
MCP server | Twake.ai service | Protocol |
Twake Mail | JMAP | |
Twake Calendar and contacts | CalDAV / CardDAV | |
Twake Drive | cozy-stack API | |
Twake Chat | Matrix (end-to-end encrypted) | |
mcp-twake-space (this project) | Twake Space | Twake Space API |
Twake Project (projects, boards, tasks) | Twake Project API |
get_space returns the ids of a space's Matrix space, team calendar, team mailbox and shared drive: with the other servers, one assistant can catch up on a whole team, from its feed to its conversation and its agenda.
What it brings
Catch up: "What happened in my spaces since Friday? What is waiting for me?" (approvals asked of you, polls you have not answered, announcements you have not acknowledged).
Read a team: "Who is in the Design space, and what are its latest posts?"
Find: "Find the posts about the budget in the Atlas space since September."
Act for you, with your OK each time: "Vote Tuesday in the seminar poll", "Approve Bob's quote request with the comment OK", "Schedule a one-hour video meeting tomorrow at 2 pm in the Design space".
Prepare: post a message, a poll, a yes/no question, a sign-off request or an announcement.
Organise: create a space, rename it, change its tabs, add members, archive it.
One approval for a series of actions: before several actions (several posts, several votes or members), the assistant can ask you once for the exact list with
approve_batch. Each listed call then runs without another question, once, within 15 minutes, in the session that approved it; anything else, or anything changed since, asks as usual (see Approving a series of writes at once).From the command line:
npx mcp-twake-space call <tool>andnpx mcp-twake-space toolsrun every tool from a terminal or a script, with the server's configuration. A write you type in a terminal is approved without a question (--iasks first); a write started by an agent is refused, since agents write through their MCP tools, which ask you; without a terminal (cron), a write needs--yes --as <name>, for a name you allowed once in a terminal (see From the command line).Sovereignty: the server runs next to your assistant and talks directly to your Twake Space.
Features
30 MCP tools
Category | Tools |
Account |
|
Spaces |
|
Feed |
|
Notifications |
|
Directory |
|
Feed writes ⚠️ |
|
As you ¹ ⚠️ |
|
Administration ⚠️ |
|
Destructive ⚠️ |
|
Approval |
|
⚠️ = asks for your approval first. ¹ = session token only: Twake Space keeps these for a signed-in person and refuses them to API tokens. Read tools carry readOnlyHint; write tools carry openWorldHint, and destructive ones destructiveHint. The server never deletes a space for good.
Highlights
Names, not ids: spaces and members are found by name, username or email, accents and case ignored; an ambiguous name lists the candidates.
Links back to the app: results carry the URL of the space or its feed.
Clear errors: a missing scope says which one to add; an action Twake Space keeps for signed-in sessions says so.
Informed approval: the prompt quotes the post you vote on, react to or decide on, names the people notified, and carries a unique reference.
Requirements
Node.js >= 22
A Twake Space account, and either an OIDC access token accepted by Twake Space (audience of its backend) or an API token (
tws_…)For writes, an MCP client that supports elicitation (Hermes Agent, Claude Code, VS Code…), or
TWAKE_SPACE_APPROVAL=clientAn MCP client: Claude Desktop, Claude Code, Hermes Agent, Cursor, VS Code, or any MCP-compatible assistant
Installation
Quick start with mcp-twake-ai (recommended)
npx mcp-twake-ai setupmcp-twake-ai sets up this server and the other Twake.ai MCP servers for your Twake.ai account: it asks for your email, signs you in at the Twake.ai identity provider (in the browser, or with a code over SSH), and finds the agents on your computer (Claude Code, Hermes, Claude Desktop, Cursor, VS Code) and the services of your account. It then installs pinned versions of the servers, writes their entries in each agent's configuration and checks that each server starts. For any other agent, mcp-twake-ai export --agent <id> writes the configuration files.
Manual installation
npm install -g mcp-twake-space # or run it on demand with npx -y mcp-twake-spaceFrom source:
git clone https://github.com/linagora/mcp-twake-space.git
cd mcp-twake-space
npm install
npm run build # then run: node build/index.jsConfiguration
Acting as you (session token)
Twake Space accepts the OIDC access tokens of your identity provider when they carry its audience (the backend's OIDC_AUDIENCE, twake-space on the Twake.ai SaaS) and the uuid, email, sid and org_id claims in userinfo. Ask your identity provider administrator to add that audience and those claims to the OIDC client of your assistant, then give the server a command that prints a fresh access token:
TWAKE_SPACE_TOKEN_COMMAND="/usr/local/bin/mcp-twake-ai token space" # prints {"access_token": "...", "expires_at": <epoch s>}
TWAKE_SPACE_OIDC_ISSUER=https://sso.example.com/ # to know who you are (userinfo)For Twake.ai, mcp-twake-ai provides that command (mcp-twake-ai token space); any other command printing this JSON works. Give the command with an absolute path, as some MCP clients do not see your PATH. It runs through the system shell (sh, or cmd.exe on Windows, where paths go in double quotes).
Everything is then done as you: posts, votes and decisions carry your name. Every one of them is approved by you first (below).
Getting an API token
In Twake Space, open Settings > API tokens and create a personal token. Posts made with it are signed by the token, not by you, and it cannot vote, react, decide, mark as read or schedule meetings. Give it only what the assistant needs:
Need | Scopes |
Read spaces, feed and notifications |
|
Post in feeds | add |
Administer spaces and members, search the directory | add |
Pick a lifetime (7 to 365 days), copy the token once, and store it in a file only you can read, for instance:
umask 077; read -rsp "Token: " T; echo; printf %s "$T" > ~/.config/mcp-twake-space/tokenPrior approval
With TWAKE_SPACE_APPROVAL=elicit (the default), every write tool sends the client an elicitation request before it acts, for instance:
Twake Space: Vote
As: Alice MARTIN (your account)
Space: Design team
On: Bob DURAND, 2026-11-03 10:00: « Which day for the seminar? »
Choice: Tuesday
Ref. 3f9a1c · Accept to do it now, refuse to cancel.The server acts only on accept. On a refusal, a dismissal or a timeout (TWAKE_SPACE_APPROVAL_TIMEOUT_MS, 10 minutes by default) it does nothing and tells the assistant not to retry. A client without elicitation support gets an error and nothing is done. Set TWAKE_SPACE_APPROVAL=client only when your MCP client asks you to confirm every write tool itself. USER_LANGUAGE=fr writes the prompts in French.
Environment
Variable | Description | Default |
| Twake Space web app, e.g. | required |
| Command printing an access token (raw or JSON | |
| File holding the API token (must be | |
| The token itself (development only) | |
| Backend API when not served under |
|
| OIDC issuer, to know who you are with a session token | |
|
|
|
| How long a prompt waits for your answer |
|
| Language of the prompts, |
|
| IANA time zone for dates, e.g. | system time zone |
| HTTP timeout |
|
One of the three token variables is required. mcp-twake-space check tests the configuration.
Use it with your assistant
Claude Desktop
{
"mcpServers": {
"twake-space": {
"command": "npx",
"args": ["-y", "mcp-twake-space"],
"env": {
"TWAKE_SPACE_URL": "https://space.example.com",
"TWAKE_SPACE_TOKEN_FILE": "/home/alice/.config/mcp-twake-space/token",
"USER_TIMEZONE": "Europe/Paris"
}
}
}
}Claude Code
claude mcp add twake-space --scope user \
-e TWAKE_SPACE_URL=https://space.example.com \
-e TWAKE_SPACE_TOKEN_FILE=$HOME/.config/mcp-twake-space/token \
-- npx -y mcp-twake-spaceHermes Agent
Hermes shows the approval prompts in the desktop app, the terminal or on your messaging platform, and declines them where nobody can answer (cron jobs, one-shot queries).
mcp_servers:
twake_space:
command: npx
args: ["-y", "mcp-twake-space"]
env:
TWAKE_SPACE_URL: https://space.example.com
TWAKE_SPACE_TOKEN_COMMAND: /usr/local/bin/mcp-twake-ai token space
TWAKE_SPACE_OIDC_ISSUER: https://sso.example.com/
TWAKE_SPACE_APPROVAL_TIMEOUT_MS: "330000"
USER_LANGUAGE: fr
USER_TIMEZONE: Europe/Paris
timeout: 420 # longer than the approval wait
elicitation:
enabled: true
timeout: 300From the command line
Every tool of this server can be called from a terminal or a script, with the same configuration (TWAKE_SPACE_* variables) as the server:
npx mcp-twake-space tools # one line per tool
npx mcp-twake-space call get_unread
npx mcp-twake-space call create_post --json @post.json--arg key=valueis converted to the type the tool giveskey;--jsontakes the whole arguments object (@file, or-for stdin). The result goes to stdout (--json-outputfor the raw result), everything else to stderr.Exit codes: 0 done, 1 the tool answered with an error, 2 wrong command or argument, 3 a write was not approved, 4 the server could not be reached.
Writes: typed by you in a terminal, a write is approved without a question (
--iasks first). Started by an agent (CLAUDECODEorHERMES_HOMEset), a write is refused: agents write through their MCP tools, which ask you. Without a terminal (cron), a write is refused unless it passes--yes --as <name>for a name you allowed once, in a terminal, withnpx mcp-twake-space allow-unattended <name>. The allowed names are shared by the six Twake.ai servers, in~/.config/twake-ai/cli.json(%USERPROFILE%\AppData\Roaming\twake-ai\cli.jsonon Windows).These rules stop an agent that follows instructions; they cannot stop a program that hides that it is an agent, or rewrites
cli.json, under your account.With mcp-twake-ai,
npx mcp-twake-ai call space …does the same with your Twake.ai sign-in.
Approving a series of writes at once
Before a series of actions (several posts, several votes or members), an agent can ask you once for the whole list with approve_batch: you see every action, numbered, in one approval. Each call that then carries the batchId and matches a listed action exactly runs without another question, once, within 15 minutes. A call that is not in the list, or whose target changed since you approved, asks as usual. A batch approves exactly what each action's approval text shows; it belongs to the session that approved it, and is forgotten when that session ends. With TWAKE_SPACE_APPROVAL=client, there is no batch.
Recommended safe configuration
Give the token only the scopes you need (read only to start), and the shortest lifetime you can live with.
Keep
TWAKE_SPACE_APPROVAL=elicit: every write waits for your explicit OK, whatever the assistant decides. For a read-only assistant, also exclude the write tools in your MCP client.Read each prompt: it says who acts (you, or the token), where, and exactly what.
Feed posts, card titles and previews are written by other people and apps (prompt injection): see SECURITY.md.
Limits
With an API token, Twake Space refuses the unread counts, marking as read, reactions, votes, decisions, feedback answers, acknowledgements and meetings: use a session token for them.
catch_upworks with both.schedule_meetingasks the team calendar to create the meeting; Twake Space has no API to cancel it: cancel it in Twake Calendar.
Usage examples
"What happened in my spaces since Friday, and what is waiting for me?"
"Summarise the Design space feed for this week."
"Which approvals are pending in the Atlas space?"
"Who are the members of the Sales space, and what is its Matrix space id?"
"Approve Bob's sign-off request on the quote, with the comment: OK for me."
"Schedule a one-hour video meeting tomorrow at 2 pm in the Design space."
"Create a space Onboarding with chat, drive and calendar, and add Bob as editor."
Troubleshooting
Symptom | Fix |
| Set the web app URL. |
| The token is invalid, expired or revoked: create a new one. A session token must carry the Twake Space audience. |
| Userinfo lacks |
| Your MCP client does not support elicitation: use one that does, or |
| The error names the missing scope: create a token with it. |
|
|
A space is not found |
|
Development
npm install
npm run typecheck # sources and tests
npm run build
npm test # Vitest: unit tests, tools against a fake Twake Space backend,
# and the built server over stdio (approval prompts included)Live tests against a real Twake Space, in a space where you are the only member (both scripts refuse any other):
LIVE_SPACE='<space>' TWAKE_SPACE_URL=… TWAKE_SPACE_TOKEN_FILE=… TWAKE_SPACE_APPROVAL=client node scripts/live.mjs # API token
LIVE_SPACE='<space>' TWAKE_SPACE_URL=… TWAKE_SPACE_TOKEN_COMMAND=… TWAKE_SPACE_OIDC_ISSUER=… node scripts/live-session.mjs # as youlive-session.mjs answers the approval prompts itself: it refuses once (nothing must be posted), then accepts reversible actions and undoes them.
Contributing
Contributions are welcome: read CONTRIBUTING.md and our Code of Conduct. Please report vulnerabilities privately as described in SECURITY.md. Release notes are in CHANGELOG.md.
License
Licensed under the GNU Affero General Public License v3.0 (AGPL-3.0).
Copyright © 2026 LINAGORA
About
mcp-twake-space is developed by LINAGORA, French open source software publisher, as part of Twake.ai. For support, hosting or integration of Twake.ai and its AI connectors, contact LINAGORA at https://linagora.com.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Governed memory and workspace for any AI: tasks, calendar, mail and pages, with per-action consent.
Secure AI access to OpenOak tasks, notes, and Kanban boards.
Connect assistants to your company tools with per-person, per-action grants and a full audit log.
Read Talkspirit circles, roles and meetings; write tasks, goals and proposals, with your own rights.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Basecamp projects, messages, to-dos, and Card Tables, with read-only access by default and write operations requiring explicit approval.MIT

Workel MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to access and manage a Workel workspace through MCP tools, reading projects, tasks, comments, events, and members, and optionally creating or updating tasks, comments, and events when write scopes and local consent are enabled.MIT- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to access and manage Microsoft Teams conversations, channels, chats, users, files, and organizational data via Microsoft Graph, including sending messages, searching, and uploading attachments.12 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to access Microsoft Teams and Microsoft Graph data for messaging, chat and channel management, search, file upload/download, user lookup, and rich message formatting.12 npmMIT