Plainsight MCP

pro.plainsightPublished by plainsight.proOfficial publisherv0.2.1Updated Oct 24, 2026

Search the Plainsight playbook and review code against proven best practices.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Lets an assistant search the Plainsight playbook and review code against proven best practices.

What you can do
This remote MCP server exposes the Plainsight playbook to an assistant. According to the registry description, it lets the assistant search that playbook and review code against proven best practices. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Worth adding when you want an assistant to check code against a curated set of best practices or to look up guidance from the Plainsight playbook during development. It is less useful if you only need general coding help without that specific reference material.
Requirements
A remote streamable HTTP endpoint at A bearer token is required and must be sent in the Authorization header; the token is obtained from the provider's authorize page. No local runtime, package, or environment variables are declared.
Before you install
The server requires a bearer token supplied in the Authorization header; treat that token as a secret and avoid exposing it in logs or shared configurations. The description indicates code is submitted for review, so code content may be sent to the remote service. No payment, write, or delete behavior is described.

Installation

In SourceWeft

  1. Open Plainsight MCP in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/pro.plainsight%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.

{
  "mcpServers": {
    "plainsight": {
      "type": "http",
      "url": "https://playbook-mcp.plainsight.pro/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.2.1LatestSep 16, 2026

Score

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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

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

  • License10 pts

    Declare a license in the repository or the registry entry.