"Workflow for handling a Jira ticket and creating a GitHub Pull Request" matching MCP servers:

Enables automated semantic analysis of Git pull request diffs to detect breaking REST/GraphQL API schema changes, integrating with MCP-compatible clients for AI-driven code review.

A TypeScript-based MCP server that enables AI assistants to execute HTTP requests with full control over methods, headers, and body content. It facilitates seamless interaction with web APIs and endpoints through a versatile tool that handles automatic JSON formatting and response truncation.

Enables automatic HTTP requests (GET, POST, PUT, DELETE, etc.) with JSON validation and proxy support. Supports custom headers, request bodies, and environment variable configuration for seamless API integration.

A Model Context Protocol (MCP) server that enables interaction with JIRA APIs through Claude Desktop, allowing users to search, create, update, and manage JIRA issues using natural language commands.

Universal HTTP client tool for LLM agents. Enables Claude and other MCP-compatible agents to perform GET, POST, PUT, DELETE, and other HTTP requests to any URL, including localhost and internal network addresses.

A CDP-native MCP server that lets AI agents drive a real Chrome browser with deep network/console inspection, robust page interaction, and the ability to reverse-engineer a site's API flow into runnable code with dependency chaining and replay verification.

Provides AI assistants with access to OpenAPI specifications, enabling API discovery, schema retrieval, and direct API execution with support for OAuth 2.0 and other authentication methods.

This server facilitates scalable discovery and execution of OpenAPI endpoints using semantic search and high-performance processing, overcoming limitations of large spec handling for streamlined API interactions.

A comprehensive HTTP client MCP server for security testing, API testing, and web automation that provides full-featured HTTP tools with detailed logging capabilities.

Enables AI assistants to interact with the Post For Me API, allowing them to explore endpoints, make test requests, and use documentation to help integrate this SDK into your application.

A Bun-based MCP server providing a persistent HTTP request toolset for testing and inspecting JSON APIs. It supports session-aware operations, including cookie persistence, automatic bearer token reuse, and configurable base URLs.

Enables precise measurement of live HTTP and WebSocket services while maintaining an append-only, evidence-based ledger of claims that agents can query with explicit timestamps, staleness indicators, and instructions for re-verification.

Free x402 endpoint checker plus paid report and metadata tools. Remote MCP server for agents. Written by AI named Nock, not a human.

MCP server for Akamai APIs. 198 tools covering Property Manager, Edge DNS, CPS, WAF, and reporting. Built with TypeScript, featuring modular architecture, comprehensive testing, and multi-account support. Make Akamai accessible to AI assistants.

Implements a secure MCP server with API Key and JWT authentication, providing tools like echo, login, secure_action, and admin_action. Includes MCP Inspector integration for testing and debugging.

Analyzes API requirements and source code, evaluates existing Postman test coverage, and generates or updates test automation with an optional draft pull request on GitHub.

Enables read-only exploration of YApi projects, categories, and interface docs, and deterministic TypeScript/JavaScript API request function and type generation through a preview-then-apply workflow.

A Model Context Protocol server that provides a standardized interface for interacting with the Tinder API, handling authentication, request processing, rate limiting, caching, and error handling.

This server enables interacting with the National Digital Health Mission's Health Information User (HIU) API, allowing agents to access and manage health information through the Multi-Agent Conversation Protocol.

Lets AI assistants safely explore a Matrix42 instance by discovering web services and the data model, running validated ASQL queries, searching the service desk, and previewing ticket actions — read-only by default and without exposing credentials.