Connect Claude Code
Add Gorila to Claude Code with one command and sign in with your Gorila account.
Gorila's MCP prompts show up as slash commands in Claude Code: /mcp__gorila__gorila-setup runs onboarding, /mcp__gorila__gorila-plan-my-day orders your day, /mcp__gorila__gorila-delegate hands work to a teammate, /mcp__gorila__gorila-bring-my-tasks brings your own open tasks from your other tools and /mcp__gorila__gorila-shift runs your work shift.
Hooks (optional)
Gorila does not need a plugin. If you want Claude Code to see your open tasks and the right company rules before you even ask, you can wire two hooks to Gorila's context API with a personal token (Settings → Tokens): SessionStart calls GET /api/hooks/session-start and UserPromptSubmit posts the prompt to POST /api/hooks/context. Both return plain text ready to print, take no LLM time, and must fail silently so they never slow you down. A packaged plugin is planned.
Steps
-
Add Gorila as a remote MCP server:
claude mcp add --transport http --scope user gorila https://app.gorila.la/api/mcp -
Run /mcp inside Claude Code, pick gorila and sign in. If the browser shows a redirect error, add --callback-port 8976 to the command above and try again.
-
Paste this block into your CLAUDE.md (~/.claude/CLAUDE.md for every project, or the repo's CLAUDE.md).
Block to paste (CLAUDE.md):
## Gorila 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. -
Gorila's prompts are slash commands: /mcp__gorila__gorila-setup runs onboarding, /mcp__gorila__gorila-plan-my-day orders your day, /mcp__gorila__gorila-delegate hands work to a teammate, /mcp__gorila__gorila-bring-my-tasks brings your own open tasks from your other tools, /mcp__gorila__gorila-shift runs your work shift.
-
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 Code and it follows the steps for you. Run /mcp, pick gorila and sign in with your Gorila account.
Set up Gorila for me:
1. Run: claude mcp add --transport http --scope user gorila https://app.gorila.la/api/mcp
2. Add the section below to ~/.claude/CLAUDE.md (create the file if it doesn't exist; if it already has a "## Gorila" section, replace it instead of adding a second one).
3. Tell me to run /mcp, pick gorila and sign in.
## Gorila
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.