Beacons.ai

Beacons Creator MCP Server

A live, first-party Model Context Protocol server exposing a Beacons creator's own data to an agent. Discovered through the RFC 9728 Protected Resource Metadata document Beacons serves at https://beacons.ai/.well-known/oauth-protected-resource, which names this exact resource. Protected by an OAuth 2.1 authorization code + PKCE (S256) flow with open dynamic client registration and a single advertised scope, mcp:read, so the published surface is read-only. tools/list returns 401 with a WWW-Authenticate bearer challenge, meaning the tool manifest and every inputSchema require an authenticated creator; Beacons publishes no documentation, no llms.txt tool list and no help-centre article for this server, so no tool names are recorded.

GitHub

Documentation

📖
Authentication
https://raw.githubusercontent.com/api-evangelist/beaconsai/refs/heads/main/authentication/beaconsai-authentication.yml
📖
RateLimits
https://raw.githubusercontent.com/api-evangelist/beaconsai/refs/heads/main/rate-limits/beaconsai-rate-limits.yml

Other Resources

🔗
MCPServer
https://raw.githubusercontent.com/api-evangelist/beaconsai/refs/heads/main/mcp/beaconsai-mcp.yml
🔗
MCPServer
https://beacons.ai/api/v001/creator/mcp
🔗
OAuthScopes
https://raw.githubusercontent.com/api-evangelist/beaconsai/refs/heads/main/scopes/beaconsai-scopes.yml
🔗
ErrorCatalog
https://raw.githubusercontent.com/api-evangelist/beaconsai/refs/heads/main/errors/beaconsai-problem-types.yml
🔗
Conventions
https://raw.githubusercontent.com/api-evangelist/beaconsai/refs/heads/main/conventions/beaconsai-conventions.yml
🔗
APIsJSON
https://raw.githubusercontent.com/api-evangelist/beaconsai/refs/heads/main/apis.yml

API entry from apis.yml

apis.yml Raw ↑ 
name: Beacons Creator MCP Server
description: A live, first-party Model Context Protocol server exposing a Beacons creator's own data to
  an agent. Discovered through the RFC 9728 Protected Resource Metadata document Beacons serves at https://beacons.ai/.well-known/oauth-protected-resource,
  which names this exact resource. Protected by an OAuth 2.1 authorization code + PKCE (S256) flow with
  open dynamic client registration and a single advertised scope, mcp:read, so the published surface is
  read-only. tools/list returns 401 with a WWW-Authenticate bearer challenge, meaning the tool manifest
  and every inputSchema require an authenticated creator; Beacons publishes no documentation, no llms.txt
  tool list and no help-centre article for this server, so no tool names are recorded.
humanURL: https://beacons.ai
baseURL: https://beacons.ai/api/v001/creator/mcp
tags:
- mcp
- agent-native
- creator-economy
- link-in-bio
- oauth
properties:
- type: MCPServer
  url: mcp/beaconsai-mcp.yml
- type: MCPServer
  url: https://beacons.ai/api/v001/creator/mcp
- type: Authentication
  url: authentication/beaconsai-authentication.yml
- type: OAuthScopes
  url: scopes/beaconsai-scopes.yml
- type: ErrorCatalog
  url: errors/beaconsai-problem-types.yml
- type: RateLimits
  url: rate-limits/beaconsai-rate-limits.yml
- type: Conventions
  url: conventions/beaconsai-conventions.yml