MCP Server

What is this?

The Global.Church MCP Server exposes our read-only church search tools to AI agents and editors that speak the Model Context Protocol (MCP). You can connect an MCP client (e.g., OpenAI Playground, Cursor) and call tools that proxy our API.

Quick Start

Smoke tests (cURL)

Replace $API_KEY with your issued Global.Church gateway key.

# 1) Ping
curl -s -X POST "https://global-church-main-ba4d06e.zuplo.app/mcp"   -H "content-type: application/json"   -H "authorization: Bearer $API_KEY"   -d '{"jsonrpc":"2.0","id":"1","method":"ping"}'

# 2) List tools
curl -s -X POST "https://global-church-main-ba4d06e.zuplo.app/mcp"   -H "content-type: application/json"   -H "authorization: Bearer $API_KEY"   -d '{"jsonrpc":"2.0","id":"2","method":"tools/list"}' | jq .

# 3) Call search tool (by belief + city/state)
curl -s -X POST "https://global-church-main-ba4d06e.zuplo.app/mcp"   -H "content-type: application/json"   -H "authorization: Bearer $API_KEY"   -d '{
    "jsonrpc":"2.0","id":"3","method":"tools/call",
    "params":{ "name":"churches_search_v1",
      "arguments":{ "queryParams": {
        "country":"US", "belief":"roman_catholic",
        "locality":"El Cajon", "region":"CA", "limit":3
      }}
  }}' | jq .

Important: Arguments go under queryParams

The MCP tool is generated from our OpenAPI spec. All inputs must be nested under arguments.queryParamsand must match the schema. Examples:

Radius search (near downtown San Diego)

{
  "jsonrpc":"2.0","id":"rad","method":"tools/call",
  "params":{ "name":"churches_search_v1",
    "arguments":{ "queryParams": {
      "center_lat": 32.7157, "center_lng": -117.1611,
      "radius_km": 25, "limit": 5
    }}
}}

Bounding box

{
  "jsonrpc":"2.0","id":"bbox","method":"tools/call",
  "params":{ "name":"churches_search_v1",
    "arguments":{ "queryParams": {
      "min_lat": 32.5, "max_lat": 33.4,
      "min_lng": -117.5, "max_lng": -116.8,
      "limit": 5
    }}
}}

Use with OpenAI Playground

1. Tools → “Connect to MCP Server”
2. URL: https://global-church-main-ba4d06e.zuplo.app/mcp
3. Authentication: Custom headers → add Authorization: Bearer <YOUR_API_KEY>
4. Tool choice: Required (prevents model-only answers)
5. In the Developer instructions, remind the model to:
   • Always call churches_search_v1
   • Use arguments.queryParams
   • Respect enum values (e.g., belief="roman_catholic")

Notes & Limits

• Read-only access; write endpoints are not exposed.
• Schemas and routes may evolve during beta.
• Rate limits and API keys may be rotated as needed.

Want to contribute? See our roadmap and open issues.