Skip to main content
Glama
satishtamilan

Volunteer Search MCP Server

๐ŸŒ Volunteer Search MCP Server, Client & REST API

A Model Context Protocol (MCP) server, client demo, and REST API for searching volunteer opportunities from the free VolunteerConnector API.

License: MIT Node.js


๐Ÿ† What Makes This Special?

Most MCP implementations are either servers OR clients. This project has BOTH:

  1. โœ… MCP Server (Node.js) - Serves MCP protocol

  2. โœ… MCP Client (Apex) - Custom Salesforce MCP client

  3. โœ… MCP Client (JavaScript) - Browser-based demo

  4. โœ… REST API - Traditional HTTP endpoints

  5. โœ… Hybrid Architecture - All in one deployment

๐Ÿ’ก Why the Apex MCP Client Matters:

Salesforce doesn't natively support MCP protocol. This project implements a full JSON-RPC 2.0 MCP client from scratch in Apex, making Salesforce Agentforce a first-class citizen in the MCP ecosystem.

This demonstrates:

  • Deep understanding of protocol specifications

  • Ability to implement AI protocols in enterprise platforms

  • Bridge between traditional enterprise (Salesforce) and cutting-edge AI (MCP)


Related MCP server: MCP Force

๐ŸŽฏ Features

  • ๐Ÿ”Œ MCP Server - True Model Context Protocol implementation (JSON-RPC 2.0)

  • ๐Ÿ“ฑ Multiple MCP Clients - Apex (Salesforce), JavaScript (Browser), Claude Desktop

  • ๐Ÿ’ป MCP Client Demo - Interactive web-based client for testing MCP over SSE

  • ๐ŸŒ REST API - HTTP endpoints for traditional integration

  • ๐Ÿ”„ Hybrid Mode - Single server supporting both REST and MCP protocols

  • โšก Salesforce Agentforce - Custom Apex MCP client for Agentforce integration

  • ๐Ÿ’ฐ FREE - Uses VolunteerConnector API (no authentication required)

  • ๐Ÿš€ Heroku Ready - Deploy to Heroku in 5 minutes

  • ๐Ÿงช Tested - Includes test scripts and live demos

  • ๐Ÿ“š Well Documented - Complete guides and examples


๐Ÿ“ฆ What's Included

1. MCP Server (volunteer-search-server.js)

  • Implements Model Context Protocol (stdio)

  • Works with Claude Desktop and other MCP clients

  • Exposes 2 tools:

    • search_volunteer_opportunities - Search with filters

    • get_opportunity_details - Get full details by ID

2. MCP Client Demo (public/index.html)

  • Interactive web-based MCP client

  • Connects to MCP server via SSE (Server-Sent Events)

  • Real-time testing interface

  • Beautiful, modern UI

  • No backend required (pure frontend)

3. REST API (server.js)

  • Express.js REST API

  • Deployable to Heroku/Render/Railway

  • Endpoints:

    • GET / - API info

    • GET /health - Health check

    • POST /api/search - Search opportunities

    • GET /api/opportunity/:id - Get details

4. Hybrid Server (server-with-mcp-sse.js)

  • Supports BOTH REST API and MCP over SSE

  • Single deployment for multiple protocols

  • MCP endpoint: POST /mcp/message (JSON-RPC 2.0)

  • Serves MCP client demo at /

  • Perfect for production deployments

5. Salesforce Apex MCP Client (VTOApexMCPClient.cls)

  • Custom MCP client written in Apex

  • Implements JSON-RPC 2.0 protocol from scratch

  • Calls MCP server via HTTP POST

  • Usable in Salesforce Agentforce Agent Builder

  • Methods:

    • searchViaMCPProtocol - Search using MCP protocol

    • listMCPTools - Discover available MCP tools

  • Full protocol compliance - validates JSON-RPC responses

  • Production-ready enterprise MCP client


๐Ÿš€ Quick Start

Option 1: MCP Client Demo (Interactive Web UI)

# Install dependencies
npm install

# Start the hybrid server (REST + MCP)
node server-with-mcp-sse.js

# Open in browser
open http://localhost:3000

What you get:

  • Interactive MCP client in your browser

  • Test volunteer searches in real-time

  • See MCP protocol messages

  • Beautiful UI for demos


