tyk
Tyk is an API gateway for teams that want a common place to manage API and MCP access. Selection depends on the actual integration: proxying an existing remote MCP service, exposing REST operations as tools, and choosing the authentication and policy features that deployment requires. We reviewed a fixed source commit and completed selected configuration and Redis-script checks. A full Go build failed because host temporary storage filled; the task-created toolchain and caches were removed afterward. We did not launch the gateway or establish an upstream defect from that environment failure.
Seventeen local checks used Python Draft4Validator on bundled extension schemas and executed an original sliding-log Lua script in a separate Redis process. Selected missing fields, incorrect boolean types, invalid primitive names and unknown properties were rejected. An empty MCP extension and a well-formed but unreachable upstream URL remained structurally acceptable. Direct Redis calls reported prior counts zero, one and two, with remaining values one, zero and zero. Window trimming, expiry and separate keys behaved as recorded. The script stored the third attempt rather than rejecting a request.
These results are narrower than runtime enforcement. The selected Go script wrapper is marked deprecated and incomplete, and we did not execute it. HTTP authentication, actual rate-limit responses, MCP sessions and throughput remain untested. The source license distinguishes MPL 2.0 code outside ee from commercial code inside ee; feature and edition requirements need separate review. Consider Tyk when operating shared API policies justifies gateway infrastructure, then validate a controlled real service with normal, unauthenticated, denied and over-limit calls before relying on the deployment.
Read the full review, verification scope and sources →Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-11-05
- Commits, last 90 days
- 69
- Releases, last 90 days
- 6
- Latest release
- v5.13.5 (2026-10-30)
- Open issues
- 519
- Recent issues with at least one comment
- 3/3
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #7573 JWT panic in concurrent access15 comments · 2025-11-27
- #979 [TT-1755] Feature request: Expose prometheus metrics endpoint14 comments · 2017-08-03
- #2623 [TT-2378] - Allow 'OR' logic for multiple authentication modes for an API definition13 comments · 2019-10-17
- #6489 [TT-13406] Attaching a span to the trace started in the Tyk API Gateway from a grpc plugin when Open Telemetry is enabled.12 comments · 2024-09-09
- #3622 [TT-9621] Unable to send identical headers in ResponseObject of JSVM Middleware10 comments · 2021-07-10
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Who it fits
- You already need shared API/MCP governance and can operate a gateway.
- You will validate real client, upstream and edition requirements.
- You need a completed runtime or throughput benchmark from this review.
- Your only need is a small local tool and gateway operations add little value.
Compatibility
Quick start
Use cases
Alternatives
Comments
No comments yet. Be the first!