Plixlab

com.plixlabPublished by plixlab.comOfficial publisherv1.0.2Updated Oct 25, 2026

Executable presentations: build, compute and share plixes, decks whose slides Python cells compute.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowData & Analytics

Overview

AI-generated overview

Plixlab is a remote MCP server for building, computing and sharing executable presentations whose slides contain Python cells.

What you can do
Build executable presentations, called plixes, whose slides contain Python cells that compute content. Compute the Python cells inside those slides. Share the resulting presentations. No individual tools are listed in the manifest, so the exact operations available are not documented here.
When to use it
Consider it when you want an assistant to help assemble or run data-driven slide decks where Python code produces the content, rather than static slides.
Requirements
A remote MCP endpoint at mcp.plixlab.com over streamable HTTP. OAuth authentication is required, so a Plixlab account and sign-in are needed. No environment variables or headers are declared.
Before you install
OAuth grants the server access tied to your Plixlab account, so review the scopes requested at sign-in. Slides run Python cells, which may execute code you or the assistant supply; treat that as running code. Sharing presentations may expose their contents to others.

Installation

In SourceWeft

  1. Open Plixlab 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/com.plixlab%2Fplixlab/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": {
    "plixlab": {
      "type": "http",
      "url": "https://mcp.plixlab.com/"
    }
  }
}

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.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.