"How to remotely connect to an MCP running on a Raspberry Pi" matching MCP servers:

Enables MCP clients to interact with A2A agents through four ordinary tools, translating agent discovery, messaging, task reading, and cancellation between the A2A and MCP protocols, with support for the tasks extension.

An MCP server that turns a one-sentence idea into working, tested code using a pipeline of six AI agents, with optional deployment.

Turns any OpenAPI/Swagger specification into a functional MCP server, dynamically exposing API endpoints as LLM tools or generating standalone Python code.

MCP server that lets you drive Claude Code sessions hands-free by voice from any MCP client, enabling remote models to send prompts, monitor progress, and get results read back.

Enables Claude to use Google Gemini as a secondary AI through MCP for large-scale codebase analysis and complex reasoning tasks. Supports both Gemini Flash and Pro models with specialized functions for general queries and comprehensive code analysis.

Converts any REST API into MCP-compatible tools instantly by providing an OpenAPI/Swagger spec, enabling seamless integration with AI agents.

Acts as a bridge between standard REST/OpenAPI web APIs and the Model Context Protocol, dynamically converting REST endpoints into MCP tools for LLM clients like Cursor, Claude Desktop, and n8n.

Manages MCP server configurations and exposes their tools to the Pi agent through a single gateway, with on-demand startup and discovery.

Automatically converts OpenAPI/Swagger documents into MCP servers, enabling AI agents to call third-party REST APIs via the MCP protocol.

MCP server that routes Claude Desktop chat into Claude Code, enabling headless execution and terminal handoff with session continuity.

An MCP bridge for the Pi coding agent running in WSL, enabling task execution, research, review, and session management through MCP.

Exposes Pi execution nodes to any MCP client so it can dispatch sub-tasks to local or cloud models, poll and cancel them, and get command-based acceptance, diff-based evidence chains and automatic escalation to stronger models on failure.

A Model Context Protocol (MCP) server that automates generating LinkedIn post drafts from YouTube videos. This server provides high-quality, editable content drafts based on YouTube video transcripts.

Orchestrates multiple coding agents at once so an MCP client can delegate implementation work while retaining judgment: each agent runs in its own isolated git worktree and branch, claims the files it edits, and communicates via a mailbox and shared board. Supports blocking questions to the orchestrator, Codex-written acceptance tests locked before workers start, scope validation, and reporting on first-pass success.

Enables teams to securely store and retrieve credentials, view decrypted secrets or live OAuth tokens, and connect to third-party MCP servers through a unified MCP endpoint.

Enables Claude Code to hand off prompts, research, and adversarial reviews to non-Claude models such as GPT-5.5 and Gemini 3.1 Pro through the pi CLI, billed to an existing flat-rate subscription. Delegates run read-only and web-capable, with evidence tracking, continuation threads, and file-based output to keep context small.

Exposes pi as a sub-agent for MCP-capable coding assistants, enabling task dispatch, messaging, and interactive dialog handling via tools like pi_dispatch, pi_send, and pi_respond.

Enables web search for the pi coding agent using z.ai GLM native search with a DuckDuckGo fallback.

Enables Codex to supervise one or more local Pi coding-agent workers through bounded task execution, state polling, steering, aborting, and listing. Tasks can run in a direct working directory or isolated Git worktree while Codex remains the planner and reviewer.

Enables the Pi coding agent to drive Chrome through DevTools, providing browser automation tools, persistent or isolated profiles, screenshots, page analysis, and bundled agent policies.