Use Open Circuit SF with AI agents
Open Circuit SF runs a public MCP server that AI agents can use to look up our events and newsletter issues. It is read-only, returns only what the public website already shows, and needs no account or key.
Endpoint
https://www.opencircuitsf.com/mcpAlways use the www address. It speaks MCP's Streamable HTTP transport.
Discovery
https://www.opencircuitsf.com/.well-known/ai-catalog.jsonhttps://www.opencircuitsf.com/mcp/server-cardThe server card has the connection details: name, version, endpoint and transport. It does not list the tools; an MCP client gets those from the server itself.
Claude Code
claude mcp add --transport http opencircuitsf https://www.opencircuitsf.com/mcpOther clients
Most MCP clients accept an mcpServers entry like this one.
{
"mcpServers": {
"opencircuitsf": {
"type": "http",
"url": "https://www.opencircuitsf.com/mcp"
}
}
}Tools
- list_upcoming_events — List upcoming Open Circuit SF events, soonest first.
- search_events — Search Open Circuit SF events by words in the title, description and tags.
- get_event — Get one Open Circuit SF event by its id (its slug), from list_upcoming_events or search_events.
- list_newsletter_issues — List Open Circuit SF newsletter issues, newest first.
- get_newsletter_issue — Get one Open Circuit SF newsletter issue by its id (its slug), from list_newsletter_issues.
- get_about — What Open Circuit SF is, and how to join, subscribe or get in touch.
Times are RFC 3339 with an offset in America/Los_Angeles. Every event and newsletter result carries its public url.
Limits: 60 requests a minute per IP, one budget shared between /mcp and /api/public/v1/. Past that you get HTTP 429 with a Retry-After header in seconds. List results may be cached on the server for up to 60 seconds.
What it never returns
Drafts, unpublished events, unsent or withheld newsletter issues, attendees, RSVPs and subscribers. It returns only what the public website already shows.