rejifald/StitchAPI
by Various
The agent-native runtime where a typed, declarative stitch replaces fetch — for humans and agents alike.
MCP
rejifald/StitchAPI
Added 13 July 2026
Overview
A TypeScript runtime that replaces fetch with a typed, declarative stitch for API composition. Designed for use by both humans and AI agents, it provides a structured way to combine multiple API calls.
Best for
Best for
Developers building typed API orchestration layers for both human and agent consumption
Use cases
- Orchestrating multiple API calls with declarative pipeline definitions
- Building agent-compatible API integration layers with typed interfaces
- Replacing ad-hoc fetch logic with a consistent stitch-based runtime
How to use
Install
npm install stitchapi@rc # or: pnpm add stitchapi@rc · yarn add stitchapi@rc Tools exposed
STITCH_VALIDATIONSTITCH_DRIFTSTITCH_AUTH_WALLSTITCH_TIMEOUTSTITCH_CIRCUIT_OPENSTITCH_GRAPHQL
Tested with
Cursor, Windsurf, Cline
Notes
A TypeScript runtime that replaces fetch with a typed, declarative stitch for API composition. Designed for use by both humans and AI agents, it provides a structured way to combine multiple API calls.
8 stars on GitHub. Last updated 2026-07-13. Licensed Apache-2.0.
Use cases
- Orchestrating multiple API calls with declarative pipeline definitions
- Building agent-compatible API integration layers with typed interfaces
- Replacing ad-hoc fetch logic with a consistent stitch-based runtime
Pros
- Typed design improves developer experience and reduces runtime errors
- Declarative syntax simplifies complex API orchestration
- Agent-native focus allows seamless use by autonomous workflows
Cons
- Small community with only 8 GitHub stars, limiting support and ecosystem
- Requires shifting from imperative fetch to a new declarative abstraction
- Limited adoption evidence for production-scale or agent-heavy use cases
Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.
Pros
- Typed design improves developer experience and reduces runtime errors
- Declarative syntax simplifies complex API orchestration
- Agent-native focus allows seamless use by autonomous workflows
Cons
- Small community with only 8 GitHub stars, limiting support and ecosystem
- Requires shifting from imperative fetch to a new declarative abstraction
- Limited adoption evidence for production-scale or agent-heavy use cases
Pairs with
Other entries in the index that connect to this one. Click through to see the chain.
Get the free Developer’s Field Guide
A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.
Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.