{
"mcpServers": {
"com-picaos-mcp": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A Model Context Protocol Server for Pica
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 33 days ago. 12 stars.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Dynamic problem-solving through sequential thought chains
A Model Context Protocol server for searching and analyzing arXiv papers
An open-source AI agent that brings the power of Gemini directly into your terminal.
The official Python SDK for Model Context Protocol servers and clients
MCP Security Weekly
Get CVE alerts and security updates for com.picaos/mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) server that integrates with Pica, enabling seamless interaction with various third-party services through a standardized interface. This server provides direct access to platform integrations, actions, execution capabilities, and robust code generation capabilities.
The fastest way to get up and running is with the Pica CLI. It handles API key configuration and MCP installation for your agent or editor of choice.
npm install -g @picahq/cli
pica init
pica init will prompt you for your API key (get one from the Pica dashboard) and walk you through configuring the MCP server for your environment (Claude Desktop, Cursor, Claude Code, etc.).
If you prefer to configure the server manually, install the package directly:
npm install @picahq/mcp
Then set the required environment variable:
PICA_SECRET=your-pica-secret-key
You can scope connections to a specific identity (e.g., a user, team, or organization) by setting these optional environment variables:
PICA_IDENTITY=user_123
PICA_IDENTITY_TYPE=user
| Variable | Description | Values |
|----------|-------------|--------|
| PICA_IDENTITY | The identifier for the entity (e.g., user ID, team ID) | Any string |
| PICA_IDENTITY_TYPE | The type of identity | user, team, organization, project |
When set, the MCP server will only return connections associated with the specified identity. This is useful for multi-tenant applications where you want to scope integrations to specific users or entities.
Fine-tune what the MCP server can see and do by setting these optional environment variables:
PICA_PERMISSIONS=read
PICA_CONNECTION_KEYS=conn_key_1,conn_key_2
PICA_ACTION_IDS=action_id_1,action_id_2
PICA_KNOWLEDGE_AGENT=true
| Variable | Type | Default | Description |
|---|---|---|---|
| PICA_PERMISSIONS | read | write | admin | admin | Filter actions by HTTP method. read = GET only, write = GET/POST/PUT/PATCH, admin = all methods |
| PICA_CONNECTION_KEYS | * or comma-separated