API
RuneSpoke is built to be programmable. Alongside the web app, it exposes an API surface so you can integrate RuneSpoke into your own tools, scripts, and AI workflows.
REST and tRPC API
RuneSpoke provides a REST and tRPC API covering core platform resources such as projects, issues, code review, and deployments. The tRPC layer gives type-safe access from TypeScript clients, while the REST endpoints make it easy to call RuneSpoke from any language or environment.
Model Context Protocol (MCP) server
RuneSpoke ships a Model Context Protocol server that exposes platform capabilities to AI clients such as Claude Code, VS Code, and other MCP-aware tools. Queries are surfaced as resources and actions as tools, so an AI assistant can read your workspace and take governed actions on your behalf.
BYOAI and governance
Because RuneSpoke is BYOAI, AI calls run through the provider keys you connect, and high-impact actions can be governed by approval and access policies. This applies to programmatic access too, so automated and AI-driven workflows stay within the guardrails you set.
Full reference
This page is a high-level overview. The detailed reference, including authentication, endpoints, and MCP setup, lives in the documentation.
Questions
Building something with the RuneSpoke API? Email support@runespoke.ai and we will help you get set up.