Plaro

io.github.plaro-krPublished by GitHub account plaro-krv1.2.1Updated Oct 29, 2026

Agreed client requirements, changes and open questions from Plaro, read by Claude Code and Codex.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Plaro's remote MCP server lets Claude Code and Codex read a project's agreed requirements, changes and open questions, and plan work against them.

What you can do
  • Read agreed requirements, requirement changes, open questions, verification gaps, change notices, and search requirements
  • Plan work for what changed, plan the whole current version, and compare acceptance criteria with the code before acceptance
  • Leave a question for the PM, report which requirements were built with the commit, and mark acceptance checks as passing on your own account
  • Receive a change notice on each message through the plugin's message hook
When to use it
Useful when a project's requirements live in Plaro and you want the coding assistant to check them before building, plan changes, or prepare for an acceptance check. Also fits teams where a PM invites a developer to read one connected project.
Requirements
Remote endpoint at plaro.kr over streamable HTTP with OAuth sign-in; no API key. Sign in through the browser with your own Plaro account, or with the address and 6-digit code a PM connected. Add the two project lines Plaro provides to CLAUDE.md or AGENTS.md. Use either the plugin or a hand-added server, not both.
Before you install
Some tools write to Plaro: ask_pm, report_built and mark_checks; the README says each call needs your approval and headless runs refuse them. Requirements, versions, client confirmation, amounts and dates cannot be changed from here. Tool calls, approvals, the working-folder fingerprint and sign-in records are sent to Plaro and kept for one year. A sign-in lasts 30 days.

Installation

In SourceWeft

  1. Open Plaro 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/io.github.plaro-kr%2Fplaro/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": {
    "plaro": {
      "type": "http",
      "url": "https://plaro.kr/mcp/v1"
    }
  }
}

README

Plaro for Claude Code

Your project's agreed requirements and what changed, from Plaro, inside Claude Code.

  • Tools to read — get_requirements, get_changes, get_open_questions, get_verification_gaps, search_requirements, and get_notices (the change notice).
  • Change notices — when you send a message, Claude learns what changed in the requirements since the last notice (a few lines, or nothing).
  • Commands — plan_changes (plan the work for what changed), plan_project (plan the whole current version), check_acceptance (compare acceptance criteria with the code before the acceptance check).
  • What Claude may leave in Plaro — you approve each call — ask_pm (a question the requirements do not answer), report_built (which requirements were built, with the commit), and on your own Plaro account mark_checks (acceptance checks you confirmed as passing). Claude Code asks you every time, in every permission mode, with no "don't ask again"; a run that cannot ask (claude -p) refuses them. Nothing else can be changed from here: requirements, versions, the client's confirmation, amounts and dates stay in Plaro.

Install and sign in

In Claude Code:

/plugin marketplace add plaro-kr/plaro-ai/plugin install plaro@plaro-ai

Then open /mcp, pick plaro and sign in. The browser opens Plaro's sign-in page:

  • Your own Plaro account (you build the project yourself, or you are on the team): if the browser is signed in to Plaro, press Allow. That is all — one sign-in reads every project your account can see.
  • Invited by a PM (no Plaro account): enter the address your PM connected and the 6-digit code mailed to it, and pick the project.

There is no key to copy: Claude Code keeps the sign-in in your computer's secure storage and renews it by itself. A sign-in lasts 30 days; then the browser asks again.

Until you sign in, Claude Code marks the server as needing authentication, and the message hook reports an error on each message — sign in from /mcp. On a computer without a browser, copy the address Claude Code shows; if the redirect fails, paste the full address from the browser's bar into Claude Code.

Use the plugin or a server added by hand (claude mcp add … plaro https://plaro.kr/mcp/v1), not both. With both, Claude Code keeps the one added by hand and hides the plugin's server, so the plugin's message hook reports an error on each message. If you added it by hand before, remove it first:

claude mcp remove plaro -s user

Which project

Add the two lines Plaro gives you (project → Export → Developer AI connection) to the repository's instruction file (CLAUDE.md, or AGENTS.md) so every session checks Plaro before building. On your own account the first line carries the project's code (plaro:7f3c9a12): Claude names the project with it, and after that Plaro knows the folder you work in. Another repository of another project gets that project's two lines — no new sign-in. Without the lines, Claude asks you which project once.

An invited developer's sign-in reads the one project the PM connected; to switch, use Clear authentication on plaro in /mcp and sign in again.

What is sent

  • To https://plaro.kr/mcp/v1: the tool calls Claude makes, with the token from your sign-in, and what you approved Claude to leave.
  • On every message, the hook calls get_notices through that same signed-in connection, with the folder Claude Code works in (Plaro keeps only a keyed fingerprint of it, to know its project). What you type is never sent. The hook waits five seconds at most and never blocks your work.
  • Plaro sends back only what the PM put into a requirements version or processed. No meeting or chat text, no amounts, no client names or contacts.

Plaro keeps a record of each sign-in step and call (which connection or account, which tool, the outcome, how long, from which address) for one year — never the content.

Remove

/plugin uninstall plaro@plaro-ai

Your own account's tools are listed in Plaro under account settings → Connections, where you can disconnect each. The PM can revoke an invited developer's connection at any time; one nobody uses for 90 days stops by itself.

License and trademarks

The files in this repository are released under the MIT License (LICENSE). It covers these files only: using Plaro is governed by its Terms of Service, and the Plaro name and logo are not licensed.

Claude Code is a product of Anthropic. This plugin is made by Plaro and is not affiliated with, endorsed by or sponsored by Anthropic.

Codex and ChatGPT

openai/plaro is the same Plaro MCP server packaged for OpenAI's plugin directory, which ChatGPT and Codex share. It has no message hook (the directory does not take hooks), so in ChatGPT and Codex the change notice comes when the AI calls get_notices or get_changes — the two lines in AGENTS.md (see Which project) ask it to before building. In Codex:

codex plugin marketplace add plaro-kr/plaro-aicodex plugin add plaro@plaro-aicodex mcp login plaro

The sign-in is the same as above: your Plaro account, or the address your PM connected. To have Codex ask before each call that leaves something in Plaro, add this to ~/.codex/config.toml:

[plugins."plaro@plaro-ai".mcp_servers.plaro]default_tools_approval_mode = "writes"

Layout

  • .claude-plugin/marketplace.json — this repository as a plugin marketplace (plaro-ai).
  • plugins/plaro/.claude-plugin/plugin.json — the plugin.
  • plugins/plaro/.mcp.json — the MCP server (OAuth sign-in, no key).
  • plugins/plaro/hooks/hooks.json — the message hook (type: "mcp_tool", calling get_notices).
  • openai/plaro/plugin.json · openai/plaro/mcp.json · openai/plaro/assets/ — the package for OpenAI's plugin directory (ChatGPT and Codex): listing, review cases and the remote MCP server, no hooks.
  • .agents/plugins/marketplace.json — this repository as a Codex plugin marketplace.
  • LICENSE — MIT.

This folder is kept in Plaro's main repository (integrations/claude-plugin) and copied to the public repository when it changes.

Source: README.md at commit c0fe92d

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.2.1LatestOct 29, 2026

Score

85% 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
  • License10 pts