- Home
- Skills
- DevOps & Cloud
- Recall MCP
Recall MCP
Helps you deploy, configure, and connect your own instance of Recall, a personal MCP memory server hosted on Google Cloud.
Free
Works with the AI Agents you already use
About this skill
Helps you deploy, configure, and connect your own instance of Recall, a personal MCP memory server hosted on Google Cloud. The agent checks the target, helps configure Firestore, Secret Manager and embedding access, guides the GitHub-to-Cloud Run deployment, and connects your current MCP-capable agent.
The workflow preserves Recall's buildpack-based Cloud Build pipeline and its test-before-deployment gate. It supports resuming interrupted setup, checks existing resources before changing them, and verifies real memory saves and semantic retrieval using temporary records that are cleaned up afterward.
The user completes account sign-in, billing setup and GitHub app/repository consent. For substantive Google Cloud CLI operations, the agent validates command syntax and uses supported previews; where no preview is supported, it explains the proposed changes before authorized execution.
The skill is free. You provision and manage the infrastructure and pay Google Cloud charges. Agensi does not host or run Recall. There is no bundled managed endpoint, cloud credit, or hosting subscription. This is an installation companion for Recall's personal, single-user design.
Validation
On 2026-10-31, a disposable Singapore deployment passed a final Cloud Build with overall SUCCESS and requested VERIFIED provenance. All 14 seeded MCP checks passed on an earlier revision of the same configured source commit, including memory operations, namespace isolation and fixture cleanup. The final revision separately passed health, unauthenticated 401 and authenticated tool discovery.
Testing used a temporary protocol client; persistent client configuration and reconnect behavior were not tested. Test application resources, the private repository and temporary credentials were removed; the project and billing link were retained. This is a summary of recorded validation, not a conversation transcript.
- Recall is personal and single-user; appId namespaces are not customer authentication.
- The user pays Google Cloud costs; the free skill does not include hosting or cloud credits.
- Sign-in, billing setup, GitHub consent and missing access require user involvement.
- Clients must support remote Streamable HTTP MCP with bearer authentication; compatibility is checked during setup.
- Uses the existing Java buildpack pipeline; no Dockerfile or manual deployment alternative is supplied.
- No local Docker deployment, managed hosting, custom-domain setup, ongoing upgrades or service-level agreement is included.
- Persistent client configuration/reconnect and native Windows/Linux/WSL execution were not live-tested; Agensi delivery/review remains untested.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 17 days ago
- Free with an Agensi account
Requires
Permissions
Allowed Hosts
Limit file reads and writes to the selected Recall checkout, relevant client configuration/backups, and restricted temporary files created for this setup. Limit cloud and repository changes to the approved project, locations, named resources/IAM bindings and selected fork/branch. Use only the selected local Recall credential or explicitly required setup variables; do not enumerate or read unrelated environment data. Transfer credentials only to the selected Secret Manager secret and approved client-supported credential/reference mechanism; never print credentials. Send authenticated MCP calls only to the verified endpoint and create/delete only tracked, owned test records. Infrastructure teardown requires separate explicit approval; ordinary deployments remain running. Network access is used for official documentation, the selected GitHub fork, Google Cloud APIs and the user's verified Cloud Run MCP endpoint. File-scope fields stay blank because actual paths are selected during setup.