Picaos

com.picaosPublished by picaos.comv2.0.3Updated Oct 24, 2026

A Model Context Protocol Server for Pica

VerifiedSTDIODesktop onlyProductivity & Workflow

Overview

AI-generated overview

A local MCP server for Pica that connects an AI assistant to the Pica platform using a PICA_SECRET API key.

What you can do
This server runs locally over stdio and exposes Pica to an MCP-capable assistant. The registry description only states that it is a Model Context Protocol server for Pica; no tools are listed in the manifest, so the specific actions it offers are not documented here. It authenticates with a single API key supplied as the PICA_SECRET environment variable.
When to use it
Consider it when you already use Pica and want an assistant to work with it from a local MCP client. Because the available tools are not described, confirm what it can actually do before relying on it.
Requirements
Runs as a local process on the user's machine via the npm package @picahq/mcp over stdio. Desktop only; not available as a web executable. Requires a Pica API key passed in the PICA_SECRET environment variable. Network access is implied by the remote service.
Before you install
The server requires a secret, PICA_SECRET, which is a Pica API key; store it securely and avoid exposing it in logs or shared configuration. The manifest lists no tools, so any actions it can take on your Pica account are undocumented and should be verified before use.

Installation

In SourceWeft

  1. Open Picaos in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v2.0.3LatestSep 16, 2026

Score

25% 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 days25 pts

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

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

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