Rust-centric, codegen-first framework for building typed web services and generating idiomatic server scaffolds for Python, TypeScript, Rust, Ruby, PHP, and Elixir.

• Codegen-first CLI for OpenAPI 3.1, AsyncAPI 3.0, OpenRPC/JSON-RPC, GraphQL, and Protobuf/gRPC
• Agent-friendly MCP server with CLI-equivalent project init and code generation tools
• Real starter projects via spikard init for Python, TypeScript, Rust, Ruby, PHP, and Elixir
• Shared Rust runtime with Tower HTTP middleware, WebSockets, SSE, and gRPC support
• Quality-validated output with formatter, syntax, and lint/type checks for generated code

cargo install spikard-cli

Install the CLI, scaffold a real project, and generate typed handlers:

spikard init my_api --lang python --dir . cd my_api uv sync uv run python -m my_api.app

Generate code from a schema with the current command surface:

# OpenAPI 3.1 spikard generate openapi examples/schemas/auth-service.openapi.yaml --lang python --output ./generated.py # GraphQL spikard generate graphql examples/schemas/social.graphql --lang typescript --output ./src/generated.ts # Protobuf / gRPC spikard generate protobuf examples/schemas/user-service.proto --lang rust --output ./src/generated.rs

The CLI ships with an MCP server by default, exposing the same init and code generation surface over stdio:

spikard mcp

That MCP surface includes init_project, generate_openapi, generate_asyncapi_handlers, generate_jsonrpc, generate_graphql, generate_protobuf, generate_asyncapi_fixtures, generate_asyncapi_test_app, generate_asyncapi_bundle, validate_asyncapi, and get_features.

For HTTP transport, build or install with the mcp-http feature and run:

cargo run -p spikard-cli --features mcp-http -- mcp --transport http --host 127.0.0.1 --port 3001

All generated output is validated before write-out, and spikard init starter projects now produce real, idiomatic project layouts for every supported binding.

Benchmarked across 34 workloads at 100 concurrency (methodology):

Spikard is benchmarked against mature framework baselines across the supported bindings.

Key optimizations:

• Thin bindings over a shared Rust core
• Zero-copy FFI paths where the binding supports them
• Template-driven code generation validated before files are written

Use the task runner to keep the workspace aligned with CI:

task setup task build task test task lint task readme:validate

The authoritative README set is template-driven from scripts/readme_config.yaml, scripts/readme_templates/, and scripts/readme_content/.

• CLI - init, generate, testing, validate-asyncapi, and MCP
• Rust crate - runtime API and tower-based HTTP stack
• Python package - PyO3 bindings and Python-first usage
• Node package - napi-rs bindings for TypeScript and Node.js
• Ruby package - Magnus bindings and Ruby DSL
• PHP package - ext-php-rs bindings and PHP framework API
• Elixir package - Rustler bindings and Elixir router API

• spikard.dev
• Examples
• Schema fixtures

MIT - See LICENSE for details