PR-Braincells

Created By
haydulskia year ago
mcp server
Overview

what is PR-Braincells?

PR-Braincells is a test node server designed for handling markdown files, allowing users to generate helpful answers from properly formatted markdown content stored in a designated directory.

how to use PR-Braincells?

To use PR-Braincells, clone the repository, install the necessary dependencies, and configure the server in your preferred IDE. Set the CELLS_DIRECTORY environment variable to point to the directory containing your markdown files.

key features of PR-Braincells?

  • Supports markdown file processing for generating answers.
  • Easy setup with npm and environment variable configuration.
  • Customizable server command and arguments for flexibility.

use cases of PR-Braincells?

  1. Creating a knowledge base from markdown files.
  2. Developing a Q&A system that utilizes markdown content.
  3. Automating responses based on markdown documentation.

FAQ from PR-Braincells?

  • What is the purpose of the CELLS_DIRECTORY variable?

It specifies the directory where the markdown files are stored for processing.

  • How do I install PR-Braincells?

Clone the repository and run npm install to set up the project.

  • Can I customize the server command?

Yes, you can modify the mcp.json configuration to change the server command and its arguments.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
haydulski
Star
0
Language
TypeScript
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.

8 hours ago