Index of every page on this site: llms.txt
All skills
jetbrains avatar

/managing-mcp-servers

@e85862d
by jetbrainsjetbrains/thinkrail8.4k stars
532
Run it yourself

Use when the user asks to add, change, remove, enable or disable an MCP server, or when an MCP tool is missing, needs sign-in, fails, or was blocked. ThinkRail runs pi in-process, so there is no `pi` command to call.

Use this Skill: https://skilld.dev/gh/jetbrains/thinkrail/managing-mcp-servers

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈60 tokens for metadata: the name and description. ≈778 when used: this file.

Description uses 3.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈239 characters, or 3.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Managing MCP servers in ThinkRail

ThinkRail uses pi's built-in MCP support but has no pi executable. Never run pi mcp add, pi mcp login or other pi commands; edit the configuration files and point the user at Settings › MCP servers for everything that needs them.

Where servers are configured

  • User level — pi's agent directory, usually ~/.pi/agent/mcp.json: available in every project.
  • This repository — .pi/mcp.json in the worktree, tracked in git. A server defined here does not run until the user approves it in Settings, and any later change to its entry needs approval again. It only loads when the user trusts the project.

Both files use pi's format:

{
  "mcpServers": {
    "docs": { "url": "https://example.com/mcp" },
    "browser": { "command": "npx", "args": ["-y", "@playwright/mcp@0.0.83"] }
  }
}
  • Pin package versions in args; never @latest.
  • Never write a secret into either file. Reference it as ${ENV_VAR} (from the host's environment) or !command (the command's output, for example !gh auth token), or let the user sign in.
  • exposure: deferred (the default here — load the server's tools with tool_search first), direct (a few always-useful tools), or hidden. codemode is treated as deferred.
  • Prefer the user-level file for personal servers; only put a server in .pi/mcp.json when the user wants it shared with the repository.

GitHub

GitHub is a recipe, not a preset: its hosted server, authenticated with the user's GitHub CLI sign-in. Add it to the user-level file (Settings › MCP servers offers the same entry under Paste JSON):

{
  "mcpServers": {
    "github": {
      "url": "https://api.githubcopilot.com/mcp/readonly",
      "headers": { "Authorization": "!t=$(gh auth token) && echo \"Bearer $t\"" }
    }
  }
}
  • /readonly is GitHub's documented read-only mode (same as an X-MCP-Readonly: true header). Use https://api.githubcopilot.com/mcp/ only when the user asks for tools that change data.
  • The header command runs each time a chat connects. While gh is logged out it fails instead of sending an empty token; the user runs gh auth login in a terminal.
  • Unverified: whether GitHub accepts the GitHub CLI token's scopes for every toolset. If the server rejects it, ask the user for a token in an environment variable: "Authorization": "Bearer ${GITHUB_TOKEN}".

After editing

The host reloads idle chats on its own and a busy chat picks the change up when it is idle. Tell the user when a step is theirs: approving a repository server, or Sign in for a server that uses OAuth (both in Settings › MCP servers). Do not ask them to restart ThinkRail.

Using MCP tools

  • Tools are named mcp__<server>__<tool>. For a deferred server, call tool_search to load them.
  • Subagents cannot call MCP tools: call them yourself and put what the subagent needs in its task.
  • ThinkRail asks the user before a call that may change data. A denied or cancelled call is final for that call; do not retry it without asking the user first.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts22d3 checks · Risk SAFE
  • Gen Agent Trust Hub22d

    The skill provides instructions for managing Model Context Protocol (MCP) servers, which involves writing shell commands to configuration files for authentication and dynamically loading tools. These features are inherent to the skill's purpose but introduce potential attack surfaces for command execution and indirect prompt injection.

  • Socket26d

    No alerts

  • Snyk26d

    Risk: LOW · No issues

Signed by skilld at e85862d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated last month

README badge

README badge for jetbrains/thinkrail/managing-mcp-servers