Zipline MCP

li.ziplinePublished by zipline.liOfficial publisherv1.0.0Updated Nov 4, 2026

One thread for every AI assistant you use. Share tasks and context across ChatGPT, Claude and Grok.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowAI & ML

Overview

AI-generated overview

Zipline MCP is a remote server that lets assistants share tasks and context across ChatGPT, Claude and Grok in one thread.

What you can do
  • The listing names no tools, so capabilities are known only from its short description.
  • It presents itself as one thread for every AI assistant you use.
  • It is meant to share tasks and context across ChatGPT, Claude and Grok, so work started in one assistant can carry over to another.
When to use it
Consider it if you regularly switch between ChatGPT, Claude and Grok and want tasks and context to follow you rather than being retyped in each assistant.
Requirements
A remote endpoint at zipline.li; nothing is installed locally. Sign-in with OAuth is required. No environment variables or headers are declared.
Before you install
OAuth grants the server access to your account, and shared threads mean conversation context is stored and passed between assistants and services. The listing gives no detail on what is stored or who can see it, so review the provider's privacy terms before sharing sensitive work.

Installation

In SourceWeft

  1. Open Zipline MCP 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/li.zipline%2Fzipline/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": {
    "zipline": {
      "type": "http",
      "url": "https://zipline.li/api/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.0.0LatestNov 4, 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.