Claude Code
CLI connector · Run Saung tools from your terminal
Saung
Bring Saung into the tools you already use. Connect your favorite AI clients and keep tasks, projects, context, and time in sync with the work.
Use Saung alongside the tools and agents you already work in. Choose a client below to see how to connect it.
CLI connector · Run Saung tools from your terminal
App connector · Add Saung in claude.ai or Claude Desktop
App connector · Add Saung as a connector
CLI connector · Run Saung tools from your terminal
App connector · Add Saung as a connector
CLI connector · MCP server in settings.json
App connector · Add Saung as an MCP server
App connector · Add Saung as a connector
Agent connector · Run Saung from your own agent
Coming soon · See your Google Calendar beside your tasks
Saung connects to AI clients through MCP, the open standard for giving agents access to external tools. Add a client once, sign in with your Saung account, and let it work with the context you keep in your workspace.
No schedules and no background agents. Every action starts from a prompt you write, and nothing runs while you are away.
Connecting a client opens a Saung sign-in. You can see every connected client and revoke any of them at any time from the Connectors page.
An agent sees only your own workspace, shared projects follow the same access you have, and your content is never used to train AI.
Full read and write access to the core of Saung, grouped by what you are working on.
Capture tasks, update them, schedule work onto your day, tag, and search.
Create projects, organize board sections, and move work to where it belongs.
Log time entries, correct them, and query any date range for reporting.
Leave notes on a task’s thread, edit them, or clean them up.
Read the context kept on a project and on the team behind it before acting, and write down what is worth keeping.
26 tools, read and write, scoped to your account.
One URL for every MCP client. Adding it opens a Saung sign-in popup, then your agent is connected.
Server URL:
https://saung.app/api/mcp/oauth
claude mcp add --transport http saung https://saung.app/api/mcp/oauth
Add a custom connector with the server URL. A Saung login popup opens to authorize, no token to copy.
Add a custom connector with the server URL. A Saung login popup opens to authorize.
codex mcp add saung -- npx -y mcp-remote https://saung.app/api/mcp/oauth
Add to ~/.gemini/settings.json. Gemini opens a login popup to authorize.
{
"mcpServers": {
"saung": { "httpUrl": "https://saung.app/api/mcp/oauth" }
}
}
Add Saung as a remote MCP server. ZCode opens a login popup to authorize.
Add to ~/.hermes/config.yaml. Hermes opens a login popup the first time, then refreshes on its own.
mcp_servers:
saung:
url: 'https://saung.app/api/mcp/oauth'
auth: oauth
enabled: true
oauth:
scope: 'openid profile email offline_access'Point any MCP client at the server URL over HTTP. Authorization happens through the same Saung login popup. Clients that cannot do OAuth can use a personal access token from Settings instead.
No. The Saung MCP server is human-driven by design: there are no schedules, no polling, and no background loops. An agent can only act inside a conversation you started, on the request you made.
Only your workspace: tasks, projects, board sections, time entries, comments, and the context documents kept on your projects and teams, scoped to your account. Projects shared with you follow the same access you already have. Your content is never sold, never used for ads, and never used to train AI. The privacy policy covers this in full.
Open the Connectors page in Saung. Every connected client is listed there and can be revoked with one click. Personal access tokens can be rotated or revoked from Settings.
No. The MCP server is part of Saung and free for personal use. You only pay whatever your AI provider charges for the assistant itself.
Free for personal use. Set up takes about a minute.