Pleasanter MCP

io.github.ImplemPublished by GitHub account Implemv1.0.6Updated Oct 24, 2026

Pleasanter MCP - You can perform data operations on Pleasanter directly from VSCode

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Lets an assistant perform data operations on Pleasanter directly from VSCode through a remote MCP endpoint.

What you can do
This server connects an assistant to Pleasanter so it can carry out data operations on that platform directly from VSCode. It is offered as a remote streamable HTTP endpoint rather than a locally installed package. The manifest does not list individual tools, so the exact operations available are not specified in the supplied material.
When to use it
Use it when you work with Pleasanter data and want an assistant to act on it from inside VSCode instead of switching to the Pleasanter interface. It suits teams already running a Pleasanter instance who can provide an API key.
Requirements
A remote streamable HTTP endpoint at and a Pleasanter API key sent in the X-API-Key header. No local package or runtime is declared. Network access to the Pleasanter host is required.
Before you install
The connection requires a Pleasanter API key supplied in the X-API-Key header; treat it as a secret and avoid exposing it in shared configuration or logs. Because the server performs data operations on Pleasanter, an assistant may read, create, update, or delete records in that system, so review what it is allowed to change before use.

Installation

In SourceWeft

  1. Open Pleasanter MCP in the dashboard and add it to a workspace.
  2. Connect X-API-Key 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.

Other MCP clients

Follow the launch instructions in the repository.

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. v1.0.6LatestSep 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.