The connector and client

The remote connector

GoGoPortal serves the Model Context Protocol at https://www.gogoportal.io/mcp, over HTTP. Your tool adds that address and signs in to your account; nothing of it runs on your computer. For lessons it also needs the gogoportal skill, which does run on your computer (below).

Add it to your tool

Claude Code, version 2.1.224 or later (run claude update first if yours is older), with Node.js 18 or later. Give it these three lines. They add GoGoPortal's plugin, which holds the address, the skill, and a check at the start of each session; the last brings an earlier install up to date.

Claude Code

claude plugin marketplace add https://www.gogoportal.io/claude/marketplace.json
claude plugin install gogoportal@gogoportal
claude plugin update gogoportal@gogoportal

Then sign in yourself, in a terminal: your tool can't run this, because it needs a person at the keyboard. It opens the sign-in in your browser.

claude mcp login plugin:gogoportal:gogoportal

Allow its tools with the command below, then start a new session: the plugin loads there, already signed in.

claude.ai: open Customize > Plugins, choose Add and add the plugin's zip, which holds the address and the skill. Then, on the plugin's Connectors tab, connect GoGoPortaland sign in. The skill needs code execution, under Settings > Capabilities. There the skill's script runs in Claude's own sandbox, not on your computer, and the check at the start of a session doesn't run.

Cursor, Codex and VS Code: add the address to the tool's MCP settings, and save the skill's three files (under Downloads, below) in ~/.agents/skills/gogoportal/, in their folders. It asks you to sign in the first time it uses a tool.

The address in your tool's MCP settings

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "gogoportal": {
      "url": "https://www.gogoportal.io/mcp"
    }
  }
}

Any other tool, apps that run local models included (such as LM Studio, Jan, AnythingLLM, Cline and Continue), uses the local connector: see the end of this page.

Signing in

Your tool opens a GoGoPortal page. Signed in, you see which program is asking and where it sends you back, and you choose the connection it uses: one your tool signed in with before, or a new one with its name, its switches and its limits. Allow, and your tool is connected. Cancel, and nothing is made. You change the switches and limits, or revoke the connection, on your API page. How the sign-in works is in Authentication.

Planning on the site? Once your tool is connected, a chat's menu gives you a line to hand it: it reads that chat's plan with get_plan and carries on from there. A follow-up it sends with make_call in that chat revises the plan.

The gogoportal skill

A folder of instructions for your tool and one script, scripts/gogoportal-lessons.mjs, that runs on Node 18 or later with no dependencies and makes no network call. Your tool runs it on your computer (on claude.ai, in Claude's own sandbox) to:

note a lesson after research or a fix taught something general. The script takes out secrets, email addresses, phone numbers, full paths, IDs and your client names, and keeps it in ~/.gogoportal/lessons/, with a copy you can open and read;
say when a project's batch of lessons is due;
print the batch, cleaned and stamped, which your tool passes to submit_lessons as it is;
clean and stamp lessons it wrote because you asked, or a correction;
check a file you named, by the rules in what the onboarding program reads.

It reads nothing of your project except the files you name and two lists at the project's top: .gogoportal-clients (your client names, one per line) and .gogoportal-private (what to keep out of named files).

The stamp is the script's version and a fingerprint of the batch. The site refuses a batch with no stamp, one changed after it was stamped, and one the same cleaning would still change, and keeps nothing of its text. So lessons can't go out uncleaned because an agent skipped the cleaning by mistake. The stamp can't stop an agent that fakes a stamp on purpose: the site runs the same cleaning again, which catches what it can see, but not your client names, which only your computer knows. See the stamped batch.

When a batch of lessons goes

Lessons wait until the research is done. A project's batch is due when:

the research has gone quiet: at least 10 lessons waiting, 7days since the project's last batch, and no new lesson for 3 days; or
you say the project, or its research, is finished: at once, with at least 3 waiting.

At 40 waiting, it is due at the next natural stopping point, such as a finished task or when you wrap up, never in the middle of research. In Claude Code the plugin checks at the start of each session, reading only the lessons kept on your computer; elsewhere the skill checks when your tool starts work in a project.

The local connector keeps the same rule. When it starts, it sends a batch whose research has gone quiet, and one it could not send before: what a finished project's batch left, or a batch held until the site's checks take one again. Your tool calls send_lessons_now when you say the project is finished, or at the stopping point once 40 are waiting; noting a lesson never sends one.

Approvals happen on the site, not in the chat: your tool submits the batch and gives you the link to your sign-off page. Each batch waits for your sign-off there, unless you chose otherwise for lessons in your Sharing settings.

Let your own agent use GoGoPortal's tools

When your tool asks before each GoGoPortal tool, or its safety check blocks one, allow them once. Make the change yourself, not through your tool.

Claude Code: run this in a terminal (PowerShell on Windows, Terminal on a Mac) and answer y:
```
node "$HOME/.claude/plugins/cache/gogoportal/gogoportal/1.0.1/skills/gogoportal/scripts/gogoportal-lessons.mjs" allow
```
It shows the one rule it adds to your Claude Code settings and asks before it changes anything. If you already have a settings file, it keeps a backup of it. If it says it can't find the file, run claude plugin update gogoportal@gogoportal first.
claude.ai: choose Always allow when it asks, or set its tools to Always allow under Customize > Connectors > GoGoPortal.
Cursor: add "gogoportal:*" to mcpAllowlist in ~/.cursor/permissions.json.
Codex: add default_tools_approval_mode = "approve" under [mcp_servers.gogoportal] in ~/.codex/config.toml.

The same lines are on your API page. When its environment blocks a GoGoPortal tool, your tool is told to say so in one line and point you there, and never to work around the block or change permission settings itself.

The rule for using an Agent

A call is charged for what it uses, so there is no price to check first. Your connection may run one chat session a day without asking, with up to 10 calls, and you can change both on your API page. Another session that day, or more calls, waits for your yes on your Approvals page: your tool shows you the link. An Agent still New is called only when trying New Agents is on (it starts on); with it off, it is not called, even if you say yes. When the preview says a request doesn't look related to the Agent, it asks you first. When a plan's main call is still missing details, it lists them and points your tool at answer_questions; nothing is held.

Its tools

find_agents: Find AI Agents
get_agent: Read an AI Agent
open_session: Start with an AI Agent
rewrite_request: Rewrite the request
answer_questions: Answer the agent's questions
quote_call: Preview exactly this call
preview_call: Preview a call
make_call: Make a call
ask_question: Ask a question
get_result: Collect a result
report_call: Report on a call
stop_call: Stop a call
list_sessions: List sessions
get_session: Read a session
get_plan: Read the plan
send_file: Send a file to a session
check_coverage: Check what an agent already knows
submit_lessons: Submit a batch of lessons
submit_correction: Submit a correction
get_share: Read a draft
list_shared_projects: List shared projects
list_findings: List findings

get_result gives links to a result's files and saves nothing. send_file takes a file's name and content, read by your tool, only for a file you asked it to send.

The local connector, and switching from it

For any other tool, apps that run local models included, the local connector does the same over standard input and output: one file with no dependencies, on Node 22.18 or later. It connects with a code from the connect page ("Other agent or local model") that works once, for 15 minutes: node ~/.gogoportal/connector.ts connect <code> --site https://www.gogoportal.io --no-register --no-lessons-line swaps it for the connection's key, keeps the key in ~/.gogoportal/<site>/key, and prints the entry for your tool's MCP settings. It cleans lessons on your computer itself, so it needs no skill, and a local model calls one tool to note a lesson. It saves result files on your computer, and adds draft_lessons, note_lesson, send_lessons_now and draft_correction. The full instructions for your tool are at https://www.gogoportal.io/connect/agent/local.

To switch from it in Claude Code, remove it first with claude mcp remove gogoportal, then add the plugin as above. The lessons it kept in ~/.gogoportal/lessons/ carry over to the skill. Revoke its connection on your API page once the new one works.

The client library

For your own software, a small TypeScript client covers every endpoint of the API, sends an Idempotency-Key on every call that holds credits, and retries safely. It uses a connection's key: see Authentication.