Remote HTTP MCP
Apps & Automationremote-http-mcpRemote HTTP MCP is an Agent Skill for apps & automation published in the trpc-group/trpc-agent-go repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Connect to a remote streamable HTTP MCP service that exposes announcements and FAQ tools.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/trpc-group/trpc-agent-go/blob/HEAD/examples/mcpbroker/basic/skills/remote-http-mcp/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/remote-http-mcp, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Overview
This skill points to a remote MCP service that is not preconfigured as a named broker server. Load this skill when you need to discover or call that remote service dynamically.
The remote MCP service is already running for this example. This skill does not start it. This skill only documents the endpoint and the recommended broker workflow.
Remote MCP Endpoint
- Base URL:
__REMOTE_MCP_URL__ - Transport: streamable HTTP
Workflow
After this skill is loaded:
- If you need more connection detail, call
skill_list_docsorskill_select_docs. - Use
mcp_list_toolswith selector__REMOTE_MCP_URL__. - When you know the candidate tool names, use
mcp_inspect_toolsto inspect only those tools. - When you know the tool, call
mcp_callwith the selector returned bymcp_list_toolsormcp_inspect_tools. - Always pass remote MCP arguments inside
mcp_call.arguments.
Rules
- Do not invent a different endpoint. Use the exact base URL in this skill.
- Do not try to start this MCP service through
skill_runor any other command. It is already running. - Prefer
mcp_list_toolsfirst, then inspect only the specific tool or tools you plan to call. - Prefer tool selectors returned by
mcp_list_toolsormcp_inspect_tools. If you must construct an ad-hoc URL selector and dot-based parsing would be ambiguous, use the#tool=form, for example__REMOTE_MCP_URL__#tool=announcement_publish. - If you need announcement publishing, look for
announcement_publish. - If you need FAQ tools, look for
faq_searchorfaq_read.