About MCP
MCP is an MCP server published by OpenRouterTeam in the Developer Tools category: openRouter Agent SDK.
The repository has 36 stars and 18 forks, with the last commit 4 days ago. Recent commit activity is the strongest signal that reported issues will get attention.
Install
git clone https://github.com/OpenRouterTeam/typescript-agentThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about MCP
Powered by Claude · Grounded in docs
Security checks
Static checks derived from the repository 6 days ago. Heuristics on the source, not an audit.
- ✓README presentThe repository ships documentation.
- !License declaredNo license file. Legally you have no right to use it in a product.
- ✓Tests presentA test suite exists in the repository.
- ✓Dependencies pinnedA lockfile pins dependency versions.
- ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
1 check has not been run yet.
Releases
README

typescript-agent
Monorepo for the OpenRouter TypeScript agent ecosystem.
Packages
| Package | Path | Description |
|---|---|---|
@openrouter/agent |
packages/agent |
Agent toolkit with optional @openrouter/agent/tool-set and @openrouter/agent/mcp subpaths. |
@openrouter/mcp |
packages/mcp |
Compatibility facade for the canonical @openrouter/agent/mcp integration. |
Development
This repo uses pnpm workspaces and Turborepo for task orchestration.
pnpm install # install all workspace dependencies
pnpm run lint # Biome check across all packages
pnpm run typecheck # TypeScript noEmit across all packages
pnpm run build # tsc across all packages
pnpm run test # vitest unit projects across all packages
pnpm run test:e2e # vitest e2e projects (requires OPENROUTER_API_KEY)
Turbo caches task results; re-running an unchanged task replays cached output.
Releasing
Releases are driven by Changesets. Each PR that ships a user-visible change should include a changeset:
pnpm changeset
Pick the affected packages and bump type. On merge to main, the release workflow opens a "Version Packages" PR. Merging that PR publishes every package with a consumed changeset to npm — no republishing of unchanged packages.
See .github/workflows/publish.yaml for the full flow.
README fetched from the repository 6 days ago. The original is authoritative.