Skill

connect-as-client

Use when you need to register a relay server as an MCP client in your local Claude install.

npx claudepluginhub danielrosehill/claude-code-plugins --plugin agent-relay

Tool Access

This skill uses the workspace's default tool permissions.

Preview

SKILL.md

Similar Skills

cache-components

139.3k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

Stats

Stars0

Forks0

Last CommitMay 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Connect as Client

When to use

After deploying a relay server with setup-relay-server

Adding a second Claude instance to an existing relay

Switching to a different relay endpoint

Inputs to gather

Relay URL (e.g., http://ubuntuvm:8844)

Client ID for this instance (e.g., claude-daniel-desktop)

Optional shared bearer token (if the relay requires it)

Procedure

Prompt the user for relay URL, client_id, and optional token.

Call claude mcp add with HTTP streamable transport, passing the relay URL.

Invoke the relay_status MCP tool to verify connectivity.

If successful, write the chosen client_id and relay URL to ${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/agent-relay/client.toml.

Display the relay status and confirm the client is registered.

Output / side effects

Relay registered in Claude's MCP config.

client.toml persisted under $CLAUDE_USER_DATA/agent-relay/ with client_id and relay URL.

User sees relay version, uptime, and a list of active sessions.

Safety / constraints

Bearer token (if provided) is stored in plaintext in config; assume the user controls file permissions.

Relay URL is validated with a live relay_status call before confirming registration.