Vibe Coder MCP Server

Created By
freshtechbroa year ago
Vibe-Coder-MCP server extends AI assistants with specialized software development tools.
Overview

What is Vibe Coder MCP?

Vibe Coder MCP is a Model Context Protocol server designed to enhance AI assistants with advanced software development tools, facilitating tasks such as research, planning, and code generation.

How to use Vibe Coder MCP?

To use Vibe Coder MCP, set it up by following the installation guide, configure your environment variables, and integrate it with your AI assistant. You can then issue commands to perform various development tasks.

Key features of Vibe Coder MCP?

  • Semantic Request Routing for intelligent request handling.
  • Tool Registry Architecture for centralized tool management.
  • Direct LLM Calls for improved reliability.
  • Workflow Execution for predefined sequences of tool calls.
  • Code Generation and Refactoring capabilities.
  • Dependency Analysis and Git Integration.
  • Research and Planning tools for generating documentation.

Use cases of Vibe Coder MCP?

  1. Assisting in software development by generating code stubs.
  2. Performing deep research on technical topics.
  3. Creating project-specific development rules and PRDs.
  4. Analyzing project dependencies and summarizing Git changes.

FAQ from Vibe Coder MCP?

  • Can Vibe Coder MCP be used with any AI assistant?

Yes! It is designed to integrate with various AI assistants like Cursor and Cline AI.

  • Is Vibe Coder MCP free to use?

Yes! Vibe Coder MCP is open-source and free to use.

  • What programming languages does Vibe Coder MCP support?

Vibe Coder MCP primarily supports TypeScript, but it can assist with various programming languages through its tools.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
freshtechbro
Star
29
Language
TypeScript
License
View license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day 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.

6 hours ago