Public MCP API
AI agents can browse our Notion templates, blog posts and current offer through a public, read-only Model Context Protocol (MCP) server.
Connect
Endpoint: https://jithinrajiv.com/mcp. Transport: Streamable HTTP with JSON responses and no sessions. Supported protocol versions: 2025-06-18, 2025-03-26 and 2024-11-05.
No sign-in, API key, OAuth authorization or scopes are required. This website does not operate an OAuth authorization server or expose an OAuth-protected public API. The private content editor signs in through GitHub separately.
Request safeguards
Requests must use JSON and fit within 64 KiB. Batches contain 1 to 20 messages. Each server process allows up to 120 requests per client address per minute and returns HTTP 429 when the limit is reached. Slow request bodies time out after 10 seconds.
Native MCP clients may omit Origin. Browser requests must come from this website or an origin explicitly configured by its owner through MCP_ALLOWED_ORIGINS.
Available tools
list_templates: browse templates; optionaltype(all, free or premium) andquery.get_template: read template details; requires aslugfrom the template list.list_blog_posts: browse guides; optionalquery.get_current_offer: read the current sale and bundle price; no arguments.
Example request
Send a POST to the endpoint with Content-Type: application/json and Accept: application/json, text/event-stream. An MCP client should initialize first, send its initialized notification, then list or call tools.
{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": {
"name": "list_templates",
"arguments": {
"type": "free"
}
}
}Requests receive JSON-RPC results or errors. Notifications receive HTTP 202 with no body. GET event streams are not supported and return HTTP 405.
All tools are read-only. Purchases follow the returned Gumroad links; the MCP server does not accept payments or personal data.