beyond

Beyond MCP Server is an extensible MCP (Model Context Protocol) server that provides standardized access to social platform data and on-chain data. It currently offers a full Farcaster integration via the Neynar API, with a placeholder for Twitter integration; the architecture is designed to easily add additional providers in the future. The server exposes a set of MCP-compliant resources and tools for querying content, profiles, wallets, threads, and trending information across supported platforms. It supports both stdio and HTTP/SSE transports for flexible integration with agents like Claude or other LLM workflows. To start, ensure you have a Neynar API key and use the provided npm scripts to build and run the server in your preferred mode (stdio or HTTP/SSE). The available tools focus on content discovery and retrieval across platforms, including search, profiles, wallet-based lookups, threads, and trending data, as well as prompt helpers to analyze and summarize content.

Prerequisites:

• Node.js 16+ installed on your machine
• Neynar API key for Farcaster access
• Git (optional, for cloning the repo)

Installation steps:

1. Clone the repository

git clone https://github.com/yourusername/beyond-mcp-server.git
cd beyond-mcp-server

2. Install dependencies

npm install

3. Create a .env file from the template (optional, env vars can also be set directly in the MCP config)

cp .env.example .env
# Edit .env with your API keys

4. Configure environment variables

• Required: NEYNAR_API_KEY in your environment
• You can obtain a Neynar API key from https://neynar.com/

5. Build and run the server

npm run build
npm start  # For stdio mode (default)
# OR
npm run start:http  # For HTTP/SSE mode

6. (Optional) Run in development mode

npm run dev        # stdio mode
npm run dev:http   # HTTP mode

Notes and tips:

• The server relies on Neynar for Farcaster access; without a valid NEYNAR_API_KEY, Farcaster endpoints will not function.
• The README shows example Claude Desktop configurations that pass the server as a long-running process; you can replicate these settings in your environment by specifying the node path to your built dist/index.js and providing environment variables in the config.
• Supported provider switches: ENABLE_FARCASTER and ENABLE_TWITTER allow you to enable or disable specific platforms at runtime via environment variables.
• The MCP capabilities cover a broad set of resources and prompts including search, profiles, wallet balances, threads, trending topics, channels, and bulk channel searches. You can customize which providers are enabled by editing the environment or the provider registry in the codebase.
• If you encounter transport issues, verify that your host can reach the Neynar API and that the server is started with the correct mode (stdio vs HTTP/SSE).
• For CLI-based testing, you can simulate MCP calls using the supported mcp endpoints and validate responses against the MCP specification.