Skip to Content
Gorila docs

Connect Cursor

Add Gorila to Cursor's mcp.json and a rules file.

Steps

  1. Add Gorila to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):

    {
      "mcpServers": {
        "gorila": {
          "url": "https://app.gorila.la/api/mcp"
        }
      }
    }
    
  2. Open Cursor Settings → MCP, find gorila and click Connect to sign in.

  3. Save this block as .cursor/rules/gorila.mdc in your project.

    Block to paste (.cursor/rules/gorila.mdc):

    ---
    description: Gorila, your organization's shared tasks and company knowledge
    alwaysApply: true
    ---
    
    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.
    
  4. 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. At cursor.com/automations, add an automation with a daily schedule, the prompt your AI gives you when you ask it to "let my AI work for me" and Gorila's MCP connection, with no repository attached.

Let your AI do it

Paste this into Cursor's agent and it follows the steps for you. Open Cursor Settings → MCP and click Connect on gorila.

Set up Gorila for me:
1. Add a "gorila" server with url "https://app.gorila.la/api/mcp" to ~/.cursor/mcp.json, keeping the servers already there.
2. Save the text below as .cursor/rules/gorila.mdc in this project.
3. Tell me to open Cursor Settings → MCP and click Connect on gorila.

---
description: Gorila, your organization's shared tasks and company knowledge
alwaysApply: true
---

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.