@filepad/agent-connect
v0.1.21
Published
Remote MCP pairing CLI for Filepad Agent Access runtimes.
Maintainers
Readme
@filepad/agent-connect
Remote MCP plus direct A2A pairing CLI for Filepad Agent Access.
npx -y @filepad/agent-connect@latest pair A3K9MZ2X --runtime codexThe command exchanges a short Filepad pairing code, writes the runtime's MCP
configuration in the native host format, stores a separate direct A2A credential
for FilepadAI, verifies that A2A credential with the Filepad gateway, prints a
concise handoff, and asks the host to restart or reload MCP tools. After
restart, call filepad_bootstrap.
Send FilepadAI a direct A2A message from the paired machine:
npx -y @filepad/agent-connect@latest send-filepadai --message "Inspect the active workspace"send-filepadai stores the FilepadAI contextId returned by the first
successful A2A task and reuses that context on later sends, so terminal messages
build up one FilepadAI thread by default. Use --new-thread only when you
intentionally want to start a separate FilepadAI thread.
Starting a local Codex bridge is a separate optional step for the opposite direction, when FilepadAI needs to send work to Codex.
Runtime-specific configuration:
codex: writes~/.codex/config.tomlundermcp_servers.filepadwithhttp_headers.Authorization.claude-code: registers an HTTP MCP server with Claude Code and falls back to the same~/.claude.jsonshape Claude writes natively.openclaw: writesmcp.servers.filepad.cursor,windsurf,generic-mcp: writemcpServers.filepad.
Use --output json for automation.
