Connect an agent over MCP
Connect an agent over MCP
Furnace exposes the same operations as the REST API through a Model Context Protocol server, so an AI assistant can browse and call the platform as typed tools.
Endpoint: https://api.falcata.io/mcp (Streamable HTTP)
Browse before you authenticate
initialize, tools/list, and resources/* work anonymously — an agent can inspect the full tool catalogue before any credential exists. The server also publishes a server card at https://api.falcata.io/.well-known/mcp/server-card.json, readable without opening a connection at all.
Authenticate
tools/call requires the same bearer token as REST — mint one via the device flow or OAuth. The token's scoping and your account's permissions apply identically on both surfaces.
Two ways to wire a client
Point any MCP-capable client at https://api.falcata.io/mcp with an Authorization: Bearer header. Tools are namespaced by domain: tasks_*, content_*, workflows_*, media_*, and so on; whoami is the one unprefixed tool.
Next: MCP for the full server contract, or Tool catalogue for how the tool surface is organized.