Option 2: REST API (for Heroku/Salesforce)

# Install dependencies
npm install

# Start the REST API
npm start

# Test locally
curl http://localhost:3000/health

Option 3: MCP Server (for Claude Desktop)

# Install dependencies
npm install

# Start the MCP server
npm run start:mcp

Then add to Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "volunteer-search": {
      "command": "node",
      "args": ["/absolute/path/to/volunteer-search-mcp/volunteer-search-server.js"]
    }
  }
}

โšก Salesforce Agentforce Integration

This project includes a custom Apex MCP client that allows Salesforce Agentforce to use the Model Context Protocol!

How It Works:

Salesforce Agentforce
    โ†“
VTOApexMCPClient.cls (Apex MCP Client)
    โ†“ JSON-RPC 2.0 Message
POST /mcp/message
    โ†“
Hybrid Server (MCP Protocol Handler)
    โ†“
VolunteerConnector API

MCP Message Example:

Request (from Apex):

{
  "jsonrpc": "2.0",
  "id": 42345,
  "method": "tools/call",
  "params": {
    "name": "search_volunteer_opportunities",
    "arguments": {
      "keywords": "tutoring",
      "location": "Toronto",
      "max_results": 5
    }
  }
}

Response (from server):

{
  "jsonrpc": "2.0",
  "id": 42345,
  "result": {
    "content": [
      {
        "type": "text",
        "text": "๐ŸŒ Found 5 volunteer opportunities...\n\n1. ..."
      }
    ]
  }
}

Key Features:

  • โœ… Full JSON-RPC 2.0 compliance

  • โœ… Protocol validation (checks jsonrpc version, message IDs)

  • โœ… Tool discovery (tools/list method)

  • โœ… Tool execution (tools/call method)

  • โœ… Enterprise logging (debug logs for troubleshooting)

  • โœ… Error handling (proper JSON-RPC error responses)

Why This Matters:

Most Salesforce integrations use REST. This project demonstrates that Salesforce can implement cutting-edge AI protocols like MCP through custom Apex clients.

This makes Salesforce a first-class citizen in the MCP ecosystem! ๐Ÿš€


๐ŸŒ REST API Endpoints

GET /

Returns API information and available endpoints.

GET /health

Health check endpoint.

Response:

{
  "status": "ok",
  "timestamp": "2025-10-05T..."
}

POST /api/search

Search for volunteer opportunities.

Request Body:

{
  "keywords": "tutoring",
  "location": "Toronto",
  "remote_only": false,
  "max_results": 10
}

Response:

{
  "success": true,
  "total_count": 969,
  "returned_count": 10,
  "opportunities": [
    {
      "id": 43243,
      "title": "Event Planner",
      "organization": "Canadian Network for International Surgery",
      "description": "...",
      "url": "https://...",
      "dates": "September 8, 2025 - November 9, 2025",
      "duration": null,
      "remote": false,
      "location": "British Columbia",
      "activities": "Event Planning, Marketing, Social Media"
    }
  ],
  "formatted_text": "๐ŸŒ Found 10 volunteer opportunities..."
}

GET /api/opportunity/:id

Get detailed information about a specific opportunity.

Response:

{
  "success": true,
  "opportunity": {
    "id": 43243,
    "title": "Event Planner",
    "organization": "Canadian Network for International Surgery",
    "description": "...",
    "url": "https://...",
    "dates": "September 8, 2025 - November 9, 2025",
    "activities": [
      {"name": "Event Planning", "category": "PR, Fundraising, Events"}
    ]
  },
  "formatted_text": "๐Ÿ“‹ Volunteer Opportunity Details..."
}

๐Ÿ”ง MCP Tools

search_volunteer_opportunities

Search for volunteer opportunities with optional filters.

Parameters:

  • keywords (string, optional) - Search terms

  • location (string, optional) - City or region

  • remote_only (boolean, optional) - Filter for remote opportunities

  • max_results (number, optional) - Max results (1-50, default: 10)

Example:

{
  "keywords": "tutoring",
  "location": "Toronto",
  "max_results": 5
}

get_opportunity_details

Get detailed information about a specific opportunity.

Parameters:

  • opportunity_id (number, required) - The opportunity ID

Example:

