Last9 MCP Server

Created By
last9a year ago
Last9 MCP Server
Overview

What is Last9 MCP Server?

Last9 MCP Server is a Model Context Protocol server implementation that enables AI agents to seamlessly integrate real-time production context, such as logs, metrics, and traces, into local environments for faster code fixes.

How to use Last9 MCP Server?

To use the Last9 MCP Server, install it via Homebrew or NPM, configure it with the necessary environment variables, and integrate it with compatible applications like Claude, Cursor, or Windsurf.

Key features of Last9 MCP Server?

  • Real-time integration of production context into local environments.
  • Tools for fetching exceptions, service graphs, and filtered logs.
  • Compatibility with various IDEs and applications.

Use cases of Last9 MCP Server?

  1. Enhancing debugging processes by providing real-time logs and metrics.
  2. Streamlining code fixes with contextual information.
  3. Supporting developers in maintaining observability in their applications.

FAQ from Last9 MCP Server?

  • What is the Model Context Protocol?

The Model Context Protocol is a framework that allows AI agents to access and utilize production context for improved decision-making and automation.

  • Is Last9 MCP Server free to use?

Yes! Last9 MCP Server is free to use for developers.

  • What applications are compatible with Last9 MCP Server?

It works with Claude, Cursor, Windsurf, and VSCode (GitHub Copilot).

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
last9
Star
32
Language
Go
License
Apache-2.0 license

Recommend Servers

View All
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.

7 hours ago