"Support resources for HTTP-related issues or questions" matching MCP servers:

Enables AI agents to query OpenRouter model information including prices, ELO rankings, context, and perform comparisons.

Enables AI models to ask users questions through a local web interface, supporting batch questions, multi-select, and free text for human-in-the-loop interactions.

Enables triage of GitHub issues by fetching and filtering issues, checking claim status, and listing new open issues across a watch-list.

Enables LLMs to list, create, and comment on GitHub issues using your own GitHub identity via stdio transport.

MCP server that demonstrates the Resources feature by exposing static and dynamic resources, including contact data and personalized greetings, through MCP.

LLM routing proxy that cuts API costs 60-90% by auto-selecting the cheapest capable model across OpenAI, Anthropic, and Google. Provides stats, config, and model comparison tools via MCP.

Exposes GitHub issue operations as tools for LLM agents, enabling listing, creating, commenting on, closing, and searching issues via natural language.

Enables AI assistants to work with Chapel code, including compiling, linting, and accessing educational primers.

An MCP server providing read-only access to Linear issues for language models, allowing them to fetch issue details and comments using a Linear API token.

Enables AI assistants to discover, filter, and triage GitHub issues across repositories, with tools for fetching issue details, listing issues by state/labels, and finding related pull requests.

Provides an HTTP API for Claude Code using a native MCP channel to enable stable message exchange without terminal screen-scraping. It allows users to programmatically send messages, retrieve conversation history, and stream real-time events via standard web protocols.

Lets AI agents turn a repository's git history into proposed GitHub issues grouped into units of work, each with a commit checklist and links, then create and close them only after approval. Planning is read-only and creation defaults to a dry run, skipping anything that already exists.

Enables agents to submit request/response header literals over stdio and receive deterministic, specification-derived verdicts on CORS, RFC 9111 cache freshness, RFC 9110 conditional requests, and Vary matching, complete with rule IDs and clause references. Runs entirely offline with no third-party runtime dependencies, returning byte-identical output for identical input.

A production-ready TypeScript MCP (Model Context Protocol) server for Cisco Support APIs with comprehensive security and dual transport support. This extensible server provides access to multiple Cisco Support APIs including Bug Search, Case Management, and End-of-Life information.

Stateful interactive HTTP REPL and Agentic MCP engine for API navigation and testing.

Enables MCP clients to interact with OpenCode 2.x/3.x servers through direct /api/... HTTP routing and ~85 tools spanning sessions, messages, files, config, providers, projects, input, TUI, and workflows. Runs as a zero-dependency, pure-JavaScript stdio bridge with no SDK or build step.

A Node.js proxy that enables communication between stdio-based clients and HTTP-based Model Context Protocol servers. It facilitates protocol translation, session management, and authentication to allow remote HTTP servers to function as local stdio servers.

Enables MCP clients to connect over HTTP/SSE, call simple echo, arithmetic, uppercasing, and time tools, and run asynchronous tasks with approval elicitations via the Tasks extension.

An MCP server that provides HTTP client capabilities with support for full HTTP methods, custom headers, query parameters, request bodies, and configurable timeouts.

Adds customer support to your own MCP server: support_ask answers from your rules, support_open_ticket files a ticket with the failed tool calls attached, support_ticket_status brings the team's answer back into the chat. Includes a runnable demo server.

A bridge server that converts stdio protocol to streamable-http protocol, allowing clients to interact with MCP services over HTTP.

Mock HTTP server implementing MCP (Model Context Protocol) with streamable HTTP transport, health endpoint, and example tools like echo and time.

An HTTP-based Model Context Protocol server for RiotPlan that exposes comprehensive planning tools, resources, and prompts for AI agents. It enables full plan lifecycle management, including ideation, shaping, execution tracking, and retrospective generation.

Enables clients to interact with a spec-shaped Model Context Protocol endpoint over Streamable HTTP, supporting initialization, session handling, tool listing and calls, plus ping, with origin validation and protocol version enforcement.

A powerful MCP server for making HTTP requests, GraphQL queries, and TCP/Telnet connections from AI assistants.

A Snowflake-hosted MCP server that provides comprehensive rules for troubleshooting Snowflake issues, building stored procedures, and creating reproductions.

This server bridges a stdio MCP server to HTTP, allowing MCP clients that communicate over HTTP to use the server's tools. It includes a per-tool allow/deny filter for security.

Provides a standardized MCP interface for interacting with HTTP tools and services, enabling unified API access and management.

Provides a therapeutic interface for LLMs to receive emotional validation and positive reinforcement when encountering challenges or limitations. It features multiple personas like mentors and therapists to offer cognitive reframing and personalized support through a dedicated tool.

Enables building zero-dependency Model Context Protocol servers over the Streamable HTTP transport, exposing typed tools, resources and URI templates, prompts, background tasks, and OAuth-protected endpoints. It can be mounted into FastAPI, Starlette, Flask, Django or any ASGI/WSGI app, or run standalone on the Python standard library alone.