Pica Settings

io.github.withpicaPublished by GitHub account withpicav1.1.0Updated Oct 24, 2026

account, team, and api key management for withPICA

VerifiedSTDIODesktop onlyProductivity & Workflow Security & Monitoring

Server details

Identifier: io.github.withpica/pica-settings
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account withpica for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.withpica%2Fpica-settings.svg)](https://sourceweft.com/mcp/io.github.withpica%2Fpica-settings?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server that gives an assistant account, team, and API key management for withPICA.

What you can do: Manage withPICA accounts through the assistant, including account-level settings and operations. Handle team management, such as team membership and team-level configuration. Manage API keys for withPICA. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it: Useful when you work with withPICA and want an assistant to handle account, team, or API key administration without switching to the web interface.
Requirements: Runs as a local process on the user's machine via the npm package @withpica/mcp-server-settings over stdio. Desktop only; no web execution. No authentication, environment variables, or headers are declared.

Before you install

It manages API keys and team settings, so it can likely create, change, or revoke credentials and team access; review actions before confirming. No credentials or secrets are declared in the manifest, but the server may still require a withPICA login at runtime.

Installation

In SourceWeft

Open Pica Settings in the dashboard and add it to a workspace.
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

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

Version history

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