Pica Community Edition
Connect AI agents to 200+ integrations via MCP
- Source repo
- withoneai/pica
- Stars
- ★ 1.5k
- Last updated
- 2mo ago
- License
- GPL-3.0
- Primary language
- Rust
- FA score
- 9/100 · Major gaps
At a glance
- How it runs
- Works with
- Platform-specific
- Cost
- Free tier plus a paid hosted plan
- Setup effort
- Low · running in minutes
- You'll need
- Typical use
- Developers who want to integrate their AI agent (built with any framework) with Gmail via MCP for email automation.
- Not a fit if
- Teams needing fully offline or self-hosted deployment; the platform is cloud-only
- Users who need ongoing maintenance and support; the community edition is unmaintained
- Teams unwilling to bind data and accounts to the app.picaos.com cloud
- Source review
- 9/100 · Major gaps 8 safety controls not found
What does this agent do, and when should you use it?
Pica Community Edition is an agentic tooling platform that connects AI agents to 200+ integrations. The repository is the community edition, which is no longer actively maintained and has transitioned to a private cloud platform. It provides a CLI (@picahq/cli) for initialization, a web dashboard for managing connections, and an MCP server (via the Pica skill) that enables agents to interact with connected platforms like Gmail. The platform manages authentication, verified action knowledge, and offers developer-friendly SDKs. Users must obtain an API key from the dashboard, then use the Pica CLI and install the skill to integrate with their AI agent or agent builder.
Pica Community Edition provides a CLI tool (@picahq/cli) that initializes configuration via 'pica init' using an API key from the dashboard. It allows users to add connections like Gmail through the web app. It installs the Pica skill via npx (npx skills add) that provides access to connected integrations through an MCP server. In its architecture, agents invoke MCP calls to manipulate user-connected platforms (e.g., Gmail) for actions like email management. The platform curates integration knowledge to verify available actions.
- Developers who want to integrate their AI agent (built with any framework) with Gmail via MCP for email automation.
- Agent builders who need to give their agents access to a wide range of integrations (200+ platforms) without managing OAuth manually.
- Developers who require centralized connection management and secure API key storage for multiple integrations.
- Teams that use 'npx skills add' to quickly install the Pica skill into their environment and then interact with connected services.
- Developers who need a CLI tool to initialize and configure their project for agent integration.
How do you install or deploy this agent?
Install the Pica CLI globally with npm: 'npm i -g @picahq/cli'. Then run 'pica init' and provide your API key from https://app.picaos.com/settings/api-keys.
How do you use this agent?
After installing the CLI, run 'pica init' and add a Gmail connection from the app dashboard. Then install the Pica skill with 'npx skills add https://github.com/picahq/skills --skill pica'. Finally, configure your AI agent or builder to use the MCP server, allowing it to interact with your connected integrations.
What are this agent's strengths and limitations?
- Supports over 200 integrations and 25,000+ actions, covering a broad range of platforms.
- Simplifies authentication with centralized connection management and secure storage.
- Uses the MCP protocol, a standard interface that many agent frameworks can adopt.
- Offers developer-friendly SDKs to accelerate integration.
- Community edition is no longer maintained, meaning no updates or support.
- No self-hosting option; the platform is cloud-only, creating vendor lock-in.
- Requires API key and dashboard access to app.picaos.com, increasing platform dependency.
- Core features like verified action knowledge depend on cloud services, not available offline or in private deployments.
How does this agent compare with similar options?
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| Pica Community Edition This agent | 9 · Major gaps | CLIFreemium | ★ 1.5k | 2mo ago | Rust | — |
| Unbrowse Website API Client | 56 · Major gaps | Hosted serviceFreemium | ★ 801 | 1d ago | TypeScript | ChatGPT · Codex · Claude Code |
| SkillKit — Package Manager for AI Agent Skills | 40 · Major gaps | CLIFree + model costs | ★ 1.6k | 4mo ago | TypeScript | ChatGPT · Claude Code |
| OSS Autopilot | 83 · Good | Agent plugin / skillFree | ★ 21 | 1d ago | TypeScript | Claude Code · Claude.ai |
How does FollowAgents rate this agent?
Why each dimension lost points
Evidence shows only README and LICENSE; no code or configuration to demonstrate permission management, user confirmation, data flow transparency, sensitive data handling, dependency security, external effects, rollback, or source attribution. All trust criteria lack evidence, hence 0.
README states it is the community edition and no longer actively maintained, consistent with repository description, but lacks code and tests to verify consistency. Dependency availability and failure messages have no evidence. Thus self-consistency scores 1, others 0.
README identifies target audience (AI agent developers) and use case (connecting Gmail etc.), but does not define capability boundaries, trigger precision, or environment fit. Hence audience and scenarios score 1, others 0.
README provides installation steps and links to documentation, basic information architecture. Known limitation (no longer maintained) is stated. License is GPL-3.0, but no version or changelog. Maintenance responsibility implied by deprecation notice. Thus information architecture, install notes, known limitations, and maintenance responsibility each score 1, license scores 2, others 0.
README describes product value (connect 200+ integrations), but no concrete evidence of output usability, marginal value, or cost-benefit. Hence marginal value scores 1, others 0.
All claims lack code or test support, cannot be traced or cross-verified, facts and inferences not separated. Hence all criteria score 0.
- Not found in source: least-privilege scopingGrant only what the task needs: a dedicated account or read-only token, scoped to specific directories and repos.
- Not found in source: confirmation before actingTurn on (or add) a confirmation step before it acts, and try it in a sandbox or test environment before real data.
- Not found in source: data-flow disclosureWatch which external services it contacts (proxy or firewall logs) and keep sensitive data out until you know where it goes.
- Not found in source: sensitive-data handlingUse dedicated, low-privilege, revocable API keys — never production credentials — and keep secrets out of logs.
- Not found in source: dependency securityPin versions and run a dependency audit (npm audit, pip-audit) before installing; prefer running it in a container.
- Not found in source: disclosed external effectsEstablish which external systems it writes to, sends to or changes, and verify with test accounts or repos before production.
- Not found in source: rollback or recovery pathBack up first, or work on a git branch or snapshot, so its changes can be undone.
- Not found in source: verifiable attributionInstall from the official repo or registry and check the publisher and URL to avoid look-alike packages.
- Repository contains only README and LICENSE, no code or tests, so any functional or security claims cannot be verified.
- README explicitly states it is no longer maintained; assess risk before use.
- No dependency manifest or security audit provided; dependency security unknown.
Recent releases
Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.
-
Release notes excerpt
What's Changed * feat: Puzzle.io OAuth Configuration by @siddharth-bhansali in https://github.com/picahq/pica/pull/332 Full Changelog: https://github.com/picahq/pica/compare/1.58.0...1.59.0View on GitHub ↗ -
Release notes excerpt
What's Changed * feat: Canva OAuth Configuration by @siddharth-bhansali in https://github.com/picahq/pica/pull/337 * feat: Contentstack Content Management OAuth by @siddharth-bhansali in https://github.com/picahq/pica/pull/336 Full Changelog: https://github.com/picahq/pica/compare/1.57.0...1.58.0View on GitHub ↗ -
Release notes excerpt
What's Changed * feat: ShipBob OAuth Configuration by @siddharth-bhansali in https://github.com/picahq/pica/pull/333 Full Changelog: https://github.com/picahq/pica/compare/1.56.0...1.57.0View on GitHub ↗