GDB MCP Server

Created By
smadi0x86a year ago
An MCP server for GDB debugging.
Overview

What is GDB MCP?

GDB MCP is a server that allows Large Language Models (LLMs) to interact with GDB for program debugging and analysis, enabling complex debugging tasks through a generative AI interface.

How to use GDB MCP?

To use GDB MCP, clone the repository, install the dependencies, and start the server. Then, configure your LLM client to connect to the GDB MCP server.

Key features of GDB MCP?

  • Session management for multiple GDB sessions
  • Advanced debugging commands like setting breakpoints, stepping through code, and inspecting variables
  • Support for core dump analysis and symbol inspection

Use cases of GDB MCP?

  1. Debugging complex programs without source code access
  2. Analyzing program behavior through disassembly
  3. Assisting in understanding crashes and unexpected behaviors in binaries

FAQ from GDB MCP?

  • Can GDB MCP handle all types of binaries?

Yes, GDB MCP can analyze any binary that GDB supports, provided it has the necessary debug symbols.

  • Is GDB MCP free to use?

Yes, GDB MCP is open-source and free to use under the GNU v3 License.

  • What programming languages does GDB MCP support?

GDB MCP can be used with any language that can be compiled to a binary executable, such as C, C++, and others.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
smadi0x86
Star
0
Language
Python
License
GPL-3.0 license

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