How do I install the Forgetful MCP Setup skill?

Run npx skillmds@latest add scottrbk/forgetful-mcp-setup in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Forgetful MCP Setup safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Forgetful MCP Setup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Forgetful MCP Setup free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Forgetful MCP Setup?

scottrbk (@scottrbk) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Forgetful MCP Setup by scottrbk — Agent Skill

Name: Forgetful MCP Setup
Author: scottrbk

Forgetful MCP Setup

Set up an MCP client for Forgetful — wire Claude Code, Cursor, Copilot, Codex, Gemini, or OpenCode to the server and verify the connection behaves. Covers stdio vs HTTP transport, auth and scopes, the three meta-tools every client sees, and delegation to subagents.

scottrbk 246b4c3 2.4 KB Updated Sep 17, 2026

File contents

Setting up an MCP client

Every MCP client sees the same three tools fronting the full registry: discover_forgetful_tools (what exists, by category), how_to_use_forgetful_tool (one tool's docs and schema), execute_forgetful_tool (invoke by name with a JSON arguments object). Roughly 500 tokens of surface, with everything else disclosed at runtime.

Pick a transport

stdio — the client spawns the server per session: command uvx forgetful-ai (equivalently forgetful serve --transport stdio). Right for a personal, local setup.
HTTP — the client connects to a running server at <server>/mcp, e.g. http://localhost:8020/mcp. Right for a shared or deployed instance.

Claude Code, as the worked example:

claude mcp add forgetful -- uvx forgetful-ai                          # stdio
claude mcp add --transport http forgetful http://localhost:8020/mcp  # HTTP

Other clients follow the same two shapes (spawn command, or HTTP endpoint) in their own config format — full per-client walkthroughs live in docs/connectivity_guide.md in the Forgetful repo.

Auth and scopes

A local server defaults to no-auth single-user mode — connect and go. Deployed servers use bearer tokens or OAuth (the server's configured provider). FORGETFUL_SCOPES on the server side sets a capability ceiling (e.g. read-only) that both MCP and CLI honour; a client that should only recall can be scoped so writes are refused.

Verify — the completion criterion

Behavioural, not configurational:

discover_forgetful_tools returns categories, and they match the server's enabled feature flags (skills/files/plans appear only when enabled).
One execute_forgetful_tool round-trip returns real data — get_current_user or list_projects both work as smoke calls.

Done when: both pass in the client that was just wired, in a fresh session.

Delegation boundary

Run Forgetful MCP calls in the main conversation — subagents do not inherit MCP tool access. When work must be delegated to a subagent, give it the CLI surface instead (Bash with the forgetful command travels into subagents; see forgetful-cli-setup).

---name: forgetful-mcp-setupdescription: Set up an MCP client for Forgetful — wire Claude Code, Cursor, Copilot, Codex, Gemini, or OpenCode to the server and verify the connection behaves. Covers stdio vs HTTP transport, auth and scopes, the three meta-tools every client sees, and delegation to subagents.license: MIT---# Setting up an MCP clientEvery MCP client sees the same three tools fronting the full registry:`discover_forgetful_tools` (what exists, by category), `how_to_use_forgetful_tool` (onetool's docs and schema), `execute_forgetful_tool` (invoke by name with a JSON argumentsobject). Roughly 500 tokens of surface, with everything else disclosed at runtime.## Pick a transport- **stdio** — the client spawns the server per session: command `uvx forgetful-ai` (equivalently `forgetful serve --transport stdio`). Right for a personal, local setup.- **HTTP** — the client connects to a running server at `<server>/mcp`, e.g. `http://localhost:8020/mcp`. Right for a shared or deployed instance.Claude Code, as the worked example:```bashclaude mcp add forgetful -- uvx forgetful-ai # stdioclaude mcp add --transport http forgetful http://localhost:8020/mcp # HTTP```Other clients follow the same two shapes (spawn command, or HTTP endpoint) in their ownconfig format — full per-client walkthroughs live in `docs/connectivity_guide.md` in theForgetful repo.## Auth and scopesA local server defaults to no-auth single-user mode — connect and go. Deployed servers usebearer tokens or OAuth (the server's configured provider). `FORGETFUL_SCOPES` on the serverside sets a capability ceiling (e.g. read-only) that both MCP and CLI honour; a client thatshould only recall can be scoped so writes are refused.## Verify — the completion criterionBehavioural, not configurational:1. `discover_forgetful_tools` returns categories, and they match the server's enabled feature flags (skills/files/plans appear only when enabled).2. One `execute_forgetful_tool` round-trip returns real data — `get_current_user` or `list_projects` both work as smoke calls.Done when: both pass in the client that was just wired, in a fresh session.## Delegation boundaryRun Forgetful MCP calls in the main conversation — subagents do not inherit MCP toolaccess. When work must be delegated to a subagent, give it the CLI surface instead(`Bash` with the `forgetful` command travels into subagents; see `forgetful-cli-setup`).

Frequently asked questions