Litak

● Active

io.litak/mcp

Connect your Litak goals, habits, weekly plan and sleep with scoped OAuth or Bearer access.

Connect this server

One click to install, or copy the config below. Suits: Cursor · HTTP clients.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "mcp": {
      "url": "https://litak.io/mcp"
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --transport http mcp https://litak.io/mcp
VS Code
code --add-mcp '{"name":"mcp","type":"http","url":"https://litak.io/mcp"}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Productivity
Version
1.2.1
Registry
active
Published
11/18/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Mostly fine: Litak is maintained, hosted endpoint behind a sign-in.

Maintained
Active
Last commit 4 days ago (Nov 18, 2026), 0 open issues.
Official registry
Active
Published as io.litak/mcp in the official MCP registry, version 1.2.1.
Source
No licence found
Public repository, but GitHub reports no recognised licence (0 stars). Check the README before shipping it in a product.
Runs
Hosted by the publisher
Your client talks to litak.io: prompts and tool arguments leave your machine for that host.
Credentials
Sign-in required
The hosted endpoint answered 401/403 to a credential-free call (checked Nov 22, 2026): it wants an API key or an OAuth login first.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.

Live check

checked Nov 22, 2026, 00:07 UTCStatus history & uptime →
● Needs sign-in

The endpoint is up but wants a key or an OAuth sign-in before the handshake, so its tools can only be read with an account.

Checked by Serverdex with a plain initialize + tools/list call to litak.io/mcp, no credentials, about once a day. A failed check is never a removal.

On GitHub

read Nov 18, 2026
Stars
0
Forks
0
Last push
Nov 18, 2026
License
Other

From the README

Litak MCP Connection metadata and documentation for the hosted Litak Model Context Protocol server. MCP server: https://litak.io/mcp Transport: Streamable HTTP Authentication: OAuth with PKCE, or a dedicated Litak Bearer key. Add the server URL in your AI client and choose the permissions you want to grant. For key-based clients, create a key in Litak settings and store it in the client's secure configuration. Never paste keys into an AI conversation or commit them to a repository. See connection instructions and the Litak connection guide. Capabilities Available tools depend on the permissions granted to the connection. Writes require the matching read permission. Sleep has separate read/write permissions. Creating a task alone does not make it the main daily task. Missing sleep values mean no value was recorded, not zero hours. What this repository contains This repository contains only public connection metadata and documentation. The Litak application and MCP implementation remain private. No application source, private Git history, credentials, account records or database exports are included. This repository is not a self-hostable server or an open-source release. server.json is published in the official MCP Registry as io.litak/mcp, version 1.2.0. The domain was verified through HTTP. A registry listing is metadata, not a security review or endorsement.…

Read the full README on GitHub →

Remotes

  • streamable-httphttps://litak.io/mcp

The most-starred Productivity servers in the index, with their live-check result.

ServerStarsLast pushLive check
Front-End Checklist74,746Oct 2026Working
Windmill18,600Nov 2026Needs sign-in
Agent-Native Content7,735Nov 2026Needs sign-in
Agent-Native Calendar7,735Nov 2026Needs sign-in
Agent-Native Plan7,735Nov 2026Needs sign-in

Litak: questions people ask

Is Litak a remote or a local MCP server?
According to its entry in the official MCP registry, Litak ships as a hosted endpoint (streamable-http) that your client connects to by URL.
Does Litak need an API key or a sign-in?
Yes. Its hosted endpoint answered the credential-free Serverdex live check with HTTP 401/403 on Nov 22, 2026: it expects an API key in a header or an OAuth login before it lists its tools.
Is Litak safe to use?
Mostly fine: Litak is maintained, hosted endpoint behind a sign-in. In detail — maintained: Active; official registry: Active; source: No licence found; runs: Hosted by the publisher; credentials: Sign-in required. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is Litak still maintained?
Active: the repository's last commit 4 days ago. Last push Nov 18, 2026, 0 GitHub stars, Other licence. Read from GitHub on Nov 18, 2026.
How do I add Litak to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
Browse all Productivity →

Add the badge to your site

Show visitors that Litak is listed here — it’s also the link we check for a free listing.

Litak — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-litak-mcp?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Litak — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Litak — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-litak-mcp?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/io-litak-mcp) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/io-litak-mcp) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/io-litak-mcp)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/io-litak-mcp"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-litak-mcp"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-litak-mcp"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).