Skip to content
Internal to Plabs — sign in with your Lark account

Give your AI tools the run of Lark

One URL turns Claude, Codex or Cursor into something that can read and edit the Plabs workspace — wiki pages, docs, sheets, Base tables — as you, only where you are allowed, and always on the record.

As you
your Lark permissions
41 tools
8 toolsets, per person
Scoped
writes stay in your projects
  • Wiki
  • Docs
  • Sheets
  • Base
  • Whiteboards
  • Slides
  • Messenger
  • Calendar
  • Claude Code
  • Claude Desktop
  • Codex
  • Cursor
  • VS Code

Three guarantees

Broad reach, narrow blast radius

An agent with a workspace-wide token is a liability. These three limits are enforced in code on every single call, not written down as policy.

It acts as you, not as an app

Every call to Lark uses your own credentials, so your agent sees exactly what you see and nothing you cannot. No shared service account with the run of the workspace.

user_access_token · never leaves the server

Edits stay inside your projects

An admin assigns you project folders. Anything inside them is yours to change; a write anywhere else is refused before it reaches Lark — including via a shortcut to a file that lives elsewhere.

assigned folders and their descendants

Nothing happens off the record

Tool, outcome, duration and a redacted copy of the arguments, for every call. Long strings are truncated, so the log stays a log instead of quietly becoming a second copy of your documents.

visible to you and to admins

One command

Setup is a copy and a paste

No API key to rotate, no client id to keep. Your client registers itself, sends you through Lark once, and remembers. The dashboard has the exact snippet for Claude Code, Codex, Cursor and VS Code.

terminal
# once, in any terminal
claude mcp add --transport http plabs-lark \
  https://mcp.dev-plabs.id/api/mcp

# sign in with Lark when prompted, then just ask
> what changed in the GRAB project brief this week?
> add a row to the sprint tracker for the new API task
> summarise the last 20 messages in #design-review
41
tools across the workspace
8 toolsets · 21 of them write
1
sign-in, then never again
refreshed in the background
0
Lark tokens in your AI client
held server-side, never forwarded
100%
of calls logged
arguments redacted, not stored whole

Stop pasting Lark into chat windows.

Sign in with Lark, copy one line into your client, and ask it about your projects directly.