Pica MCP Server
Allows sending and reading emails, and retrieving recent messages via Gmail.
Allows managing Linear users, projects, and issues.
Allows fetching and displaying QuickBooks invoices and financial data.
Allows retrieving products and managing Shopify store data.
Allows sending messages to Slack channels and integrating with Slack workspaces.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Pica MCP Server get my last 5 emails from Gmail"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
get_pica_platform_actions - Get 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
Related MCP server: anyapi-mcp-server
Key Capabilities
🔌 Platform Integration
Connect to 100+ platforms through Pica
Manage multiple connections per platform
Access real-time connection status
🎯 Smart Intent Detection
Execute actions immediately (e.g. "read my last gmail email", "send a message to the slack channel #general")
Generate integration code (e.g. "build a form to send emails using gmail", "create a UI for messaging")
Intelligent context handling
🔒 Enhanced Security
Never exposes secrets in generated code
Uses environment variables:
PICA_SECRET,PICA_[PLATFORM]_CONNECTION_KEYSanitized request configurations for production use
⚡ Direct Execution
Execute actions directly through the MCP interface
Support for all HTTP methods (GET, POST, PUT, DELETE, etc.)
Handle form data, URL encoding, and JSON payloads
Pass path variables, query parameters, and custom headers
🔒 Secure Authentication
All requests authenticated through Pica's secure proxy
No need to manage individual platform API keys
Environment variable configuration for security
Installation
npm install @picahq/mcpSetup
PICA_SECRET=your-pica-secret-keyGet your Pica secret key from the Pica dashboard.
Usage
As a Standalone Server
npx @picahq/mcpIn Claude Desktop
To use with Claude Desktop, add the server config:
On MacOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"pica": {
"command": "npx",
"args": ["@picahq/mcp"],
"env": {
"PICA_SECRET": "your-pica-secret-key"
}
}
}
}In Cursor
In the Cursor menu, select "MCP Settings" and update the MCP JSON file to include the following:
{
"mcpServers": {
"pica": {
"command": "npx",
"args": ["@picahq/mcp"],
"env": {
"PICA_SECRET": "your-pica-secret-key"
}
}
}
}Using Docker
Build the Docker Image:
docker build -t pica-mcp-server .Run the Docker Container:
docker run -e PICA_SECRET=your_pica_secret_key pica-mcp-serverInstalling via Smithery
To install pica for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @picahq/mcp --client claudeDeploy to Vercel
You can deploy this MCP server to Vercel for remote access:
Install dependencies including Vercel adapter:
npm install @vercel/mcp-adapter zodDeploy to Vercel:
vercelConfigure your MCP client to use the remote server:
For Cursor:
https://your-project.vercel.app/api/mcpFor Claude/Cline: Use
npx mcp-remote https://your-project.vercel.app/api/mcp
See DEPLOYMENT.md for detailed Vercel deployment instructions.
Examples for Inspiration
📋 Integration Code Generation
Build Email Form:
"Create me a React form component that can send emails using Gmail using Pica"
Linear Dashboard:
"Create a dashboard that displays Linear users and their assigned projects with filtering options using Pica"
QuickBooks Table:
"Build a paginatable table component that fetches and displays QuickBooks invoices with search and sort using Pica"
Slack Integration:
"Create a page with a form that can post messages to multiple Slack channels with message scheduling using Pica"
🚀 Direct Action Execution
Gmail Example:
"Get my last 5 emails from Gmail using Pica"
Slack Example:
"Send a slack message to #general channel: 'Meeting in 10 minutes' using Pica"
Shopify Example:
"Get all products from my Shopify store using Pica"
API Reference
Tools
list_pica_integrations
List all available Pica integrations and platforms. Always call this tool first to discover available platforms and connections.
Parameters: None
Returns:
Connected integrations grouped by platform
Available platforms with descriptions
Summary statistics
Management links
get_pica_platform_actions
Get all available actions for a specific platform.
Parameters:
platform(string, required): Platform name in kebab-case format (e.g., 'ship-station', 'shopify')
Returns:
List of available actions with IDs and titles
Platform-specific action count
Next steps guidance
get_pica_action_knowledge
Get comprehensive documentation for a specific action. Must be called before execute_pica_action to understand requirements.
Parameters:
action_id(string, required): Action ID from get_pica_platform_actionsplatform(string, required): Platform name in kebab-case format
Returns:
Detailed action documentation
Parameter requirements and structure
API-specific guidance and caveats
Usage examples and implementation notes
execute_pica_action
Execute a Pica action to perform operations on third-party platforms. Critical: Only call this when the user wants to execute an action, not when building applications.
Parameters:
platform(string, required): Platform nameaction(object, required): Action object with_id,path, andmethodconnectionKey(string, required): Connection key for the platformdata(object, optional): Request body datapathVariables(object, optional): Variables to replace in the pathqueryParams(object, optional): Query parametersheaders(object, optional): Additional headersisFormData(boolean, optional): Send as multipart/form-dataisFormUrlEncoded(boolean, optional): Send as URL-encoded form data
Returns:
requestConfig: Sanitized request configurationresponseData: Actual API response from the platform
Error Handling
The server implements comprehensive error handling:
✅ Parameter validation for all tools
✅ Connection verification before execution
✅ Path variable validation and substitution
✅ Graceful handling of API failures
✅ Detailed error messages for debugging
✅ MCP-compliant error responses
Security
🔐 Single environment variable required:
PICA_SECRET🛡️ All requests authenticated through Pica's secure proxy
🔒 No direct platform API key management needed
🚫 Secrets never exposed in responses
✅ Request configurations sanitized
🔍 Sensitive data filtered from logs
🛡️ Input validation and sanitization
License
GPL-3.0
Support
For support, please contact support@picaos.com or visit https://picaos.com
Available Tools
4 toolsexecute_pica_actionExecute Pica ActionA
Execute a Pica action to perform actual operations on third-party platforms. CRITICAL: Only call this when the user's intent is to EXECUTE an action (e.g., 'read my last Gmail email', 'fetch 5 contacts from HubSpot', 'create a task in Asana'). DO NOT call this when the user wants to BUILD or CREATE code/forms/applications - in those cases, stop after get_pica_action_knowledge and provide implementation guidance instead. REQUIRED WORKFLOW: Must call get_pica_action_knowledge first. If uncertain about execution intent or parameters, ask for confirmation before proceeding.
Inputs: platform (required), action (required), connectionKey (required), data, +5 more.
get_pica_action_knowledgeGet Action KnowledgeA
Get comprehensive documentation for a specific action including parameters, requirements, and usage examples. MANDATORY: You MUST call this tool before execute_pica_action to understand the action's requirements, parameter structure, caveats, and proper usage. This loads the action documentation into context and is required for successful execution.
Inputs: action_id (required), platform (required).
get_pica_platform_actionsGet Platform ActionsA
Get all available actions for a specific platform. Call this after list_pica_integrations to discover what actions are possible on a platform. Use the exact kebab-case platform name from the integrations list. This shows you what actions are available for that platform's API.
Inputs: platform (required).
list_pica_integrationsList Pica IntegrationsA
List all available Pica integrations and platforms. ALWAYS call this tool first in any workflow to discover what platforms and connections are available. This returns the connections that the user has and all available Pica platforms in kebab-case format (e.g., 'ship-station', 'shopify') which you'll need for subsequent tool calls.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a distinct purpose in a clearly defined workflow: listing integrations, fetching platform actions, retrieving action documentation, and executing the action. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern with snake_case (list_pica_integrations, get_pica_platform_actions, get_pica_action_knowledge, execute_pica_action). The verbs are action-oriented and match the tool's function.
With 4 tools, the server is lean but covers the essential steps for discovering and executing actions on third-party platforms. Each tool earns its place; the number is appropriate for the scope.
The toolset provides a complete workflow: discover available integrations, explore platform actions, get detailed action knowledge, and execute the action. There are no obvious gaps or dead ends for the stated purpose.
Maintenance
Related MCP Connectors
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
Discover and call 10,000+ production APIs from one MCP server. Pay-per-call billing for AI agents.
Unified MCP Server is a remote MCP connector for AI agents and vertical AI products that provides access to 22,000+ authorized SaaS tools across 400+ integrations and 24 categories directly inside LLMs (Claude, GPT, Gemini, Cohere). Tools operate only on explicitly authorized customer connections, enabling agents to safely read and write against live third-party systems.
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
Related MCP Servers
- AlicenseCqualityDmaintenanceAggregates multiple third-party APIs into unified MCP tools, providing out-of-the-box access to 10 popular services including OpenWeather, Google Maps, GitHub, Notion, Spotify, and more. Enables users to interact with weather data, search places, manage repositories, create content, and access various web services through a single MCP server.34MIT
- FlicenseNot gradedqualityDmaintenanceA universal MCP server that connects any REST API to AI assistants via OpenAPI or Postman specifications. It enables dynamic tool creation with GraphQL-style field selection and automatic schema inference for efficient data retrieval.9 npm6-

Spica MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceMCP server that enables AI agents to interact with Spica servers, managing databases, serverless functions, storage, authentication, auditing, debugging, and version control.12 npmISC- AlicenseNot gradedqualityCmaintenanceMCP server that bridges AI agents with external tools, APIs, databases, and services, enabling standardized tool execution and resource access.MIT