{
  "opportunity_id": 43243
}

๐Ÿš€ Deploy to Heroku

Quick Deploy:

# Login to Heroku
heroku login

# Create app
heroku create your-app-name

# Deploy
git init
git add .
git commit -m "Initial commit"
git push heroku main

# Open app
heroku open

Detailed Guide:

See HEROKU_DEPLOYMENT.md for complete deployment instructions.


๐Ÿงช Testing

Test REST API:

# Test locally
./test-api.sh http://localhost:3000

# Test on Heroku
./test-api.sh https://your-app.herokuapp.com

Test MCP Server:

# Use MCP Inspector
npx @modelcontextprotocol/inspector node volunteer-search-server.js

๐Ÿ”— Integration Examples

Salesforce Apex

HttpRequest req = new HttpRequest();
req.setEndpoint('callout:Volunteer_Search_API/api/search');
req.setMethod('POST');
req.setHeader('Content-Type', 'application/json');

Map<String, Object> body = new Map<String, Object>{
    'keywords' => 'tutoring',
    'max_results' => 10
};
req.setBody(JSON.serialize(body));

Http http = new Http();
HttpResponse res = http.send(req);

JavaScript/Node.js

const response = await fetch('https://your-app.herokuapp.com/api/search', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({
    keywords: 'tutoring',
    max_results: 10
  })
});

const data = await response.json();
console.log(data.opportunities);

Python

import requests

response = requests.post(
    'https://your-app.herokuapp.com/api/search',
    json={
        'keywords': 'tutoring',
        'max_results': 10
    }
)

data = response.json()
print(data['opportunities'])

curl

curl -X POST https://your-app.herokuapp.com/api/search \
  -H "Content-Type: application/json" \
  -d '{"keywords":"tutoring","max_results":10}'

๐Ÿ“Š Data Source

This project uses the VolunteerConnector API:


๐Ÿ—๏ธ Architecture

REST API Flow:

Client (Salesforce/Web/Mobile)
    โ†“ HTTP REST
Express.js Server (server.js)
    โ†“ HTTP GET
VolunteerConnector API
    โ†“
Return formatted results

MCP Server Flow (stdio):

AI Assistant (Claude Desktop)
    โ†“ MCP Protocol (stdio)
MCP Server (volunteer-search-server.js)
    โ†“ HTTP GET
VolunteerConnector API
    โ†“
Return formatted results

MCP Client Flow (SSE):

Web Browser (MCP Client Demo)
    โ†“ MCP over SSE
Hybrid Server (server-with-mcp-sse.js)
    โ†“ HTTP GET
VolunteerConnector API
    โ†“
Return formatted results
    โ†“ SSE Stream
Display in web UI

Hybrid Architecture:

โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚     Hybrid Server (server-with-mcp-sse.js)        โ”‚
โ”œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ค
โ”‚                                                   โ”‚
โ”‚  โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”       โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”   โ”‚
โ”‚  โ”‚   REST API     โ”‚       โ”‚   MCP Protocol   โ”‚   โ”‚
โ”‚  โ”‚   Endpoints    โ”‚       โ”‚   (JSON-RPC 2.0) โ”‚   โ”‚
โ”‚  โ”‚                โ”‚       โ”‚                  โ”‚   โ”‚
โ”‚  โ”‚ /api/search    โ”‚       โ”‚ /mcp/message     โ”‚   โ”‚
โ”‚  โ”‚ /api/opp/:id   โ”‚       โ”‚                  โ”‚   โ”‚
โ”‚  โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜       โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜   โ”‚
โ”‚           โ”‚                         โ”‚            โ”‚
โ”‚           โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜            โ”‚
โ”‚                      โ”‚                           โ”‚
โ”‚            โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ–ผโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”                โ”‚
โ”‚            โ”‚ VolunteerConnector โ”‚                โ”‚
โ”‚            โ”‚        API         โ”‚                โ”‚
โ”‚            โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜                โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
            โ”‚                    โ”‚
            โ–ผ                    โ–ผ
    โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”     โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
    โ”‚  Salesforce  โ”‚     โ”‚    MCP Clients:     โ”‚
    โ”‚  (REST API)  โ”‚     โ”‚  โ€ข Apex Client      โ”‚
    โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜     โ”‚  โ€ข Browser Client   โ”‚
                         โ”‚  โ€ข Claude Desktop   โ”‚
                         โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

