Connect Claude
Add Gorila as a custom connector in Claude on the web, the desktop app and Cowork.
Steps
-
Open Claude's connectors (Customize → Connectors) and click Add → Add custom connector. Open Claude's connectors
-
Fill in the two fields and click Continue:
- Name:
Gorila - MCP server URL:
https://app.gorila.la/api/mcp
- Name:
-
Click Connect and sign in with your Gorila account (the one you use here). Allow it when asked.
-
Paste this block into your profile preferences (Settings → Profile), or into the instructions of each project where you work.
Block to paste (Profile preferences or project instructions):
your organization uses Gorila (MCP server "gorila") as its shared work memory: the team's tasks and company knowledge (brand tone, copy rules, SOPs, policies, decisions). ALWAYS: - Before writing anything for your organization (emails, customer replies, copy, ads, posts, docs) or running a recurring process, call get_relevant_knowledge with a short description of the situation, and follow what it returns. - Facts about your organization itself (product, pricing, customers, policies) are in Gorila: call get_relevant_knowledge before searching the web or leaving a placeholder. - When I correct your tone, a process or a fact that could apply again, call propose_knowledge_change. Nothing is published until a person approves it. - When I mention work for someone else ("tell Ana to…", "this is for Esteban"), offer to create_task with full context (background, goal, done criteria, links) so their AI can do it. - When I start working or ask what's next, call list_my_tasks. - When you start working on a Gorila task, set it to doing with update_task; when it's finished (for code: its pull request merged), set it to done with a comment of what you did. Don't wait for me to ask. - Put a Gorila task's id in the title or branch of its pull requests and comment_task the link; comment again when it's merged or closed. - Store distilled, reusable text in Gorila, never raw documents, full emails or chat logs. - If a person or a task is ambiguous, ask me. Never guess. - When a task's end comes after this session (a reply, a merge, an approval), set what it's waiting for and when to look again (waiting_on, recheck_at), not only a comment. -
Let your AI work between sessions: a nightly run turns what you committed to into tasks, prepares the most urgent ones and checks the rest, and never sends anything. Ask it: "let my AI work for me". It creates the run itself.
Let your AI do it
Paste this into Claude in Chrome or Cowork and it follows the steps for you. Sign in to Gorila when the connector asks you to.
Set up Gorila in my Claude account, in my browser:
1. Open https://claude.ai/customize/connectors → Add → Add custom connector. Name it Gorila, use this MCP server URL and continue: https://app.gorila.la/api/mcp
2. Click Connect on Gorila. When it asks me to sign in to Gorila, stop and let me do it.
3. Open Settings → Profile and add the text below to my personal preferences, keeping what's already there. Save.
your organization uses Gorila (MCP server "gorila") as its shared work memory: the team's tasks and company knowledge (brand tone, copy rules, SOPs, policies, decisions).
ALWAYS:
- Before writing anything for your organization (emails, customer replies, copy, ads, posts, docs) or running a recurring process, call get_relevant_knowledge with a short description of the situation, and follow what it returns.
- Facts about your organization itself (product, pricing, customers, policies) are in Gorila: call get_relevant_knowledge before searching the web or leaving a placeholder.
- When I correct your tone, a process or a fact that could apply again, call propose_knowledge_change. Nothing is published until a person approves it.
- When I mention work for someone else ("tell Ana to…", "this is for Esteban"), offer to create_task with full context (background, goal, done criteria, links) so their AI can do it.
- When I start working or ask what's next, call list_my_tasks.
- When you start working on a Gorila task, set it to doing with update_task; when it's finished (for code: its pull request merged), set it to done with a comment of what you did. Don't wait for me to ask.
- Put a Gorila task's id in the title or branch of its pull requests and comment_task the link; comment again when it's merged or closed.
- Store distilled, reusable text in Gorila, never raw documents, full emails or chat logs.
- If a person or a task is ambiguous, ask me. Never guess.
- When a task's end comes after this session (a reply, a merge, an approval), set what it's waiting for and when to look again (waiting_on, recheck_at), not only a comment.