Tweek

so.tweekPublished by tweek.soOfficial publisherv1.3.2Updated Oct 24, 2026

Minimal weekly planner: read and manage your Tweek tasks and calendars.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Tweek is a remote MCP server that lets an assistant read and manage your tasks and calendars in the Tweek weekly planner.

What you can do
Tweek connects an assistant to the Tweek weekly planner. According to the registry description, it lets the assistant read and manage your Tweek tasks and calendars. The manifest lists no individual tools, so the exact set of operations is not documented here. It is a hosted remote endpoint rather than a local package.
When to use it
Use it when you plan your week in Tweek and want an assistant to view or update your tasks and calendar entries without switching apps. It suits people who already use Tweek as their planner.
Requirements
A remote MCP connection to the Tweek endpoint over streamable HTTP, plus OAuth sign-in with a Tweek account. No environment variables, headers or local runtime are declared.
Before you install
Access is granted through OAuth to your Tweek account, so the assistant may read and change your tasks and calendar data. Review what the OAuth consent grants before connecting, and check which write operations the assistant is allowed to perform.

Installation

In SourceWeft

  1. Open Tweek in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/so.tweek%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "tweek": {
      "type": "http",
      "url": "https://tweek.so/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.3.2LatestOct 13, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.