MCP

Furnace runs a public Model Context Protocol server exposing the same operations as the REST API, as typed tools an AI assistant can discover and call.

• Endpoint: https://api.falcata.io/mcp
• Transport: Streamable HTTP
• Server card: https://api.falcata.io/.well-known/mcp/server-card.json — identity and tool list, readable before connecting

Anonymous discovery, authenticated calls

initialize, tools/list, ping, and resources/* require no credentials, so an agent can evaluate the catalogue cold. tools/call authenticates with the same bearer token as REST, under the same permission checks and audit trail.

Tool naming

Tools are prefixed by domain — tasks_*, content_*, workflows_*, media_*, analytics_*, access_* — with whoami as the single unprefixed tool. The catalogue is large; agents should list once and filter by prefix rather than loading everything into context. See Tool catalogue.

Local alternative

CLI users can run furnace mcp — a stdio MCP server backed by the locally stored token, for hosts like Claude Code and Claude Desktop.