Pica MCP Server

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.

Features

Tools

• list_pica_integrations - List all available platforms and your active connections
• search_pica_platform_actions - Search for available actions for a specific platform
• get_pica_action_knowledge - Get detailed documentation for a specific action including parameters and usage
• execute_pica_action - Execute API actions with full parameter support

Key Capabilities

Platform Integration

• Connect to 200+ platforms through Pica
• Manage multiple connections per platform
• Real-time connection status and discovery

Smart Intent Detection

• Execute actions directly from natural language (e.g. "read my last gmail email", "send a message to the slack channel #general")
• Generate integration code from prompts (e.g. "build a form to send emails using gmail", "create a UI for messaging")
• Automatically distinguishes between execution and code generation intent

Direct Execution

• Support for all HTTP methods (GET, POST, PUT, DELETE, etc.)
• Handle form data, URL encoding, and JSON payloads
• Path variable substitution, query parameters, and custom headers

Security

• All requests authenticated and proxied through Pica; no platform API keys to manage
• Secrets never exposed in responses or generated code
• Request configurations sanitized before returning to clients
• Fine-grained access control via permission levels, connection key scoping, and action allowlisting

Getting Started

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

Manual Installation

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

Optional: Identity Scoping

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.

Optional: Access Control

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

... View full README on GitHub