Recurse MCP

Created By
namanyayga year ago
An MCP server for the Recurse Center
Overview

What is Recurse MCP?

Recurse MCP is a server that acts as a bridge between the Recurse Center's API and AI tools, allowing for seamless interaction with the Recurse Center's data.

How to use Recurse MCP?

To use Recurse MCP, clone the repository, create a .env file with your Recurse Center personal access token, install the dependencies, and run the server. The server will be accessible on port 9000 by default.

Key features of Recurse MCP?

  • Enables AI tools to interact with the Recurse Center API.
  • Allows searching for fellow Recursers and viewing their profiles.
  • Provides real-time information about who is at the hub and details about batches and locations.

Use cases of Recurse MCP?

  1. AI assistants can find and connect with other Recursers.
  2. Checking the current activity at the Recurse Center hub.
  3. Accessing batch information for better community engagement.

FAQ from Recurse MCP?

  • Can I use Recurse MCP with any AI tool?

Yes! Recurse MCP is compatible with any MCP-compatible AI assistant.

  • Do I need a Recurse Center API token?

Yes, a personal access token is required to access the Recurse Center API.

  • Is there any specific software requirement?

You need Node.js installed to run the server.

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