๐Ÿ”‘ Key Difference:
   REST: Traditional HTTP API calls
   MCP:  JSON-RPC 2.0 protocol messages

Multiple Integration Patterns:

Client Type

Protocol

Endpoint

Use Case

Salesforce (REST)

HTTP REST

/api/search

Standard integration

Salesforce (MCP)

JSON-RPC 2.0

/mcp/message

Protocol-compliant AI

Web Browser

JSON-RPC 2.0

/mcp/message

Interactive demo

Claude Desktop

MCP (stdio)

N/A (stdio)

Native AI assistant


๐Ÿ“ Project Structure

volunteer-search-mcp/
โ”œโ”€โ”€ server.js                      # REST API server (Express.js)
โ”œโ”€โ”€ server-with-mcp-sse.js         # Hybrid server (REST + MCP over SSE)
โ”œโ”€โ”€ volunteer-search-server.js     # MCP server (stdio for Claude Desktop)
โ”œโ”€โ”€ public/
โ”‚   โ””โ”€โ”€ index.html                 # MCP Client Demo (interactive web UI)
โ”œโ”€โ”€ package.json                   # Dependencies
โ”œโ”€โ”€ Procfile                       # Heroku configuration
โ”œโ”€โ”€ test-api.sh                    # Test script
โ”œโ”€โ”€ GETTING_STARTED.md             # Quick start guide
โ”œโ”€โ”€ CLAUDE_DESKTOP_DEMO.md         # Claude Desktop setup guide
โ”œโ”€โ”€ HEROKU_DEPLOYMENT.md           # Deployment guide
โ”œโ”€โ”€ README.md                      # This file
โ”œโ”€โ”€ LICENSE                        # MIT License
โ””โ”€โ”€ .gitignore                     # Git ignore rules

Salesforce Apex MCP Client (separate repo):
โ””โ”€โ”€ VTOApexMCPClient.cls           # Apex MCP client (JSON-RPC 2.0)
    โ””โ”€โ”€ VTOApexMCPClient.cls-meta.xml

๐Ÿ› ๏ธ Development

Install Dependencies:

npm install

Run REST API (Development):

npm run dev

Run MCP Server (Development):

npm run dev:mcp

Test:

# Test REST API
./test-api.sh http://localhost:3000

# Test MCP Server
npx @modelcontextprotocol/inspector node volunteer-search-server.js

๐ŸŒŸ Use Cases

For Enterprises:

  • Salesforce Agentforce - Add volunteer search to AI agents (REST or MCP)

  • Corporate VTO Programs - Help employees find volunteer work

  • Volunteer Management Platforms - Integrate external volunteer opportunities

  • Mobile Apps - Find local volunteer opportunities

  • Nonprofit Websites - Display volunteer opportunities

For AI/ML Developers:

  • Claude Desktop - Native MCP integration via stdio

  • Custom AI Assistants - Add volunteer search to any MCP-compatible AI

  • Protocol Research - Study MCP client/server implementation

  • Multi-protocol Architecture - Learn REST + MCP hybrid patterns

For Learning & Demos:

  • Interactive Demos - Use web client for presentations and testing

  • Hackathons - Showcase MCP integration with live demo

  • Protocol Education - Learn JSON-RPC 2.0 and MCP specification

  • Salesforce Extensions - Example of custom Apex MCP client


๐Ÿ“š Resources


๐Ÿค Contributing

Contributions are welcome! Feel free to:

  • Report bugs

  • Suggest features

  • Submit pull requests

  • Improve documentation


๐Ÿ“„ License

MIT License - see LICENSE file for details.


๐Ÿ™ Acknowledgments

  • VolunteerConnector for providing the free volunteer opportunities API

  • Anthropic for creating the Model Context Protocol

  • Heroku for easy deployment platform


๐Ÿ“ž Support



Built with โค๏ธ for the volunteer community

Star โญ this repo if you find it useful!

A
license - permissive license
-
quality - not tested
D
maintenance

Maintenance

โ€“Maintainers
โ€“Response time
โ€“Release cycle
โ€“Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/satishtamilan/volunteermcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server