Plero

ai.pleroPublished by plero.aiOfficial publisherv2026.10.18Updated Oct 24, 2026

Operating system for creative companies: clients, projects, estimates, contracts, invoices, talent

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Plero is a remote MCP server for a creative-business management platform covering clients, projects, estimates, contracts, invoices and talent.

What you can do
Manage clients and talent records in a creative company's workspace. Work with projects and estimates. Handle contracts and invoices. The manifest lists no individual tools, so the exact actions available to an assistant are not documented here.
When to use it
Consider it when a creative agency or studio already runs its client, project, estimate, contract and invoice work on Plero and wants an assistant to work with that data.
Requirements
A remote endpoint at plero.ai over streamable HTTP; OAuth authentication is required. No environment variables or headers are declared. An existing Plero account is implied.
Before you install
OAuth grants the assistant access to business records such as clients, contracts and invoices; scope the authorization carefully. The listed areas include financial and contractual data, and tools may create or change records, though no tool list is provided to confirm.

Installation

In SourceWeft

  1. Open Plero 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.plero%2Fplero/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": {
    "plero": {
      "type": "http",
      "url": "https://plero.ai/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

9
  1. v2026.10.18LatestOct 13, 2026
  2. v2026.10.17Oct 8, 2026
  3. v2026.10.16Oct 8, 2026
  4. v2026.10.14Oct 8, 2026
  5. v2026.10.12Oct 7, 2026
  6. v2026.10.10Oct 7, 2026
  7. v2026.10.9Oct 6, 2026
  8. v2026.10.6Oct 6, 2026
  9. v2026.7.18Sep 16, 2026

Score

56% 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

    Publish an icon in the registry entry.

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