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

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 LLMs to list, create, and comment on GitHub issues using your own GitHub identity via stdio transport.

Web scraper and token compressor that converts HTML to clean markdown with 70-80% fewer tokens. Single-page compression and multi-page BFS crawling with auto-fallback fetch modes.

A standalone MCP server that exposes a narrow set of GitHub Issues tools for a single repository, securely handling a GitHub personal access token so agents never see the credential.

Enables LLMs to make HTTP requests with OAuth2, session cookies, retry logic, and cURL command generation, while providing security features like SSRF protection and TLS enforcement.

Enables agents to run support workflows across Gmail, Linear, Stripe, Slack, Notion and other apps — turning support email into tracked bugs with drafted replies, handling refunds end to end, and replying in-thread once issues are fixed.

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

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

An MCP server that acts as a governed customer-support tool, resolving questions only when the knowledge base supports a cited, grounded answer and honestly escalating everything else with provenance and evidence.

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.

HTTP Inspector MCP Server enables sending arbitrary HTTP requests, viewing history via a web panel, and taking screenshots of the panel for AI penetration testing workflows.

MCP server for generating negative-space print supports for 3D models (STL/OBJ/STEP) via the negative.support API.

Enables AI clients to search and count indexed files and folders through Everything's HTTP JSON API, retrieve real-time file metadata, reveal items in Explorer, and automatically launch Everything with UAC when needed.

Enables AI agents to send HTTP requests to any endpoint with full control over methods, headers, query parameters, and request bodies.

Manages the state of a chess game for LLMs/agents without suggesting moves, providing tools to create/reset game, add moves, get status, and check legality.

A local stdio MCP server that brings scattered tickets, transactions, and current policies together so a model can retrieve evidence, assess cases, and prepare reply and escalation drafts. All writes stay local and pending human review, with no ability to send messages, move money, change accounts, or publish content.

Enables read-only lookup of support tickets and ticket lists through two tools, returning only bounded fields like ID, status, title and note. Tenant filtering and argument validation confine every read to the configured organization, with denied access and upstream failures surfaced as explicit results.

Enables Claude to manage customers and support tickets through database-backed CRUD tools, contextual customer and knowledge resources, and a reusable ticket-triage prompt.

Helps support engineers find similar GitHub issues to speed up troubleshooting by searching repositories and calculating similarity scores based on issue descriptions.

Exposes order status lookup and knowledge base search tools from the Support Agent AI over MCP, enabling MCP clients to handle customer support queries with grounded, citation-backed answers.

Enables AI clients to list, inspect, triage, and update support tickets via MCP tools, with a mocked dataset designed for swapping in real ticket sources later.

A read-only MCP server exposing SLURM, GPFS, Prometheus (node exporter + DCGM GPU metrics) and generic Elasticsearch exploration as diagnostic tools for LLM-based HPC support assistants.

Exposes a support-ticket inbox as tools an AI client can use to list, inspect, triage, and update tickets, including LLM-based category, priority, and sentiment classification with a drafted first response informed by similar past tickets. It works with a mocked dataset styled after a home-loan partner-support inbox, with the tool interface designed so a real ticket source could be swapped in later.

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.

First HTTP-native MCP server for Obsidian that solves stdio transport bugs, enabling AI assistants to manage Obsidian notes without crashes.

Enables AI assistants to handle customer support by looking up order status, semantically searching knowledge bases, and creating support tickets through MCP tools, with grounded answers and automated evaluations.

Provides order lookup, customer lookup, and refund issuance tools with categorized errors to ensure accurate routing and distinguish access failures from valid empty results.

Enables natural-language Q&A over customer support ticket data. Provides tools for schema inspection, SQL-based ticket counts and grouping, and full-text search for customer wording without requiring API keys.

Enables support engineers to analyze tickets against a help center with cited retrieval, role-gated and human-confirmed actions, and safety-gated evaluation.