Zine

ai.zinePublished by zine.aiOfficial publisherv1.0.1Updated Oct 24, 2026

Your memory, everywhere AI goes. Build knowledge once, access it via MCP anywhere.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Zine is a remote MCP server that gives an AI assistant access to a personal knowledge base built once and reused across AI tools.

What you can do
Connect an assistant to a personal knowledge base hosted by Zine, so stored knowledge can be reached from any MCP-capable AI tool. The manifest lists no individual tools, so the exact operations are not documented here. The stated purpose is to build knowledge once and access it via MCP wherever AI is used.
When to use it
Useful if you already keep knowledge in Zine and want AI assistants to draw on it from multiple tools instead of rebuilding context each time. Less relevant if you do not use Zine or need documented, tool-level capabilities.
Requirements
A remote MCP endpoint at zine.ai connected over streamable HTTP. OAuth authentication is required, so you need a Zine account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Before you install
Access is tied to your Zine account through OAuth, so review which permissions the sign-in grants. The server exposes your stored knowledge to connected AI tools; consider what personal or sensitive material the knowledge base holds before connecting assistants.

Installation

In SourceWeft

  1. Open Zine 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/ai.zine%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": {
    "zine": {
      "type": "http",
      "url": "https://www.zine.ai/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.1LatestSep 16, 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.