Claude Code

Install the GoBanana plugin for the 9 skills, sign in with /mcp, or add the server alone. Plus --plugin-dir for local development.

Claude Code gets the most out of GoBanana: the plugin’s skills run the whole flow, and Claude Code can write the hand-off files straight into your repo.

Option A: the plugin (recommended)

The plugin bundles the server connection and the 9 skills (gobanana-explore, gobanana-frankenstein, gobanana-handoff and the rest). See Skills.

Install the plugin. On Claude Code 2.1.275 or later, one command adds the GoBanana marketplace and installs:
```
/plugin install gobanana --marketplace MaherFayad/gobanana-plugin
```
Claude Code shows the marketplace it resolved and asks you to confirm. On older versions, add the marketplace first, then install:
```
/plugin marketplace add MaherFayad/gobanana-plugin
/plugin install gobanana@gobanana
```
From your shell, without a session: claude plugin install gobanana --marketplace MaherFayad/gobanana-plugin (2.1.292 or later), or claude plugin marketplace add MaherFayad/gobanana-plugin then claude plugin install gobanana@gobanana.
Pick a scope. The install opens the plugin’s details. Review what it adds (9 skills and the gobanana MCP server), then choose Install for you (every project), Install for all collaborators on this repository (project), or Install for you, in this repo only (local). If the summary ends with Run /reload-plugins to apply., run /reload-plugins.
Sign in. Run:
```
/mcp
```
Pick plugin:gobanana:gobanana and choose to authenticate. Your browser opens the GoBanana sign in page (WorkOS AuthKit). Sign in; when the browser says you can close it, go back to Claude Code. If the browser does not open, copy the URL Claude Code prints. From the shell, claude mcp login does the same.
Check it. Type / and look for the gobanana-* skills, then ask:
```
Check my GoBanana connection.
```
Claude calls ping and answers “Connected to GoBanana as you@example.com.”

Option B: the server only

No skills, just the tools. Useful in a repo where you only want to export, or when GitHub is not reachable.

Scopes: local (the default: you, this project), project (a .mcp.json you commit) or user (you, every project).

For you (all projects)
For this project

claude mcp add --transport http --scope user gobanana https://gobanana.fun/api/mcp

claude mcp add --transport http --scope project gobanana https://gobanana.fun/api/mcp

This writes a .mcp.json at the project root that you can commit, so your team gets the server too. Each person still signs in with their own account.

Then start Claude Code, run /mcp, pick gobanana and sign in. A project scoped server asks for approval the first time. claude mcp list shows its status.

Without the plugin, paste the one line that tells Claude to fetch the playbook, once per chat. See No plugin?.

Option C: local development with –plugin-dir

To try a local copy of the plugin (for example after editing a skill), point Claude Code at the folder:

git clone https://github.com/MaherFayad/gobanana-plugin.git
cd your-project
claude --plugin-dir /path/to/gobanana-plugin/gobanana

--plugin-dir loads the plugin for that session only. The skills are short stubs that fetch their playbook from the server with get_playbook; edit a SKILL.md description, restart Claude Code, and the change is live. The folder’s .mcp.json points at the same server:

{
  "mcpServers": {
    "gobanana": {
      "type": "http",
      "url": "https://gobanana.fun/api/mcp"
    }
  }
}

To check the plugin is valid (strict mode needs Claude Code 2.1.281 or later, which knows the directory fields in plugin.json):

claude plugin validate --strict ./gobanana

Tool names in Claude Code

With the plugin, tools show up as mcp__plugin_gobanana_gobanana__<tool>, for example mcp__plugin_gobanana_gobanana__bend_brief. With Option B they are mcp__gobanana__<tool>. Use these names if you add them to permissions.allow in .claude/settings.json so Claude does not ask each time:

{
  "permissions": {
    "allow": [
      "mcp__plugin_gobanana_gobanana__ping",
      "mcp__plugin_gobanana_gobanana__bend_brief",
      "mcp__plugin_gobanana_gobanana__get_canvas",
      "mcp__plugin_gobanana_gobanana__rate_references",
      "mcp__plugin_gobanana_gobanana__rate_directions"
    ]
  }
}

Leave delete_canvas out of the allow list, so Claude always asks before deleting.

The canvas in Claude Code

Claude Code runs in a terminal, so it cannot show the board inline. Every skill reply ends with the web link: “Open the board here: https://gobanana.fun/c/…”. Open it in a browser signed in with the same account.

What was verified

Checked on 2026-10-12 against the Claude Code docs (MCP and plugin pages). With Claude Code 2.1.226 on Windows, claude mcp add --transport http --scope project gobanana <url> wrote the .mcp.json shown above and claude mcp get gobanana listed it as an HTTP server pending approval. The live endpoint answers an unsigned request with 401 and a WWW-Authenticate header that points to its OAuth metadata, which is what /mcp sign in uses. The marketplace (.claude-plugin/marketplace.json at the repo root, marketplace name gobanana) was checked by a local add and install in a temporary config, and claude plugin validate passes. The public MaherFayad/gobanana-plugin repo holds only the plugin and its marketplace file; it is synced from the private source repo on each plugin release. The browser sign in itself was not run for these docs.

Upgrading from an older install

The plugin’s server key was renamed from banana to gobanana, and the skills from banana-* to gobanana-*. If you see an old banana server in /mcp, uninstall the old plugin, install gobanana@gobanana, and sign in again.

Your first board, or Hand off to your coding agent if you already have a board.