MCP Server GDB

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is MCP Server GDB?

MCP Server GDB is a GDB/MI protocol server based on the MCP protocol, designed to provide remote application debugging capabilities with the assistance of AI.

how to use MCP Server GDB?

To use MCP Server GDB, run the server directly and choose between two transport modes: Standard input/output or Server-Sent Events. You can also configure the server settings through the configuration file or environment variables.

key features of MCP Server GDB?

  • Create and manage GDB debug sessions
  • Set and manage breakpoints
  • View stack information and variables
  • Control program execution (run, pause, step, etc.)
  • Support for concurrent multi-session debugging

use cases of MCP Server GDB?

  1. Debugging applications remotely with AI assistance.
  2. Managing multiple debugging sessions simultaneously.
  3. Analyzing stack frames and local variables during debugging.

FAQ from MCP Server GDB?

  • What programming languages does MCP Server GDB support?

MCP Server GDB can be used with any programming language that supports GDB.

  • Is there a graphical interface for MCP Server GDB?

No, MCP Server GDB is a command-line tool designed for remote debugging.

  • How can I install MCP Server GDB?

You can install it by downloading pre-built binaries or by building it from source using Cargo.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
Rust
License
MIT license
Tags

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago