Skip to content
TalksChaowalit Greepoke

For developers and AI agents

MCP API

Talks answers a small, MCP-style JSON-RPC 2.0 API at /api/mcp. It is read-only, needs no key, and returns the same content this site shows.

Call it

Send a POST with a JSON-RPC body. A plain browser visit (GET) is not supported.

curl -s https://talks.bookchaowalit.com/api/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Then call a tool by name with its arguments:

curl -s https://talks.bookchaowalit.com/api/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"get_all","arguments":{}}}'

Tools

ToolWhat it returnsArguments
get_allList every talk in the archivenone
get_by_idGet one talk by idid
searchSearch talk titles, events and datesquery

The methods initialize, tools/list and tools/call are supported; anything else returns a JSON-RPC error.

Not a full MCP server

This is a custom subset of the Model Context Protocol, made for curl and simple scripts. An off-the-shelf MCP client may reject the replies:

  • A tools/call answer puts the data in result.talks or result.talk, not in the content array that standard MCP clients expect.
  • There is no streaming or session support.